Mostly, with File Import or Offline Collect API, we join offline data to online data based on a visitor stitching key.

However, it is possible to do this without the need for a stitching key.  Consider an example use case - the client wants to pass us data that's calculated after, or even during, an anonymous user's online visit, to store in the visitor profile.

The key here is tealium_visitor_id.  On any incoming event into AudienceStream, this is how the Visitor Processor first decides which visitor profile to associate this event with, before any visitor stitching is considered - it is the anonymous identifier for that event.

For Collect API calls, you can simply specify the tealium_visitor_id in the call, as follows;

"tealium_account": "<<the account>",
"tealium_profile": "<<the profile>>",
"tealium_visitor_id": "017544f6411b00210114efdcdbb803078004007000bd0"
For File Imports, you can map a column in the CSV to tealium_visitor_id, and leave the "Enable Visitor ID Mapping in AudienceStream" box unticked;
What value should you use for tealium_visitor_id in the offline call?
If you have a simple setup, with a single cookie domain, and no extensions altering the outgoing value of tealium_visitor_id, then this will be the same as the v_id portion of the utag_main cookie.
If you have extensions altering the outgoing value of tealium_visitor_id, then your tealium_visitor_id in the offline data calls will need to match.
If you have multiple domains, and/or you just want to be sure that the value will always match, you can create a visitor attribute to store the overall anonymous visitor ID on the visitor profile.  You can bring this back to the client device using Data Layer Enrichment, or otherwise send it to where it is needed as the key value for the offline import.  The visitor attribute you create is the same one as "vrStrTealiumVisitorIDOverall" described in this article -
Version history
Last update:
‎10-20-2020 01:12 AM
Updated by: