This article describes the order of operations for Tealium AudienceStream CDP and covers the following processes: incoming events, creating visitor profiles, enriching attributes, building audiences, and triggering connectors.
In this article:
AudienceStream is integrated tightly with Tealium EventStream, so this overview starts at the point that events are received.
The default order of operations:
Enrichments are evaluated in two ways: the timing and the condition.
The enrichment timing determines when to evaluate the condition. This appears in the interface as the WHEN setting and is limited to the following options offered in AudienceStream:
The enrichment condition determines if the attribute value will be updated. Conditions appear in the interface as rules, which you configure using logical operators.
The event is received from Tealium Collect.
The event attribute enrichments are evaluated.
Visit and visitor attributes are stored in a visitor profile, so the first step in enriching these attributes is to get the visitor profile. If the
tealium_visitor_id matches an existing profile, the profile is enriched. If the
tealium_visitor_id does not match an existing profile, a new profile is created and is enriched.
Visit and visitor attribute enrichments are evaluated based on their timing and condition.
In the following example, the attribute enrichment for the
Cart Abandoner badge is evaluated based on the following:
cart_total_items greater than 0
If Enable Rule Dependency Checking is enabled, enrichments are executed in the correct order to accommodate dependencies in rules.
If Enrichment Order Respects UI Order is enabled, enrichments are executed in the order they appear in the user interface, with adjustments for dependency checking if needed. Otherwise, enrichments are executed in attribute ID order.
If the event contains a user identifier that is configured to enrich a visitor ID attribute, the visitor ID attribute is only set if each of the following conditions are met:
If there are multiple visitor ID attributes, they are evaluated in attribute ID order.
If an enriched visitor ID attribute matches multiple visitor profiles, they are merged into a new visitor profile.
AudienceStream evaluates the visitor profile to determine which audiences it should join or leave. The visitor joins an audience if the audience rule is
true or leaves an audience if the audience rule is
false. The transition of a visitor profile into or out of an audience triggers connector actions.
AudienceStream evaluates triggers to determine which connector actions to initiate. Connector actions are initiated when the trigger condition is met. A connector condition can be one of the following: