Lifecycle_Events Table

The Lifecycle_Events table enables the use of event-driven customer behaviors within campaigns by providing a set of fields that combine predictions for customer behaviors with transaction details from the Unified_Transactions table.

Important

The fields that are described in this topic enable downstream workflows in AmpIQ, including using the output of predictive modeling.

Requirements and recommendations

This topic assumes the following requirements are met:

  • The Unified_Transaction table is configured for use with AmpIQ.

  • Predicted models are enabled for AmpIQ.

Add table

The Lifecycle_Events table enables the use of event-driven customer behaviors within campaigns by providing a set of fields that combine predictions for customer behaviors with transaction details from the Unified_Transactions table.

To add the Lifecycle_Events table

  1. From the Database Editor, click Add Table.

  2. Name the table “Lifecycle_Events”.

  3. Set the build mode to SQL.

  4. Click Apply template, and then select Lifecycle_Events.

  5. Click Validate to verify the SQL runs without error.

  6. Click Next. This opens the Database Table Definition page.

  7. Add a table description. This enables a tooltip that is visible from other areas in Amperity.

  8. Verify that the db/required field semantic is applied to the event_type column.

  9. From the Table Semantics drop-down, select Lifecycle_Events.

  10. Click Save.

Column reference

The Lifecycle_Events table contains the following columns:

Column Name

Data type

Description

amperity_id

String

The unique identifier that is assigned to clusters of customer records that all represent the same individual. The Amperity ID does not replace primary and foreign keys, but exists alongside them within unified profiles.

Note

The Amperity ID is a universally unique identifier (UUID) that is represented by 36 characters spread across five groups separated by hyphens: 8-4-4-4-12.

For example:

123e4567-e89b-12d3-a456-426614174000

event_status

String

The status for a lifecycle event. Possible values:

  • Active

  • Cooling down

  • At risk

  • Highly at risk

  • Lost

event_status_start_date

Datetime

The date on which the current lifecycle event started.

event_type

String

The type of lifecycle event. For example: “Predicted Lifecycle Status”.

is_current

Boolean

A flag that indicates if this is the most recent lifecycle event associated with the Amperity ID.

Tip

When the value of is_current is true only the most recent event_status is returned.

previous_event_status

String

The lifecycle event status for the previous lifecycle event associated with the Amperity ID.

prev_event_status_start_date

Datetime

The date on which the previous lifecycle event started. This value is NULL when there is no previous lifecycle event.