Introduction

This document describes the data flows used to monitor the execution of marketing and care actions initiated from an action plan within Lifetime Analytics and the Operator's CRM/Campaign management tools.

Creating an action in Lifetime Analytics generates a cohort of subscriptions to be contacted and monitored. The cohort is determined by the cluster definition rules and selected filters applied to active subscribers at the cluster snapshot date.

Note: The application automatically excludes any subscriptions already part of an active action or those contacted within the configured contact policy retention period (30 days by default).

Data Export and Import Functions

Export Function

The export function allows users to export relevant subscriptions for an action.

Import Function

The import function enables users to import feedback regarding subscriber responses (e.g., reached, accepted, rejected, etc.), facilitating the monitoring of action impacts over subsequent months.

Execution Methods

These functions can be executed through:

  • Manual Execution: Using the export/import buttons in the Action Plan details or action plans list UI with Excel (XLSX) files. Available to power users with action-plan:export and action-plan:import permissions.
  • Automated Execution: Using the Lifetime Analytics API, SDK, or CLI (refer to "Integration Automation with Lifetime Analytics"). The data is handled in JSON format.

Exporting Subscriptions to Contact

The exported data contains  the following fields :

Subscription

Format

Description

Marketing Product ID

String

Subscription ID

Customer ID

String

Customer ID associated with the subscription

Action ID

String

Internal identifier for the action in Lifetime Analytics

Status Level 1

String

Possible values: not_reached, blacklisted, accepted, rejected

Status Level 2

String

Additional label. If Statis Level 1 is accepted, this field contains the accepted offer name

Snapshot

Date ISO format

Snapshot date

State

String

Subscription state code (e.g., BoP, gross-adds)

Product Family

String

Values of the selected factors

Depending of the data format defined into data reference

 

During export, Status Level 1 and Status Level 2 are populated with the most recently imported follow-ups.

  • Excel Format: The exported file contains an "Action Plan Info" sheet detailing Clusters and Actions, and a "Subscriptions" sheet listing the relevant subscriptions.
  • JSON Format: The exported data follows a predefined JSON schema.

Importing Action Follow-Ups After Contact Attempts

The import function is used to track the progress of an action and is initiated by the Operator. It can be performed multiple times per day or month.

The import file must follow the same structure as the export file, with completed Status Level 1 and Status Level 2 fields.

Status Level 1 Values

  • not_reached: Contact attempts were made, but the subscriber was not reached.
  • blacklisted: The subscriber should not be contacted for any reason.
  • accepted: The subscriber was reached and accepted an offer. The offer name/code should be entered in Status Level 2.
  • rejected: The subscriber was reached but rejected the offer.

Handling Churned Subscribers

If a subscriber churned before any contact attempt, the application will automatically populate Status Level 2 with "Churned before contact attempt."

Import Format

  • Excel Format: Matches the export format. The "Contacted" and "Decision" fields must be completed with the respective values.
  • JSON Format: Follows the same structure as the Subscriptions JSON schema.