mParticle collects data from all your platforms and data connections and connects it to all of your team’s tools and systems. All collected data is used to resolve identities and stitch together customer profiles and is available to be forwarded to downstream systems. Data can also be stored in mParticle, in case you need to run data replays (re-ingesting data with help from mParticle Support). Additionally, mParticle makes all data available for evaluation in Audiences and Calculated Attributes. However, many events and the data related to them may not be needed for running data replays or evaluations depending on how you use Audiences or Calculated Attributes. With Tiered Events, you can choose to collect data but not store it, or to collect and store data but not evaluate it. These configurations help improve performance.
mParticle provides three event tiers. All three tiers support ingestion and forwarding of data, but provide different levels of support for storage and evaluation:
Connect: Data is not stored in mParticle, but can be ingested and forwarded. The data is also used for profile enrichment. Because Connect tier events aren’t stored, they won’t be visible in the User Activity view.
The following table can help you decide which tier to apply to data:
Feature |
Personalize | Preserve | Connect | |||
---|---|---|---|---|---|---|
Event data | ✓ | ✓ | ✓ | |||
Profile enrichment | ✓ | ✓ | ✓ | |||
Ingest | ✓ | ✓ | ✓ | |||
Forward | ✓ | ✓ | ✓ | |||
Store for data replays and backfills | ✓ | ✓ | ||||
Evaluate for calculated attributes | ✓ | |||||
Evaluate for real-time audience | ✓ |
To change events from the default Personalize event tier, plan and implement the changes:
In Data Master > Catalog, click Download Report to download a CSV file that lists all the events used in calculated attributes and audiences, and shows data volumes for the time range you specify.
The report shows you approximately how many of each event type have been received from input for the date range you selected. You can use this number, for example, to identify events that you may want to change to another tier, and which will be easy to remove from the calculated attribute or audience definition so that you can change the tier for that event type.
Verify that the consequences of changing tiers are acceptable in your environment:
To change the event tier:
Was this page helpful?