Listening Event Aggregate Data Adapter

Access aggregated activity data for decisioning and orchestration with the Listening Event Aggregate Data Adapter. It focuses on listening event data and excludes orchestration or action-related data aggregation.

Customize the data adapter for specific use cases by creating iterations tailored to each aggregation requirement.

Examples

To track customer engagement with 'Campaign A' for 'Washing Machines', set the Listening Event Aggregate Data Adapter to collect 'Campaign ID' and 'Proposition' over the campaign duration.

For insights on average product value, configure the adapter to aggregate 'Product Value' by 'Activity Type'. To focus on specific products, include the relevant 'Propositions' or 'Proposition Categories'.

Create a Data Adapter

  1. In MXO, navigate to Collect.

  2. Go to External Data and select Create.

  3. Select 'Listening Event Aggregate' as the adapter type.

  4. Name the adapter descriptively for ease of identification.

  5. Provide a concise description and intended use of the adapter.

  6. Initiate setup with 'Let’s get started'.

  7. Enter relevant Configuration Details to set up the adapter’s functionality.
    FieldDescription
    Group 1, 2, 3

    Select up to three attributes for aggregation, such as Customer and Activity Attributes, or dimensions like Activity, Proposition, and Channel. At least one attribute must be defined as Group 1.

    Sum GroupSelect numeric Customer and Activity Attributes if needed.
    Days

    The time frame for including data in the aggregations generated by the adapter.

    For instance, for a typical 7-10 day campaign, set to ‘10’ to exclude data older than 10 days.

  8. Use 'Test Configuration' to validate the settings.

  9. Apply the configuration upon successful testing.

  10. Save the new adapter configuration.New Data Adapter

Limitations

The Listening Event Aggregate Data Adapter can process up to 100 rows and 180 days of data. If the 'Days' parameter is set to '10' and the adapter accumulates 100 rows by Day 3, it will discard the oldest data for new entries.

Despite a UI issue allowing 'Days' to be set beyond 180, MXO will not aggregate data older than 180 days.