Tealium Learning Center

This article describes various visitor stitching scenarios. In this article: Examples of a Visitor Using Two Different Email Addresses When the same user is identified by two email addresses, the result is determined based on the device and browser used for each. For example, a user visits a website for the first time and provides an email address when submitting a form. The email address is hashed, it enriches the Email Address Hash visitor ID attribute, and a new visitor profile is created in AudienceStream. The resulting visitor profile might look like this: Attribute Value Anonymous ID 01754649ad73005a6d584d2732c401078005b0700093c Device Laptop Browser Chrome 89 Email Address Hash 16c18d336f0b250f0e2d907452ceb9658a74ecdae8bc94864c23122a72cc27a5 Scenario 1: A Different Email Address from the Same Device and Browser A week later, the user visits the website using the same device and browser and submits a form with a different email address. The anonymous ID is the same, so the incoming event will match the profile that was created on the user's first visit. However, because a visitor ID attribute cannot be changed, the new email address hash value will not be used. Result: One visitor profile with a visitor ID attribute set to the email address hash. Scenario 2: A Different Email from a Different Device or Browser A week later, the same user visits the website using a different device or browser and submits a form with a different email address. The anonymous ID will be different, so the incoming event will not match the profile that was created on the user's first visit.  A new profile is created and there are two profiles for this user after the second visit. No visitor stitching occurs, because the visitor ID attribute does not match (the email addresses are different).  These two profiles could be stitched together later, if they matched on a second visitor ID attribute. Result: Two visitor profiles, with each visitor ID attribute set to the corresponding email address hash. Example of Two Visitor Profiles Matching on a Second Visitor ID Attribute In this example, a user visits a web site from two different devices and is assigned a customer ID for each visit. The anonymous IDs do not match, and two separate profiles are created. The customer ID is configured to enrich visitor ID attribute #1, and the visitor ID attribute is enriched in each profile, as shown below. This scenario could only happen if the anonymous ID ( tealium_visitor_id ) is not known, or are different in the two profiles. No user IDs or visitor ID attributes would be evaluated if the anonymous IDs match, and the second profile would not be created. The user visits the website again from the first device and provides an email address when submitting a form. The customer_email address attribute is configured to enrich visitor ID attribute #2. Visitor ID attribute #2 in Profile A is enriched with the email address, as shown below. When the user visits the website from the second device and provides the same email address when submitting a form, the email address matches visitor ID attribute #2 in Profile A, and the two profiles are stitched together to create Profile C, as shown below. Profile C contains a new replaces array, which holds values that are no longer stored in visitor ID attributes, but can still be used for visitor stitching in the future. Profile A and Profile B had different values for the anonymous ID and Visitor ID Attribute #1 (Customer ID). Because only one value can be set per visitor ID attribute, two values had to move to the replaces array. Profile B was the newer profile and had fewer events than Profile A, so the Profile B identifiers were moved to the replaces array. HTTP API and File Import Data Sources For web or HTTP API data sources, this scenario would happen only if the attribute ID value of Visitor ID Attribute #1 (Customer ID) is lower than Visitor ID Attribute #2 (Hashed Email). With file import, because visitor ID mappings can be customized and user identifier enrichment occurs in the ordered mapped, this scenario could be achieved in a few different ways depending on the setup. About Stateless Events HTTP API and file import both send stateless events because the tealium_visitor_id value is not automatically assigned. For HTTP API requests, each event generates a new visitor profile unless tealium_visitor_id is set. In these cases, we recommend generating your own anonymous value for tealium_visitor_id . File import data sources typically include a user identifier which maps to a visitor ID attribute. If a tealium_visitor_id value is not included in an HTTP API request or in a file import mapping, AudienceStream assigns a random value to the anonymous ID and creates a new visitor profile prior to visitor stitching. Related Articles About Visitor Stitching Visitor ID Attribute Creating a Visitor ID Anonymous ID, User Identifiers, and Visitor ID Attributes ... View more

This article defines the key components involved in identity resolution: anonymous IDs, user identifers, and visitor ID attributes. In this article: Anonymous ID An anonymous ID is a unique and anonymous value assigned to a visitor on each visit to a site or each use of an app. The value is generated by Tealium Collect and is stored in a first-party cookie named utag_main_v_id , and received in Tealium EventStream API Hub as tealium_visitor_id . The Tealium anonymous ID tracks a visitor over multiple visits from the same browser or app, but not across different browsers or devices. For web data, and in most cases, this anonymous ID is also stored as the third-party cookie TAPID (Tealium EventStream attribute tealium_thirdparty_visitor_id ), which can be used to track visitors across domains within the same browser for businesses that require it. Each anonymous ID generates a new visitor profile in Tealium AudienceStream CDP, which may be combined with another profile using a shared user identifier in a process called visitor stitching. User Identifiers A user identifier is a data layer variable or an event, visit, or visitor attribute populated in your Tealium installation that uniquely identifies a known user across devices, platforms, and browsers. A user identifier can be configured as any of the following: Data layer variable in iQ Tag Management Event attribute in EventStream Visit or visitor string attribute in AudienceStream The value of a user identifier should be unique to each visitor, but should not contain personally identifiable information (PII), such as a driver's license number, bank account number, or email address. A good user identifier is unique and does contain PII. Good examples include email_address_hash , member_id , and customer_id . For example, to use an email address as a user identifier, convert the value to a hashed string of characters to conceal the original data while retaining the unique value. User identifiers are used to populate visitor ID attributes in AudienceStream. Visitor ID Attributes The visitor ID attribute is a special attribute type in AudienceStream that gets its value from a user identifier and is used in visitor stitching. When a user identifier is provided across multiple sessions, AudienceStream combines the visitor attributes from those visitor profiles into one profile using a process called visitor stitching. Visitor ID attributes are not automatically created by AudienceStream. You must create visitor ID attributes in AudienceStream and choose the user identifiers that populate them. After a visitor ID attribute is set, its value cannot be changed. Example of a visitor ID attribute named Hashed Email that is populated by the user identifier email_address_hash (event attribute): Related Articles About Visitor Stitching Visitor ID Attribute Creating a Visitor ID Attribute Visitor Stitching Scenarios ... View more

This article provides detailed steps to create a visitor ID attribute. This example uses customer_id , which is typically available when a visitor makes a purchase, as a user identifier. Learn more about Anonymous ID and User Identifiers. In this article: How It Works To create a visitor ID attribute, first determine which event attribute is a good user identifier for your users. The value of the user identifier must be unique for each visitor. This example uses customer_id as the user identifier. The user identifier is used to populate a visitor string attribute using a rule to match a qualifying event. This example uses the purchase event. The visitor string attribute is used to verify that the user identifier is unique for each visitor. After the visitor string attribute is verified to be unique across visitors, it is used to populate a visitor ID attribute. Step 1: Create a Rule Before you create a visitor ID attribute, you must create a rule to specify when the value is assigned to a visitor ID attribute. Use the following steps to create a rule to set the visitor ID attribute to customer_id when customer_id is assigned and the value is not "none". Go to   Server-Side Tools > Manage Rules. Click   + Add Rule. The   Create Rule   dialog displays. Enter the Title, in this case "customer_id is assigned". Select customer_id for the attribute and  is assigned   from the operator drop-down list. Click +Attribute Condition, select customer_id for the attribute, select does not equal (ignore case) for the operator, enter "none"  for the value, then press Enter to confirm. Step 2: Create a Visitor String Attribute Create a temporary string attribute to use for verification in Audience Discovery. If you create a visitor ID attribute without verifying data, you risk improperly stitching visitor profiles. Use the following steps to create a string attribute: Go to AudienceStream > Visitor/Visit Attributes. Click + Add Attribute. In the Add Attribute dialog, select Visitor for scope, then click Continue. For Choose a data type, select String, then click Continue. In the Add Attribute dialog, enter a Title and enter optional Notes. Click Add Enrichment and select Set String. In the Set String dialog, select customer_id for Set String to. For WHEN, select ANY EVENT. In the Choose a rule field, select the rule created in Step 1. Click Finish. Step 3: Publish to Production Save and publish the rule and attribute to production so that AudienceStream can start collecting the data. The number of users on the website and the type of data being collected will determine how long to wait before you can verify the data in AudienceStream. If you are using a first-party cookie that is available for every visitor, data should appear within 15 minutes. Step 4: Verify Data To verify that the chosen attribute is unique, use Audience Discovery to view the distribution of the attribute's values across your active visitors. For more information, see Audience DIscovery. Bad Visitor String Attribute A bad visitor string attribute would be one where there are hundreds of users with the same value. If stitching was enabled, all these users would all be combined into a single visitor profile, which is obviously incorrect. For example, if you see multiple instances of "unknown", you can add conditions to the rule to exclude those instances. If there are many visitors with the same value for the visitor string attribute, choose a different user identifier to populate the string attribute and verify the results again. Good Visitor String Attribute In the case of a good visitor string attribute, only a small sample of users would have the same value. There may be multiple users with a value of "none", which is normal because not every visitor has a value. It may be difficult to determine why visitors have the same value. When less than 1% of the visitors have two visitors assigned the same visitor string attribute, it is OK to use the chosen user identifier to populate a visitor ID attribute and enable visitor stitching. Step 5: Create Visitor ID Attribute After you verify that you have a good visitor string attribute, create a visitor ID attribute. Set the visitor ID to the  string attribute used for verification, and select the newly created rule. Save and publish to production to start recording data. Step 6: Enable Visitor Stitching After you create the visitor ID attribute, visit the Support Desk to request that visitor stitching be enabled for your account. Use Trace to See It In Action After the configuration is live, an example of stitching occurs as follows: A visitor logs into the website on their computer. Visitor profile A is created and captures the visitor ID attribute. Eventually the session ends. The same visitor later logs into the website from a mobile device. Visitor profile B is created and captures the visitor ID attribute. AudienceStream determines that profile A and profile B share the same value for the visitor ID attribute, and both profiles are stitched and merged into Profile C. Related Articles Visitor ID Attribute  About Visitor Stitching Anonymous Identifiers, User Identifiers, and Visitor ID Attributes  Visitor Stitching Scenarios  ... View more

Some data sources use webhooks to send actionable events to Tealium EventStream or Tealium AudienceStream. When you add one of these data sources, the Get Code tab shows a URL and code that you use to configure the webhook. Tealium supports incoming webhooks for the following data sources: Affirm HTTP API - Advanced Hubspot Workflow Intercom Iterable MailChimp SendGrid Zapier ... View more

To improve performance when loading the Universal Tag from behind the Chinese firewall, you can use tags.tiqcdn.cn to expedite content delivery inside mainland China, as well as elsewhere in the world. tags.tiqcdn.cn is delivered by Akamai through the closest node to the user, which can be inside or outside the firewall. If you cannot modify your site source code to use tags.tiqcdn.cn, you can add the China CDN Deployment Extension to your profile. This extension determines whether the user is inside or outside China. When the user is in China, tags.tiqcdn.cn is used to deliver content instead of tags.tiqcdn.com. For more information, see China CDN Deployment Extension. In this article: Table of Contents Placeholder Considerations Choose a method for loading the universal tag If you can modify the source code for your site, use tags.tiqcdn.cn in the code you add to your website. If you cannot modify the source code for your site, use the China CDN Deployment Extension. Use a unique profile Use a unique profile for each of your websites. Using multiple profiles allows you to tag each website and customize the delivery of all Tealium-based content for that website. tags.tiqcdn.cn tags.tiqcdn.cn is available from Akamai through the closest node to the user. This means you can use a .cn domain for users outside the China firewall with no impact on performance for those users. Internet Content Provider (ICP) license For all web content to be delivered in mainland China, your website requires a valid ICP license. Updating the Code for Your Website Create a profile for the .cn domain. For more information, see Managing Profiles. Update the Publishing URLs in Publish Configuration to specify the .cn CDN path. For example: https://tags.tiqcdn.cn/utag/your_account/your_profile/dev/utag.js https://tags.tiqcdn.cn/utag/your_account/your_profile/qa/utag.js https://tags.tiqcdn.cn/utag/your_account/your_profile/prod/utag.js For more information, see Publish Configuration. Add the following JavaScript , which uses tags.tiqcdn.cn, to the HTML source. <script type="text/javascript"> (function(a,b,c,d){ a='https://tags.tiqcdn.cn/utag/your_account/your_profile/prod/utag.js'; b=document;c='script';d=b.createElement(c);d.src=a;d.type='text/java'+c;d.async=true; a=b.getElementsByTagName(c)[0];a.parentNode.insertBefore(d,a); })(); </script> Using the China CDN Deployment Extension Create and configure a China CDN Deployment Extension to determine the user's location and serve utags.js from the appropriate CDN. For more information on creating an extension, see China CDN Deployment Extension. ... View more

This article describes how to set up the BlueKai tag in your Tealium iQ Tag Management account. BlueKai is the industry's leading cloud-based big data platform that enables companies to personalize online, offline and mobile marketing campaigns with richer and more actionable information about targeted audiences. In this article: Table of Contents Placeholder Tag Tips Use mapping to override the standard configuration values or to pass additional parameters. Tag Configuration Go to the Tag Marketplace and add the BlueKai tag. For more information, see Tags. After adding the tag, configure the following variables: Site ID: Unique number that identifies a pixel as belonging to a certain DMP Partner. Limit: Maximum number of media partner segment pixels that will be fired by BlueKai. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see Data Mappings. The following variables are available for the BlueKai tag: Standard Variable Description Site ID (siteid) Limit (limit) Allow Multiple Calls (allow_multiple_calls) [boolean] show   tod   lv   ss   top   sub1   sub2   sub3   ref   srch   ... View more

This article describes how to use the Zapier data source to create a webhook in your Zapier account to send actionable events into Tealium AudienceStream. In this article: Table of Contents Placeholder Prerequisites Zapier account Tealium AudienceStream account How It Works Zapier allows you to send webhooks from Zaps to an endpoint that you specify. These requests inform Tealium AudienceStream about activity in your Zapier account. When you add the Zapier data source a unique endpoint is generated that you use to configure the Zapier webhook. Zapier Data Source The Zapier data source generates a unique URL to use in your Zapier Webhook configuration. The data source also generates query string parameters for the Zapier webhook. The webhook URL is: https://collect.tealiumiq.com/event The following query string parameters are required in the Zapier configuration: tealium_acount=ACCOUNT tealium_profile=PROFILE tealium_datasource=DATA_SOURCE_KEY tealium_event=EVENT_NAME Add the Zapier data source before proceeding. Related:   How to Add a Data Source Zapier Setup After you have your data source endpoint, you can proceed to your Zapier account to create the webhook. When creating the Zapier webhook, use the URL and query string parameters for the data source, followed by any additional event attributes that are needed. If your Zapier events are intended to enrich visitor profiles within AudienceStream, be sure to include a user ID as well. For information on setting up Zapier Webhooks, see Use Code and Webhooks in Zaps. ... View more