Tealium Learning Center

This article describes how to set up the Bing Ads Universal Event Tracking (UET) tag in your Tealium iQ Tag Management account. In this article: Table of Contents Placeholder Tag Tips Use mapping to: Override the standard configuration values Override the E-Commerce extension values Pass custom parameters Set up event triggers Mapping to Custom Property/Parameter in the Standard tab sends that parameter with all events. Use the Event Parameters tab to send data only to certain events Supports the following e-commerce extension values: Order ID Order Sub Total Order Shipping Order Tax Order Currency Order Coupon/Promo Code List of Product IDs List of Names List of Brands List of Categories List of Quantities List of Prices Tag Configuration First, go to the Tealium tag marketplace and add the Bing Ads Universal Event Tracking (UET) tag. (Learn more) After adding the tag, configure the following settings: Tag ID Your Bing-supplied tag identifier (Tag ID). 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 available categories are: Standard Variable Description tagid Tag ID. Your tag identifier provided by Bing Ads. event_category Event Category. Sends information about the element or object being tracked. Example: Button event_action Event Action. Sends user actions. Example: click, mousedown event_label Event Label. Sends informative labels or details about the even goal. Example: Product demo event_value Event Value. Sends the numerical value of the event goal. description Error Description. The description with the error experienced by the user. fatal Error Fatal. Whether the error experienced by the user is fatal. method Method. The method associated with the user's action. screen_name Screen Name. The name associated with the screen the user is currently viewing. search_term Search Term. The term used in the user's search. content_type Content Type. The type of content selected by the user. content_id Content ID. The ID of the content selected by the user. promotion_creative_name List of Promotion Creative Names. An array of creative names used in the promotion. promotion_creative_slot List of Promotion Creative Slots. An array of creative slot names used in the promotion. promotion_id List of Promotion IDs. An array of promotion iDs used in the promotion. promotion_name List of Promotion Names. An array of promotion names used in the promotion. custom.myvar Custom Property/Parameter. A custom property for you events. Sent with all events, use Event Parameters to set properties for specific events. Replace myvar with the name of your property. E-Commerce Variable Description checkout_step Checkout Step The current step of the checkout process the user is on. checkout_option Checkout Option The current checkout option chosen by the user. order_id Order ID Use to override the default e-commerce value _corder order_subtotal Sub Total Use to override the default e-commerce value _csubtotal order_shipping Shipping Amount Use to override the default e-commerce value _cship order_tax Tax Amount Use to override the default e-commerce value _ctax order_currency Currency Use to override the default e-commerce value _ccurrency order_coupon_code Promo Code Use to override the default e-commerce value _cpromo product_id Array List of Product IDs Use to override the default e-commerce value _cprod product_name Array List of Names Use to override the default e-commerce value _cprodname product_brand Array List of Brands Use to override the default e-commerce value _cbrand product_category Array List of Categories Use to override the default e-commerce value _ccat product_quantity Array List of Quantities Use to override the default e-commerce value _cquan product_unit_price Array List of Prices Use to override the default e-commerce value _cprice List of Product Creative Names Array An array of creative names used for the product. List of Product Creative Slots Array An array of creative slots used for the product. List of Product Location IDs Array An array of location IDs used for the product. Events and Engagements Map to these destinations for triggering specific events on a page. Use the following steps to trigger an event: Select an event from the drop-down list. Choose from the predefined list, or create a custom event. For a custom event, enter a name with which to identify it. In the Trigger field, enter the value of the variable being mapped. To map more events, click the plus sign (+) and repeat Steps 1 and 2. Click Apply. The event triggers when the value supplied is found in the data layer. Variable Description add_payment_info Add Payment Info User has added new payment information to the transaction. add_to_cart Add to Cart User has added one or more items to a shopping cart. add_to_wishlist Add to Wishlist User has added one or more items to a wishlist. begin_checkout Begin Checkout User has begun the checkout process. checkout_progress Checkout Progress User has exchanged steps in the checkout progress. exception Exception The user has encountered an exception. generate_lead Generate Lead The user's action has generated a lead. login Login The user has logged in. page_view Page View The user has viewed a page. purchase Purchase Te user has completed a purchase of one or more products. refund Refund The user has requested a refund on one or more products. remove_from_cart Remove from Cart The user had removed one or more items from a shopping cart. screen_view Screen View The user has viewed a screen. search Search The user has searched. select_content Select Content The user has selected on one or more content items. set_checkout_option Set Checkout Option The user has selected a checkout option for the current checkout step. share Share The user has shared content. sign_up Sign Up The user has signed up. timing_complete Timing Complete The timing information for he user's page load. view_item View Item The user has viewed a singular item, often a detail page. view_item_list View Item List The user ahas viewed a list page with one or more items. view_promotion View Promotion THe user has clicked on a promotion. view_search_results View Search Results The user has viewed the results of a search. custom Custom Event The user has initiated action related to a custom event. Product Audience Events Map to these destinations for triggering specific events on a page. Use the following steps to trigger an event: Select an event from the drop-down list. Choose from the predefined list, or create a custom event. For a custom event, enter a name with which to identify it. In the Trigger field, enter the value of the variable being mapped. To map more events, click the plus sign (+) and repeat Steps 1 and 2. Click Apply. The event triggers when the value supplied is found in the data layer. Variable Description retail Retail Send data for retail-based marketing. travel Travel Send data for travel-based marketing. hotel Hotel Send data for hotel-based marketing. Event Parameters Map to these destination if you wish to pass additional data with events mapped earlier. Parameters are only used with predefined events. To learn how to pass a parameter with a custom event, see Creating a Custom Event Specification. Use the following steps to pass a parameter with a predefined event: Select a Bing event from the drop-down list. Select a Bing parameter from the drop-down list. If using a custom parameter, enter a name with which to identify it. Click Add. Variable Description event_category Event Category The category desired for the current event. Sends information about the element or object, such as a button being clicked on. event_action Event Action The action name desired for the current event. Sends user actions, such as click or mousedown. event_label Event Label The label desired for the current event. Sends informative labels or details, such as product demo, about the product goal. event_value Event Value Send the numerical value of the event goal for the current event. custom Custom Property/Parameter A custom property associated with the current event. description Error Description The description of the error experienced by the user. fatal Error Fatal Whether or not the error experienced by the user is fatal. method Method The method associated with the user's action. screen_name Screen Name The name associated with the current screen the user is viewing. search_term Search Term The term used in the user's search. content_type Content Type The type of content selected by the user. content_id Content ID The ID of the content selected by the user. checkout_step Checkout Step The current step of the checkout process the user is on checkout_option Checkout Option The current checkout option chosen by the user. order_id Order ID Use this to override the default e-commerce value _corder . order_total Order Total Use this to override the default e-commerce value _ctotal . order_subtotal Sub Total Use this to override the default e-commerce value _csubtotal . order_shipping Shipping Amount Use this to override the default e-commerce value _cship . order_tax Tax Amount Use this to override the default e-commerce value _ctax . order_currency Currency Use this to override the default e-commerce value _ccurrency . order_coupon_code Promo Code Use this to override the default e-commerce value _cpromo . product_id List of Product IDs Use this to override the default e-commerce value _cprod . product_name List of Names Use this to override the default e-commerce value _cprodname . product_brand List of Brands Use this to override the default e-commerce value _cbrand . product_category List of Categories Use this to override the default e-commerce value _ccat . product_quantity List of Quantities Use this to override the default e-commerce value _cquan . product_unit_price List of Prices Use this to override the default e-commerce value _cprice . product_creative_name Array List of Product Creative Names An array of creative name used for the product. product_creative_slot Array List of Product Creative Slots An array of creative slots used for the product. promotion_creative_name Array List of Promotion Creative Names An array of creative names used in the promotion. promotion_creative_slot Array List of Promotion Creative Slots An array of creative slot names used in the promotion. promotion_id Array List of Promotion IDs An array of promotion IDs used in the promotion. promotion_name Array Promotion Names An array of promotion names used in the promotion. Product Audience Parameters Map to these destination if you wish to pass additional data with events mapped earlier. Parameters are only used with predefined events. To learn how to pass a parameter with a custom event, see Creating a Custom Event Specification. Use the following steps to pass a parameter with a predefined event: Select a Bing event from the drop-down list. Select a Bing parameter from the drop-down list. If using a custom parameter, enter a name with which to identify it. Click Add. Variable Description ecomm_prodid Product ID One or more IDs currently visible to or selected by the user. ecomm_pagetype Page Type The current page type visible to the user. ecomm_totalvalue Total Value The total value currently associated with the user. ecomm_category Category The current category visible to the user. travel_destid Destination ID The ID for the destination the user has selected. travel_originid Origin ID The ID for the user's origin location. travel_startdate Start Date The date the user wishes to start travel. travel_enddate End Date The date the user wishes to end travel. travel_totalvalue Total Value The total value of the travel the user wishes to embark on. hct_bpr Hotel Base Price The base price of the hotel the user wishes to book. hct_tpr Hotel Total Price The total price, including tax and discounts, of the hotel the user wishes to book. hct_bid Hotel Booking ID The ID for the user's booking. hct_cid Hotel Checkin Date The checkin date for the user's stay. hct_cod Hotel Checkout Date The checkout date for the user's stay. hct_los Hotel Length of Stay The total length of the user's stay. hct_pid Hotel Partner ID The partner ID for the hotel the user wishes to book. hct_pagetype Hotel Page Type The current page type visible to the user. Product Audience - Retail Variable Description ecomm_prodid Product ID One or more IDs currently visible to or selected by the user. ecomm_pagetype Page Type The current page type visible to the user. One of home, searchresults, category, product, cart, purchase, or other ecomm_totalvalue Total Value The total value currently associated with the user. ecomm_category Category The current category visible to the user. Product Audience - Travel Variable Description travel_destid Destination ID The ID for the destination the user has selected. travel_originid Origin ID The ID for the user's origin location. travel_pagetype Page Type The current page type visible to the user. One of home, searchresults, offerdetail, conversionintent, conversion, cancel, or other travel_startdate Start Date The date the user wished to start travel. Date format is YYYY-MM-DD travel_enddate End Date The date the user wishes to end travel. Date format is YYYY-MM-DD travel_totalvalue Total Value The total value of the travel the user wishes to embark on. Product Audience - Hotel Variable Description hct_base_price Hotel Base Price The base price of the hotel the user wishes to book. hct_total_price Hotel Total Price The total price, including tax and discounts, of the hotel the user wishes to book. hct_checkin_date Hotel Checkin Date The check in date for the user's stay. Date format is YYYY-MM-DD hct_checkout_date Hotel Checkout Date The checkout date for the user's stay. Date format is YYYY-MM-DD hct_length_of_stay Hotel Length of Stay The total length of the user's stay. hct_partner_hotel_id Hotel Partner ID The partner ID for the hotel the user wished to book. hct_booking_ref Obfuscated Booking Reference Number hct_pagetype Hotel Page Type The current page type visible to the user. One of home, searchresults, property, cart, purchase, cancel, or other. Vendor Documentation Tracking sales and other conversions What is UET and how can it help me? FAQs ... View more

This article describes the badge attribute data type and how to use it. In this article: Table of Contents Placeholder How it Works Before you begin, familiarize yourself with the following: Using Attributes Using Enrichments A badge is a special visitor attribute for capturing interesting behavior about a customer. Badges are the building blocks for discovering audiences. Badges represent visitor behavior patterns that are relevant to your business. A behavior is defined using attributes and rules that describe its conditions. For example, you might be interested in the behavior of visitors that frequently browse your site but do not make a purchase. In this case, the following behaviors might characterize this type of visitor: Visited - has visited the site 3 times in the last 7 days. Showed Interest - has viewed a product details page or read an article. Did Not Convert - has not purchased or signed up for a service. This pattern of behavior could be configured as a badge attribute named "Window Shopper" to identify the visitors that match its behavior. The badge attribute is available in the following scopes: Visitor. Badge Associations Badge associations allow you to quickly assign multiple badges based on other badges the visitor has earned. Typically, you would trigger a badge assignment based on a certain browsing behavior or criteria, but with badge associations you can trigger more than one badge assignment after the visitor has successfully earned the qualifying badge(s). Learn more about setting up badge associations. Enrichments Badges are assigned to and removed from visitors based on the logic of their rules.  Each new visitor is assigned a default badge named "Unbadged". This badge is automatically removed once the visitor earns a custom badge. Badges are assigned (and removed) using the following enrichments. Assign Badge Assigns the badge to a visitor when a set of conditions are met. All visitors are initially unbadged. For example, to assign the "Window Shopper" badge, it must be determined if the visitor navigated away from the site without purchasing. Attribute Name: "Window Shopper" Starting Value "Unbadged" Resulting Value "Window Shopper" Remove Badge Removes an assigned badge when the visitor no longer satisfies the conditions. For example, a "Window Shopper" badge is removed once the visitor makes a purchase. Attribute Name: "Window Shopper" Starting Value "Window Shopper" Resulting Value "Unbadged" Assign Badge from Another Badge Assigns a badge based on another badge. For example, a "Window Shopper" badge is replaced with a "Cart Abandoner" badge once the visitor abandons a cart. Of course, a visitor can have more than one badge, so a visitor can be a "Window Shopper" and a "Cart Abandoner". Attribute Name: "Cart Abandoner" Starting Value "Window Shopper" Resulting Value "Cart Abandoner" Popular Badges These are popular badges. For a more complete list of popular badges, see Popular Badges. Badge Name Description Known Visitor Assigned when we capture an important identifier of the visitor For example: Customer ID (client's ID), Customer Email, Facebook ID Possible Action to take: none, but used in an Audience to ensure the visitor is targetable with a selected vendor API These visitors are more commonly targeted via Email or Social Media Unknown Visitor Assigned when the visitor has yet to authenticate on the website Authenticate does not necessarily mean they have logged in, if a visitor comes to the site from an email and the email is in the URL then we've determined who the visitor is and they've "authenticated" Possible Action to take: display a modal to the visitor encouraging them to identify themselves These visitors are more commonly targeted via Display Ad Window Shopper A visitor who visits the site often but does not purchase For example: a visitor who has been to the site 3 times in the last 7 days, has viewed a product details page or read an article, and has not purchased or signed up for a service Possible Action to take: determine their affinity to a category and change the landing page of the next session to personalize the experience Purchaser A visitor who has converted For example: purchased a product or signed up for a service Possible Action to take: email in 2 weeks with an offer enticing to make another purchase or an email showing related items for purchase, for example if the visitor bought a baseball bat offer a baseball bag and batting gloves Possible Action: remove visitor from retargeting campaign so they are not remarketed unnecessarily Browse Abandoner A visitor who has viewed a product and did not add an item to the cart. Possible Action to take: if a Known Visitor and Facebook ID is known, send data to Facebook to retarget the brand to the visitor. Cart Abandoner A visitor who has added an item to the cart and did not purchase. Possible Action to take: if email address is known, send a personalized email with the abandoned items. Search Abandoner A visitor who has landed on the site from a search engine and has not completed a qualifying action, such as 3 page views in the visit.   ... View more

Overview A Rolling Sum is the aggregate of numerical values in a Number or Tally Attribute that are captured as entries in a Timeline. The Timeline's expiration determines which entries can be factored in during the aggregation. Example with Timeline This example uses a "Lifetime Orders" Timeline that captures Order Total values.  All entries in the Timeline count towards the Rolling Sum, essentially making it a simple Sum. The Enrichment keeps the Sum updated to account for new Timeline entries: Timeline Attribute: "Lifetime Orders" Entries Order Total ($) Jan 1 10.00 Feb 15 20.00 Mar 25 30.00 Apr 10 40.00 May 15 50.00 (Rolling) Sum is (10 + 20 + 30 + 40 + 50) = 150.00 Example with Timeline Expiration This example uses a "90-day Orders" Timeline, which uses a 90 day expiration, so only entries captured in the last 90 days will be considered for the Enrichment . As the Timeline progresses,  entries falling outside the expiration window are discarded and the final Rolling Sum is recalculated with the set of valid entries. The table below illustrates a timeline of entries (assume today is March 25). All entries, including the entry on Jan 1, are included in the Sum. Timeline Attribute: "90-day Orders" Valid Entries Order Total ($) Jan 1 10.00 Feb 15 20.00 Mar 25 30.00 Rolling Sum is (10.00 + 20.00 + 30.00) = 60.00 A few weeks later, the Jan 1 entry is discarded because it falls outside the 90 day expiration and the Rolling Sum is recalculated for the valid entries. Notice how the resulting average changes when an expired entry is excluded from the aggregate. Timeline Attribute: "90-day Orders" Expired Entries Order Total ($) Jan 1 10.00 Valid Entries Order Total ($) Feb 15 20.00 Mar 25 30.00 Apr 10 40.00 Rolling sum is (20.00 + 30.00 + 40.00) = 90.00  Add and Configure the Enrichment 1. Add a new Numner Attribute or a Tally Attribute. This Attribute will store the results of the sum. 2. Give it a Title and set its Scope. 3. Click on 'Create Enrichment' and select 'Rolling Sum Based on Timeline'. 4. From the first dropdown, select the Number or Tally that contains the numerical values you want to sum up. 5. From the next dropdown, select the Timeline where the Number or Tally is being recorded. 6. Click Finish to confirm. Then Save/Publish the changes in your profile. Usage Example In this example, you will learn how to record a Timeline of order confirmation events on the receipt page for the last 90 days and, at the same time, capture the resulting order total values. Then you will create a new Number along with the Rolling Sum Enrichment to aggregate all the order total values recorded into the Timeline. STEP 1: Add a new Number Attribute. Purpose: To store the order total values from the receipt page. Title: Order Total Scope: Current Visit Enrichment: Set this Number to "order_total" WHEN: ANY_PAGE_EVENT Attach or Create Rule: Current URL contains "receipt.html" STEP 2: Add a new Timeline Attribute and set each entry to expiry after 90 days. Purpose: To record every order confirmation event on the receipt page and capture the numerical order total values. Title: 90-day Order Timeline Scope: Visitor Entry: Update Timeline Capture Attribute Data: Order Total WHEN: ANY_PAGE_EVENT Attach or Create Rule Condition: Current URL contains "receipt.html" Entry: Set Expiration of Timeline events Set each event in this Timeline to expire after "90" days STEP 3: Add a new Number and create the Set Rolling Sum Based on Timeline Enrichment. Purpose: To crunch numbers and store the final rolling sum. Title: 90-day Order Total Scope: Visitor Enrichment: Set Rolling Sum based on Timeline Set this Number to the Rolling Sum of Number "Order Total" captured in timeline "90-day Order Timeline" Results Go to API Sampler in your profile and submit a query to find out how many entries were logged into the Timeline and to determine the final rolling sum. Look for the Title you assigned to the Number/Tally and the Timeline Attribute. Assuming there are two entries in the 90-day Order Timeline, the API Sampler will display the results like so: Similarly, here's the final sum stored in the 90-day Order Total Number: ... View more

Overview This Enrichment is available to both Number and Tally Attributes. The Rolling Average is the arithmetic mean of numerical values captured over time. These values come from Number and Tally Attributes that are all collected as entries in a Timeline. The Timeline's expiration determines which entries can be factored into the final average. Example with Timeline This example uses a "Lifetime Orders" Timeline that captures the Order Total values. All entries in the Timeline count towards the Rolling Average, essentially making it a simple Average. The Enrichment keeps the average updated to account for new Timeline entries.  Timeline Attribute: "Lifetime Orders" Entries Order Total ($) Jan 1 10.00 Feb 15 20.00 Mar 25 30.00 Apr 10 40.00 May 15 50.00 (Rolling) Average is (10.00 + 20.00 + 30.00 + 40.00 + 50.00) ÷ 5 = 30.00 Example with Timeline Expiration This example uses a "90-day Orders" Timeline, which uses a 90 day expiration, so only entries captured in the last 90 days will be considered for the Enrichment. As the Timeline progresses, entries falling outside the expiration window are discarded and the final Rolling Average is recalculated with the set of valid entries. The table below illustrates a timeline of entries (assume today is March 25). All entries, including the entry on Jan 1, are included in the arithmetic mean. Timeline Attribute: "90-day Orders" Valid Entries Order Total ($) Jan 1 10.00 Feb 15 20.00 Mar 25 30.00 Rolling Average is (10.00 + 20.00 + 30.00) ÷ 3 = 20.00 A few weeks later, the Jan 1 entry is discarded because it falls outside the 90 day expiration and the Rolling Average is recalculated for the valid entries. Notice how the resulting average changes when an expired entry is excluded from the aggregate. Timeline Attribute: "90-day Orders" Expired Entries Order Total (in $) Jan 1 10.00 Valid Entries Order Total (in $) Feb 15 20.00 Mar 25 30.00 Apr 10 40.00 Rolling Average is (20.00 + 30.00 + 40.00) ÷ 3 = 30.00  Add and Configure the Enrichment 1. Add a new Metric Attribute or a Tally Attribute. This Attribute will store the resulting average. 2. Give it a Title and set its Scope. 3. Click on Add Enrichment and select Set Rolling Average Based On Timeline. 4. From the first dropdown, select the Attribute that has the values you want to average out. 5. From the next dropdown, select the Timeline where the Attributed is being captured. 6. Click Finish to confirm. Then Save/Publish the changes in your profile. Usage Example In this example, you will learn how to record a Timeline of order confirmation events that have occurred in the last 90 days and, at the same time, capture the resulting order total values. Then you will create a new Metric along with the Rolling Average Enrichment to average out the order totals.  STEP 1: Create "Order Total" as a new Metric Attribute. Purpose: To store the order total values from the receipt page. Title: Order Total Scope: Current Visit Enrichment: Set this Metric to "order_total" WHEN : ANY_PAGE_EVENT Attach or Create Rule: Current URL CONTAINS "receipt.html"   STEP 2: Create "90-Day Order Timeline" as a Timeline Attribute with a 90 day expiration. Purpose: To record every order confirmation event on the receipt page and capture the numerical order total values. Title : 90-day Order Timeline Scope : Visitor Entry: Update Timeline Capture Attribute Data : Order Total WHEN : ANY_PAGE_EVENT Attach or Create Rule Condition: Current URL contains "receipt.html" Entry: Set Expiration of Timeline events Set each event in this Timeline to expire after "90" days      STEP 3: Create "90-Day Order Average" as a new Metric Attribute with the Set Rolling Average Based on Timeline Enrichment. Purpose: To store the average value of orders from the last 90 days. Title: 90-day Order Average Scope: Visitor Enrichment: Set Rolling Average based on Timeline Set this Metric to the Rolling Average of Metric "Order Total" captured in timeline "90-day Order Timeline"   Results  Go to API Sampler in your profile and submit a query to find out how many entries were logged into the Timeline and also to determine the final average. Look for the Title you assigned to the Metric/Tally and the Timeline Attribute. Assuming there are two entries in the 90-day Order Timeline, the API Sampler will display the results like so: Similarly, here's the final average stored in the 90-day Order Average Metric: ... View more

Overview Description: Calculates the elapsed time between two events with unique timestamps. Example: Days elapsed since the last purchase made by a visitor. (Usage Example below). Things to Remember: Only Date Attributes are available to this Enrichment. The Enrichment calculates the absolute difference of the dates, which means the resulting Number is always non-negative. Elapsed time can be expressed in one of the following: Minutes Hours Days Weeks Months Add and Configure the Enrichment 1. Add a new Number Attribute. Give it a Title and select its Scope. The Notes field is optional but recommended. 2. Click on 'Create an Enrichment' and select "Set Difference Between Two Dates". 3. Select a Date attribute from each of the two Attribute dropdowns. It is NOT required to select them in a chronological order. 4. Select a unit of measurement. The default is 'Minutes' but you can change it to Hours, Days, Weeks, or Months. 5. Select a trigger from the WHEN dropdown. New Visitor: Enrichment will occur when the visitor is new to your site. New Visit: Enrichment will occur on a new visit by a visitor. Any page event: Enrichment will occur anytime a page event occurs. If you're not certain which selection to make, choose this one. Visit ended: Enrichment will occur when a visit ends. 6. Attach an existing Rule or create a new Rule for additional triggers. 7. Save the settings and Save/Publish the changes. Usage Example Here, you will learn how to calculate the days elapsed since a visitor last purchased anything on your site. You will configure the Enrichment to deduct the date of last purchase from the date of current visit. Remember, the chronology of dates is not important because the difference is always absolute. Step 1: Add a new Date attribute. Create the 'Capture Date' Enrichment to capture the timestamp whenever the visitor lands on the order completion page. Title: Last Purchase Date Scope: Visitor WHEN: Any page event Attach/Create Rule: Current URL contains (ignore case) "receipt.html" Step 2: Add a new Number Attribute and create this Enrichment. Select 'Visit Start' Date (preloaded Attribute) and the Last Purchase Date (see Step 1) from the two dropdowns. Title: Days Since Last Purchase Scope: Visitor Date Attribute in first drop-down: Visit Start Date Attribute in second drop-down: Last Purchase Date Difference in: Days WHEN: New Visit Step 3: Save the settings. Then Save/Publish your profile. Results When the Enrichment runs, it will deduct the date of "Visit Start" from the date of 'Last Purchase'. The difefrence Number can be leveraged in Rules, Audiences and other Attributes for taking suitable action on habitual and occasional visitors. ... View more

This article describes the number attribute and how to use it in the Customer Data Hub product. In this article: How it Works Before you begin, familiarize yourself with the following: Using Attributes Using Enrichments A number attribute stores a numerical property of browsing metrics such as visits, page views, and events. Common examples include Lifetime Value, Order Total Transaction, or Days Since Last Purchase. The number attribute is available in the following scopes: Event, Visit, Visitor. Number Enrichments Increment or Decrement Number Enrichment This enrichment modifies a number with a positive value (increment) or a negative value (decrement). The modifying value can be a separate number attribute or a constant value. For example, to calculate the Lifetime Total Value (LTV) of a visitor's orders use this enrichment to increment the attribute with the value of the order_total attribute each time the purchase event occurs. Attribute Name: Lifetime Total Value Initial 121.78 Enriched With order_total: 220.00 Result 341.78 Set Ratio Set the quotient of two numbers as a new ratio number. For example, to calculate the Average Cart Items Per Order use this enrichment to set the ratio of the Total Cart Items Purchased attribute to the Total Orders Completed attribute. Attribute Name: Average Cart Items Per Order Initial   Enriched With Total Cart Items Purchased: 48.00 Total Orders Completed: 3.00 Result 16.00 Set Product Set the product of two numbers as a new number. For example, to calculate the coupon_discount_amount , use this enrichment to multiply the order_subtotal by the coupon_discount_percent . Attribute Name:  coupon_discount_amount Initial   Enriched With order_subtotal: 42.00 coupon_discount_percent: 0.05 Result 2.10 Set Difference Set the difference of two numbers as a new number. Attribute Name: order_subtotal Initial 42.00 Enriched With order_subtotal: 42.00 coupon_discount_amount: 2.10 Result 39.90 Set Sum Set to the sum of two numbers. For example, set order_total to the sum of order_subtotal and order_tax_amount . Attribute Name: order_total Initial   Enriched With order_subtotal: 39.90 order_tax_amount: 3.29 Result 43.19 Set Number Set the number to a specific number. For example, set Last Purchase Amount to the value of order_total whenever the purchase event occurs. Attribute Name: Last Purchase Amount Initial   Enriched With order_total: 43.19 Result 43.19 Set Difference Between Two Dates Calculates the elapsed time between two events.  Elapsed time can be expressed as one of the following: Minutes Hours Days Weeks Months The difference is always stored as a positive value, so the dates can be set in any order. For example, to calculate Days Since Last Purchase as the difference in days between Last Purchase Date and Current Visit Date.  While date attributes are stored as Unix timestamps, these examples use formatted dates for readability. Attribute Name: Days Since Last Purchase Initial   Enriched With Last Purchase Date: "2018/10/30" Current Visit Date:  "2019/11/01" Result 367 Set Rolling Average Based on Timeline The rolling average is the arithmetic mean of numerical values captured over time. These values come from number and tally attributes that are collected as entries in a timeline. The timeline's expiration determines which entries can be factored into the final average. If there is not an expiration date, it is a simple average solution. For detailed information, see Number/Tally Enrichment: Set Rolling Average Based on Timeline. Attribute Name: Average Order Value Initial   Enriched With [20.00, 30.00, 40.00, 50.00] Result 35.00 Set Rolling Sum Based on Timeline A rolling sum is the aggregate of numerical values in a number or tally attribute that are captured as entries in a timeline. The timeline's expiration determines which entries can be factored in during the aggregation. For detailed information, see Number/Tally Enrichment: Set Rolling Sum Based on Timeline. Attribute Name: Total Order Value Initial   Enriched With [10.00, 20.00, 30.00, 40.00, 50.00] Result 150.00 Set Number to the Number of Entries in Timeline Set the number to the number of entries in a timeline. Attribute Name: Total Order Count Initial   Enriched With [10.00, 20.00, 30.00, 40.00, 50.00] Result 5.00 Set Number to Tally Value Set the number to a specific value within the tally. Specify the tally attribute and the name of the entry in the tally. For example, a tally for Site Category Views might have an entry for "Shoes". Attribute Name: Shoe Category View Count Initial   Enriched With Site Category Views: {"Shoes": 42} Result 42 Set Number to the Count of Items in Tally Set the attribute to the number of entries in a tally. For example, a tally for Site Category Views might have three entries in it. Attribute Name: Number of Categories Viewed Initial   Enriched With {   "Shoes": 42,   "Shirts": 11,   "Pants": 8 }  Result 3.00 Set Number to the Count of Items in Set of Strings Set the number to the count of items in a set of strings. For example, a set of strings Active Browser Types might have 3 entries. Attribute Name: Number of Active Browser Types Initial   Enriched With ["Firefox", "Safari", "Chrome"] Result 3.00 Set Number to Tally's Rolling Max Based on a Timeline Set the number to the rolling maximum of another number in a tally captured within a timeline. Attribute Name: Highest Order Value Initial   Enriched With [10.00, 20.00, 30.00, 40.00, 50.00] Result 50.00 Set Number to Change in Number Set this attribute to the difference between it and another attribute since the last event. For example, use this enrichment to capture the difference between a previous order amount and the current order amount. To set an attribute named Change in Order Value, set it to the change in order_subtotal since the previous order.  Attribute Name: Change in Order Value Initial 30.00 Enriched With order_subtotal: 42.00 Result 12.00 Set Number to Change in Date Set this attribute to the change in value of the selected value between this event and the last event. For example, use this enrichment to capture the change in months of the Last Purchase Date date attribute each time a purchase occurs.  The change in date can be expressed as one of the following: Minutes Hours Days Weeks Months Attribute Name: Months Since Last Purchase Initial Enriched With Last Purchase Date (last event): "10/31/2019" Last Purchase Date (this event):  "12/31/2019" Result 2 (months) Set to the Number of Items in an Array Set to the number of items in an array. For example, to store the number of products in the cart, use this enrichment to capture the number of items in the cart_product_id array. Attribute Name: num_cart_items Initial   Enriched With product_id: ["prod123", "prod456"] Result 2.00 ... View more

This article describes the visitor ID attribute and how to use it. In this article: Table of Contents Placeholder How it Works Before you begin, familiarize yourself with the following: Using Attributes Using Enrichments Visitor Stitching Identifying your visitors is a critical step in leveraging the power of AudienceStream.  When certain qualifying visitor events occur, such as a user registering or completing a purchase, there is an opportunity to identify that visitor using an event attribute such as customer_email or customer_id . When one of these identifying attributes is provided in the data layer across multiple sessions, AudienceStream can combine the visitor attributes from those sessions into one master visitor profile using a process called visitor stitching. However, for visitor stitching to work properly you must carefully choose a visitor ID attribute and create a rule to determine when to identify a visitor. The value is a unique identifier such as an email address or customer ID.   Visitor stitching is disabled by default. Contact your account manager to enable it. Learn more about visitor stitching. The Visitor ID attribute is available in the following scope: Visitor. System Requirements A visitor ID must meet the following system requirements: Length – Values must be between 6 and 255 characters in length. Non-repeating – Values must contain at least 3 different characters e.g. a 10-character identifier with only 2 different characters ( "a1a1a1a1a1" ) is invalid. UTF-8 character sets are supported. The system automatically validates these requirements, so you do not need these rule conditions in your visitor ID attribute configuration. Best Practices A visitor ID should follow these best practices: Uniqueness – Each visitor ID value should be unique for each visitor. Strong identifiers - Only use values that could be associated with a single visitor and are not likely to change, such as an email address or customer ID. Weak identifiers - Avoid values that cannot be guaranteed to be unique for each visitor or that have a high likelihood of changing over time, such as first and last name, username, or phone number. Case Sensitive – Values are case sensitive, so convert them to lower-case. For example, a single email address can be written with case variations such as FirstLast@example.com and firstlast@example.com , which would be treated as two different ID's in AudienceStream. Vendor Identifiers Third-party vendors that track visitor activity also maintain a unique identifier for each user. These values can also be used as the visitor ID attribute in AudienceStream. To ensure uniqueness across all third-party vendors it's a best practice to create a separate visitor ID attribute for each vendor you work with. For example, if your visitors have accounts with Facebook and Twitter, create a visitor ID attribute for each vendor, such as "Facebook ID" and "Twitter ID". Review the guide on visitor stitching to ensure you create the most accurate visitor ID attribute possible. Visitor ID Enrichments Set Visitor ID This enrichment stores a unique identifier for a visitor. For example, when a user registers or signs up, your system might generate an internal ID that is added to the data layer as customer_id . Use this enrichment to set a visitor ID to customer_id when the user_register event occurs. Once a visitor ID is set it cannot be updated. Attribute Name: customer_id Starting Value "" Enriched With customer_id: "123456890" WHEN: User Register event occurs (rule) Resulting Value "1234567890" ... View more

This article explains how to use the boolean attribute data type.  Booleans are used to store true or false values. In this article: How it Works Before you begin, familiarize yourself with the following: Using Attributes Using Enrichments A boolean attribute (a.k.a flag) is used to store the true or false value of a condition. For example, a boolean could store whether or not a visitor had added items to their cart or visited a specific section of site.  The boolean attribute is available in the following scopes: Event, Visit, Visitor. Boolean Enrichments Set Boolean Use this enrichment to set the boolean attribute to true or false. This example shows how to know if a visitor has added an item to his/her cart using a boolean attribute named "Did Add to Cart". Initialize the attribute by settting it to false at the beginning of each visit, then set it to true whenever the cart_add event occurs. Create two enrichments to achieve this: Set to: false WHEN: New Visit Set to: true WHEN: Any event Rule: tealium_event equals "cart_add" Attribute Name: Did Add to Cart Starting Value "" Enriched With true Resulting Value true   ... View more

This article describes the tally attribute and how to use it in the Customer Data Hub. In this article: Table of Contents Placeholder How It Works Before you begin, familiarize yourself with the following: Using Attributes Using Enrichments The tally attribute maintains a collection of key/value pairs, called entries, that count the occurrences of named items across many events. Key represents the name of the item that occurred, for example the value of the product_category attribute "Shoes". Value represents the number of times it occurred For example, to keep track of the product categories that a visitor purchases from, use a tally named "Product Category Purchases" and enrich it with the names of product categories found in the event attribute product_category when purchase events occur. Over time the tally will provide valuable information about the visitor's buying habits. Tally Favorite By default, each tally attribute generates a corresponding string attribute that automatically captures the name of the tally entry with the highest value. This string attribute has the same name as the tally, but with the word "(favorite)" appended. For example, a tally named "Product Categories Purchased" would also have a string attribute named "Product Categories Purchased (Favorite)". Scope The tally attribute is available in the following scopes: Visit and Visitor. Example The following table illustrates the example of a tally named "Product Category Purchased", which counts the number of times each product category was purchased from. This tally automatically populates a string attribute with the name of the entry containing the highest value. Tally Attribute: "Product Category Purchased" Tally Key Tally Value "Shoes" 1 "Pants" 3 "Shirts" 7 "Shorts" 2 String Attribute: "Product Category Purchased (Favorite)" "Shirts" Tally Attribute Enrichments Increment Tally Increment a number within a tally based on the value of another attribute. For example, to track the number of times each product category is viewed, use a tally named "Product Category Viewed" and enrich it with the product_category attribute. The values of product_category become entries in the tally. Attribute Name: "Product Category Viewed" Starting Value {"Shoes": 7, "Pants": 1, "Shirts": 3} Enriched With product_category:"Shoes" Resulting Value {"Shoes": 8, "Pants": 1, "Shirts": 3} Increment Tally Value Increment a tally entry based on a custom name with a custom value or another attribute value. For example, use a tally named "Product Category Searched" and enrich it with a hard-coded value of "Did Not Search" when a search has not occured (a condition likely based on a boolean attribute that keeps track of searches). Since the name "Did Not Search" would not naturally occur in a product_category attribute, this enrichment is used to add the custom entry. Attribute Name: "Product Category Searched" Starting Value {"Shoes": 7, "Pants": 1, "Shirts": 3} Enriched With Custom Key: "Did Not Search" Custom Increment: 1 Resulting Value {"Did Not Search": 1, "Shoes": 7, "Pants": 1, "Shirts": 3} Increment Tally by Tally Increment the values in a tally by the values found in another tally. Attribute Name: "Product Category Purchased (Lifetime)" Starting Value {"Shoes": 7, "Pants": 1, "Shirts": 3} Enriched With {"Shoes": 1, "Shirts": 2, "Dresses": 1} Resulting Value {"Shoes": 8, "Pants": 1, "Shirts": 5, "Dresses": 1} Increment Tally by Set of Strings Increment the entries in a tally based on the entries in a set of strings. For example, use a tally named "Product Category Searched (Lifetime)" to track the product categories searched per visit, and enrich it with a set of strings named "Product Categories Searched (Visit)" at the end of each visit. Attribute Name: "Product Category Searched (Lifetime)" Starting Value {"Shoes": 7, "Pants": 1, "Shirts": 3} Enriched With Product Categories Search (Visit): {"Shoes", "Pants", "Hats"} Resulting Value ["Shoes": 8, "Pants": 2, "Shirts": 3, "Hats": 1} Set Rolling Average Based on Timeline The rolling average is the arithmetic mean of numerical values captured over time. These values come from number and tally attributes that are all collected as entries in a Timeline. The timeline's expiration determines which entries can be factored into the final average. If there is no expiration date, it is a simple average solution. For a detailed example, see Number/Tally Enrichment: Set Rolling Average Based on Timeline. Attribute Name: "Average Product Category Purchase Amounts" Starting Value {} Enriched With Timeline entry: {"Shoes": 150.00, "Pants": 75.00, "Shirts": 30.00} Timeline entry: {"Pants": 75.00, "Shirts": 42.00} Timeline entry: {"Shoes": 110.00, "Shirts": 18.00 "Hats": 25.00} Resulting Value {"Shoes": 130.00, "Pants": 75.00, "Shirts": 30.00, "Hats": 25.00} Set Rolling Sum Based on Timeline A rolling sum is the aggregate of numerical values in a number or tally, attributes that are captured as entries in a timeline. The Timeline's expiration determines which entries can be factored in during the aggregation. For detailed information, see Number/Tally Enrichment: Set Rolling Sum Based on Timeline. Attribute Name: "Average Product Category Purchase Amounts" Starting Value {} Enriched With Timeline entry: {"Shoes": 150.00, "Pants": 75.00, "Shirts": 30.00} Timeline entry: {"Pants": 75.00, "Shirts": 42.00} Timeline entry: {"Shoes": 110.00, "Shirts": 18.00 "Hats": 25.00} Resulting Value {"Shoes": 260.00, "Pants": 150.00, "Shirts": 90.00, "Hats": 25.00} Set Tally by Corresponding Arrays Set the tally to the values defined in two corresponding arrays. For example, use a tally named "Product Category Quantity Purchased" to capture the quantity of products purchased and enrich it with the two arrays product_category and product_quantity when a purchase event occurs. Attribute Name: "Product Category Quantity Purchased" Starting Value   {} Enriched With product_category: ["Shoes", "Pants", "Shirts"] product_quantity: [1, 1, 3] Resulting Value {"Shoes": 1, "Pants": 1, "Shirts": 3} Remove Tally Remove tally based on a set of conditions. The remove tally enrichment can be used to reset a tally. For example, if you have been tracking visitor's product category searches, you might clear that tally once an order is placed. Attribute Name: reset tally to zero Starting Value {"Shoes": 1, "Pants": 3} Enriched With Purchase event occurs Resulting Value {} Remove an Entry in a Tally Remove an entry in a tally based on a set of conditions. For example, use a tally named "Product Category Searched" to track a visitors product searches (and potential purchases) then use this enrichment to remove the tally entries that match items in a purchase. Attribute Name: "Product Category Searched (Not Purchased)" Starting Value {"Shoes": 7, "Pants": 1, "Shirts": 3, "Jeans": 10} Enriched With product_catgory : "Shoes" Resulting Value ["Pants": 1, "Shirts": 3, "Jeans": 10] Increment by 1 for Each Item in an Array Increment by one (1) for each item in an array. For example, use a tally named "Product Category Purchased" and enrich it with the array attribute product_category when a purchase event occurs. Attribute Name: "Product Category Purchased" Starting Value {"Shoes": 1, "Pants": 1, "Shirts": 3} Enriched With product_category : ["Pants", "Ties"] Resulting Value {"Shoes": 1, "Pants": 2, "Shirts": 3, "Ties": 1]   ... View more

An enrichment is the application of business rules in setting attribute values. An enrichment transforms an attribute from a static value to a dynamic one.  By introducing business rules to your attributes you give them context and more meaning. These enriched attributes then become the building blocks for rest of your solution. In this article: Table of Contents Placeholder Managing  Enrichments Adding an Enrichment Enrichments are added to attributes as a way to customize their values. Find the attribute you want to enrich and follow these steps: Click Add Enrichment and select the desired enrichment. The settings vary depending on the kind of enrichment. See enrichment details below for additional information. Select WHEN to trigger the enrichment. This controls the timing of the enrichment. New Visitor –  occurs the first time a visitor comes to your site. New Visit – occurs on a new visit by a visitor. Any Event  –  occurs on any event. Visit Ended – occurs when a visit ends, based on the following time of inactivity: Web sessions: 30 minutes (10 minutes if only one event is received) Mobile App sessions: 2 minutes Omnichannel sessions: 1 minute (Optional) Select an existing Rule condition or create a new rule. Linked Enrichments When two (2) or more enrichments have a dependency on the same attribute, they become "linked enrichments". The following example shows the Enrichments applied to Visit Start and Visit End, the two preloaded attributes The enrichment in the Visit Start attribute uses the Visit End attribute and vice versa. Because each enrichment is linked to the other by an attribute, they are considered linked enrichments. Read more: EventStream Attribute and Enrichment Diagram AudienceStream Attribute and Enrichment Diagram Usage Examples Increment or Decrement Number – "Lifetime Order Total (LTV)" This enrichment can modify a number with a positive value (increment) or a negative value (decrement). This value can come from another attribute or be set as a static number. Use Case Attribute: Lifetime Value (LTV) Scope: Visitor Data Type: Number Knowing the amount spent across all orders from a visitor is a valuable piece of information. This data can be used for many purposes, such as to offer promotional deals or to assign a badge to visitors whose spending exceeds a certain threshold. Since the value of this attribute will persist for the lifetime of the visitor, it will be visitor-scoped. This enrichment has the following requirements: an event attribute to identify when a purchase is made, for example:  page_type ="purchase" an event attribute for the dollar amount of the purchas, for example:  order_total ="123.45" To configure this enrichment: Create a visitor attribute with the number data type, titled "Lifetime Order Total (LTV)" Add the "Increment or Decrement Number" enrichment Select order_total from the drop-down list. Select Any Event from the WHEN drop-down list. Create a new rule titled "Order Thank You Page" with the following condition:   page_type EQUALS " purchase" Set Difference Between Two Dates – "Days Since Last Purchase" This enrichment calculates the elapsed time between two events and stores the numeric value in one of the following units: minutes, hours, days, weeks, or months. Use Case Attribute: Days Since Last Purchase Scope: Visitor Data Type: Number This enrichment will calculate the number of days since a visitor made a purchase. The resulting value is always a positive number. This enrichment has the following requirements: an event attribute to identify when a purchase is made, for example:  page_type ="purchase" an visitor attribute to capture the date of a purchase event To configure this enrichment: Create a visitor attribute with the number data type titled "Last Purchase Date". Select Any Event from the WHEN drop-down list. Create a new rule (if it doesn't already exist) titled "Order Thank You Page" with the following condition: page_type EQUALS "purchase" Create a visitor attribute with the number data type titled "Days Since Last Purchase". Add the "Set Difference Between Two Dates" enrichment. Set the two (2) dates to: "Visit start" (built-in attribute) and "Last Purchase Date". Set the units to "Days". Select New Visit from the WHEN drop-down list. Split String (A/B Testing – "Split Test Group" This enrichment defines visitor group names and assigns them to an attribute based on a percentage distribution. The names (or values) of your segments can come from another string attribute or from a custom value. This enrichment is helpful in running A/B tests or targeting groups of users. The group distributions are calculated based on a random number generator. The enrichment does not monitor the current ratio of segments prior to assigning a value, so for smaller samples you may see ratios that do not exactly match the percentages you set. However, as the number of assignments increases, the ratio of assignments will gradually match the percentages you set. For example, if you set up three segments with distributions of 50%, 30%, and 20%, within a small sample set you might see ratios of 48%, 34%, and 18%. However, as more visitors get assigned into the segments, the ratio values will approach the expected values. Use Case Attribute: Split Test Group Scope: Visit/Visitor Data Type: String To test a new campaign on a small segment of your visitors, presumably before rolling it out for all visitors, you use the split string enrichments to assign a small percentage of your visitors into the "Action" group. This identified segment of visitors can then be built into an audience for which you can take actions. For this example we will create the following distribution of segments: 85% - "Control" - the control group that will not be part of the test 15% - "Variation1" - the group to be included in the test To configure this enrichment: Create a Visit/Visitor attribute with the String data type, titled "Split Test Group" Add the "Split String" Enrichment For each group, set a name and a percent Select New Visit from the WHEN drop-down list Now you can use this attribute in a rule to include the relevant visitors in an audience. The rule logic might be: "Split Test Group" EQUALS "Variation1". Store Array as Set of Strings – "Purchase Categories" The Store Array as Set of String enrichment saves the values from an array of strings attribute into a set of strings attribute. This Enrichment will not create a perpetual set. Meaning, you cannot append to a set of string using this enrichment, it will always overwrite the value. To preserve a set of strings and append new values you must use the Update Set of String By Set of Strings Enrichment. Use Case Attribute: Purchase Categories Scope: Visit Data Type: Set of Strings Starting with an event attribute of the data type Array of Strings called product_category , populated on purchase events to contain the category names of the products purchased.  To store this as a Visitor/Visit attribute called "Purchase Categories", it must be converted to a Set of Strings. Then, on each purchase event, the product_category values get appended to the "Product Categories Purchased" attribute via enrichments. Array of Strings (product_category) Set of Strings (Product Category Purchased) ["Pants", "Shirts"] "Pants", "Shirts" ["Boots", "Belts", "Belts"] "Boots ", "Belts" Update Set of Strings by Set of Strings – "Lifetime Purchase Categories" This enrichment appends the values from one Set of Strings attribute into another Set of Strings attribute.  This allows you to store the values that occur in one set (and that change from event to event) into a second set that persists for the life of the visitor. In this table Set A is overwritten with new values for each event and the the enrichment is copying those values into Set B where the master list grows. We recommend pairing this enrichment with Store Array as Set of Strings Enrichment so that the resulting Set can be preserved before it is overwritten by incoming values. Set A (Event) Set B (Visitor) " Pants ", " Shirts " " Pants ", " Shirts " "Shoes", "Pants" " Pants ", " Shirts ", "Shoes" "Shirts", "Shirts", "Watches" " Pants ", " Shirts ", "Shoes", "Watches" Use Case Attribute: Lifetime Purchase Categories Scope: Visitor Data Type: Set of Strings To maintain an accumulated set of product categories purchased from you will have one Event Array of Strings attribute and two Visit/Visitor Set of Strings attributes: one to capture the views as they happen and one to capture all historical views. This enrichment has the following requirements: an event attribute to identify when a purchase is made eg. page_type="purchase" an Array of Strings event attribute to identify product categories during a purchase, for example: product_category=["Boots", "Belts"] a Set of Strings Visit attribute to capture product categories purchased for the visit a Set of String Visitor attribute to capture all product categories purchased To configure this Enrichment: Create an event attribute with the Array of Strings data type named "product_category" Create a visit attribute with the Set of Strings data type, named "Product Category Purchased" Add the "Store Array as Set of Strings" enrichment Select the attribute "product_category" Set the WHEN to "Any Event" Set the Rule to the "Purchase Page" (page_type EQUALS "purchase") Create a visitor attribute with the Set of Strings data type, named "Lifetime Product Category Purchased" Add the "Update Set of Strings by Set of Strings" enrichment Select the attribute "Product Category Purchased" Set the WHEN to "Visit Ended" Set Rolling Average Based on Timeline – "90-Day Order Average" This enrichment calculates the rolling average (arithmetic mean) of numeric values captured in a timeline attribute. This example uses a "90-Day Orders" timeline to capture order total values over the last 90 days. As the Timeline progresses, entries falling outside the expiration window are discarded and the final rolling average is recalculated with the set of valid entries. This example also applies to the Set Rolling Sum Based on Timeline enrichment. The table below illustrates a timeline of entries (assume today is March 25). All entries, including the entry on Jan 1, are included in the arithmetic mean. Timeline Attribute: "90-Day Orders" Valid Entries Order Total ($) Jan 1 10.00 Feb 15 20.00 Mar 25 30.00 Rolling Average is (10.00 + 20.00 + 30.00) ÷ 3 = 20.00 A few weeks later, the Jan 1 entry is discarded because it falls outside the 90 day expiration and the rolling average is recalculated for the valid entries. Notice how the resulting average changes when an expired entry is excluded from the aggregate. Timeline Attribute: "90-Day Orders" Expired Entries Order Total (in $) Jan 1 10.00 Valid Entries Order Total (in $) Feb 15 20.00 Mar 25 30.00 Apr 10 40.00 Rolling Average is (20.00 + 30.00 + 40.00) ÷ 3 = 30.00  Use Case Attribute: 90-Day Order Average Scope: Visitor Data Type: Number Starting with a timeline attribute to capture order totals from the  last 90 days,  you will create a new visitor attribute using the Rolling Average enrichment to store average the order totals.  This Enrichment has the following requirements: an Event String attribute to identify when a purchase is made, for example: page_type="purchase" an Event Number attribute for the dollar amount of the purchase, for example: order_total="123.45" a Visitor Timeline attribute to capture order totals for 90 days an Visitor Number attribute to capture the average of order totals To configure this enrichment: Create a Visitor Timeline attribute named "90-Day Order Timeline". Click Create An Entry > Set Expiration and set it to "90 days". Click Create An Entry > Update Timeline and set the following: Record: Time of event received Capture data: order_total WHEN: Any Event Rule: page_type EQUALS "purchase" Create a Visitor Number attribute named "90-Day Order Average" Add the "Set Rolling Average Based On Timeline" enrichment with "order_total" and "90-Day Order Timeline" selected.  ... View more

If you are using EventStore/EventStream Legacy (ESL) to export live events and data, we recommend upgrading to EventStore. EventStore is powered by the Tealium Collect tag and offers many benefits over ESL. In this article: Table of Contents Placeholder Why Upgrade from ESL to EventStore? There are several reasons to switch to EventStore: ESL is deprecated The ESL feature is deprecated. This means that there will be no further updates or improvements to it. The ESL tag is no longer be available in the tags marketplace. Ability to create Filtered Event Feeds Filtered feeds contain events that matter the most to you. Data from every event feed is compressed in a gzip file and made available for download. This makes it easy to export data from events you select without having to download extraneous data. The downloaded JSON file will have a .gz extension as of August 4, 2017. All files downloaded before August 4, 2017 will have the .gzip extension. Learn more about this change here. Cleaner data structure Event data collected by EventStore is structured in a flattened JSON format, as opposed to the legacy space-delimited format. The old format combined the data points in your data layer into one long string, which you then had to parse. The new format provides these data points as individual key/value pairs, which allows you to easily view and access the data. The the new structure is better organized and more easily ingested by other Tealium products. More frequent uploads to Tealium's S3 bucket Events that you feed to EventStore are uploaded to Tealium's S3 bucket once every hour or when at least 5 MB of compressed files are queued, whichever comes first. ESL only uploads data to the bucket once per day. Compatibility with EventDB You cannot feed events directly to EventDB without first sending them to EventStore. The data structure of EventDB is similar to that of the new EventStore. In contrast, t he legacy data structure is space-delimited, which is not fit for use with EventDB. Legacy vs New: At a Glance EventStore Feature Legacy New Tag in charge of fetching live events EventStore Tealium Collect Ability to create and export filtered event feeds ✘ ✔ Compatible with EventDB ✘ ✔ Frequency of upload to Tealium's S3 bucket Once a day Once per hour File format available for download log file (*.tgz) compressed (*.gz) Structure of event data space-delimited (unstructured) flattened JSON (structured) Upgrading from ESL to EventStore Use the following steps to upgrade from ESL to EventStore: Request your account or deployment manager to enable EventStore/EventDB for your account   and to provide  with the server URL for the tag. Add and configure the Tealium Collect Tag. Once the Tag is up and running, it will start feeding data from your site. Click Delete to delete or disable the tag o r delete the  legacy EventStore/EventStream tag  in the same profile. Confirm that the Collect Tag is working properly before you delete or deactivate ESL, as you cannot add the ESL tag back from the tag marketplace. When complete, the Current Published Locations should display Unpublished. Save/Publish the changes to your profile. Go to the Live Events tab in the matching AudienceStream profile. Click to open the event feeds of your choice and use the slider to enable EventStore. You can select "All Events" or choose only the filtered event feeds that are important to you and your organization. Getting the S3 Access Key for EventStore If you have the access key for ESL, it will not work for EventStore. You must get a new Amazon S3 access key. For additional information, contact your account manager. ... View more

Attributes are the foundation of your implementation and are used to help you understand your customers' behavior and interaction with your brand. In Tealium iQ Tag Management, attributes are used to define data associated to the properties of a visitor, the characteristics of a visitor's session, and any event data collected in real-time. Common examples of attributes include Email Address, Member ID, Product Category, Date of Last Visit, and Active Browser. This article provides an overview of how attributes are used and basic steps to add, duplicate, or remove an attribute. In this article: Attribute Properties Attributes are the building blocks of your solution. They define the data that flows from your sources of data through to your vendor integrations. They are used in rule definitions, audience creation, and connector settings. Attributes have the following properties, which are set when you define them: Scope, Data Type, Enrichment, and Rule. Scope Scope refers to how long an attribute persists in real-time. The following table lists supported scopes: Scope Description / Examples Uses Event Attributes associated with individual events that describe the page, content, and real-time actions being taken by a customer. Examples: Page Name, Product Price, Event Name, Order Total, etc. Attribute Sources Event attributes are sourced from the following values: Universal Variable Universal Data Object Javascript Page Variable Global JavaScript variable (browser) HTML Metadata Metadata tag (browser) First-Party Cookie Browser cookie Querystring Parameter Current page's URL querystring (browser) Visit Attributes about a particular visit (or session). Data persists for the length of the visit. Examples: Visit Duration, Browser Used, Referring URL, and Carted Products. These attributes represent visitor activity from the current session on a single device. Visit attributes persist for the length of the session. See Session Length  for more detail. Visitor Attributes about a particular visitor across all visits. Examples: Email Address, Member ID, Lifetime Order Total, and Category Views. This data follows a visitor from session to session and across different devices. Visitor data persists even after the current visit ends. Omnichannel For importing offline data via the Omnichannel service. This scope does not require a data type. Omnichannel attributes are defined when you define your file imports. Session Length In AudienceStream, session length is set based on the platform of the events: Web - 30 min (10 min if one event and no follow-up events) Mobile App - 2 min Omnichannel - 1 min File Import - 1 min Collect API - 30 min The platform is based on the reserved attribute named platform according to the following values: Web - platform is set to web or not set. Mobile - platforn is set one of android|ios|win|bb10|native_mobile . To customize the session length set the data layer variable   _dc_ttl_ to a value in milliseconds on the first event of a session. The session length cannot be changed once the session has commenced.  The following example sets the session length to 30 minutes ( 180000 milliseconds):   "_ dc_ttl_ " : 1800000 Data Types Attributes come in a variety of types, from a basic number or, to the more powerful tally and badge. The data type determines the format in which the attribute value is stored. The following data types are supported: Data Type Description Number Stores numerical values such as order total, lifetime event count, or number of days since last visit. String Stores text values such as first/last name, address, favorite product, and page name. Boolean Stores only one of two values: 'true' and 'false'. Boolean can be used for indicating the status of a visitor action or visit. Array of Numbers Stores multiple numeric values as an array. The array may contain unique or duplicate numeric values. Array of Strings Stores multiple string values as an array. The array may contain unique or duplicate string values. Array of Booleans Stores multiple Boolean (true/false) values as an array. The array may contain unique or duplicate Boolean values. Tally Stores one or more key-value pairs. Set of Strings Stores a collection of unique string values as a Set. Date Stores the date of an event, a visitor event, or particular visit. Funnel Tracks the status of every step in a multi-step event, such as payment funnel and registration. Timeline Records all occurrences of a visitor action within a time range. Badge Assigns a visual mark or symbol to visitors who meet certain criteria or browsing behavior. Visitor ID Stores visitor's unique traits as their secondary identifier. Scope and Data Type Matrix This matrix shows which data types are available for each scope. Data Type Event Scope Visit Scope Visitor Scope Number ✔ ✔ ✔ String ✔ ✔ ✔ Boolean ✔ ✔ ✔ Array of Numbers ✔ ✔ ✔ Array of Strings ✔ ✔ ✔ Array of Booleans ✔ ✔ ✔ Tally   ✔ ✔ Set of Strings   ✔ ✔ Date ✔ ✔ ✔ Funnel   ✔ ✔ Timeline   ✔ ✔ Badge     ✔ Visitor ID     ✔ Enrichment An enrichment is the use of custom logic to transform an attribute from a static value to a dynamic one. This is used to create new data values or modify incoming data. Pre-built enrichments are available for each data type. For example, the ability to increment or decrement a numeric value is available to number attributes. (Learn more) Rule A rule provides additional logic for the purpose of triggering an enrichment. To apply a predefined rule, make a selection from the drop-down list and click Add Rule. Creating a new rule through the enrichments dialog box automatically applies it to the enrichment. To apply a new rule, click Create Rule. Restricted Data This property is used to identify attributes that contain data that should not be sent out of the system, such as third-party Connectors or DataAccess. Learn more about Restricted Data. Managing Attributes From the left navigation bar, go to AudienceStream > Visitor / Visit Attributes to view your attributes. You can optionally filter your view by clicking on any the available options on the left. Click the desired attribute to view the details. Adding an Attribute Use the following steps to add an attribute: In the sidebar, select AudienceStream > Visitor / Visit Attributes. You can optionally use the filters on the left to narrow your view. In the upper right, click + Add Attribute. In the Choose a scope dialog, select Visit or Visitor. Click Continue. In the Choose a data type dialog, select the desired data type. Click Continue. Required. In the Title field, enter a descriptive name. In AudienceDB, you can use any ASCII character for an attribute name other than double quotes. For EventDB, you are limited to ASCII characters 0 through 127, excluding double quotes. The name of an event attribute must match the name of the variable implemented. In the Notes field, enter helpful notes that describe the purpose and/or mechanics of the attribute. (Optional) Check the Restricted Data checkbox if the data will include the visitor's personal information. (Optional) Check the AudienceDB checkbox to include the attribute as a column in AudienceDB. This feature requires AudienceDB to be enabled in the profile. (Learn more) Continue to the next section to add an enrichment. Adding an Enrichment Use the following steps to add an enrichment: From the Add Attribute dialog, click Add Enrichment. A pop-up list displays a list of available enrichments based on the data type selected in previous steps. The settings or fields in the dialog box vary depending on the kind of enrichment possible for the attribute. Select the enrichment to add. Select WHEN to trigger the enrichment. This controls the timing of the enrichment. Under ANY EVENT, select an event from the drop-down list or keep the default value of ANY EVENT, (Optional) Select an existing Rule condition or create a new rule. Click Finish. Save and publish your profile to apply the changes. Imported Attributes from iQ Tag Management An imported attribute is a variable that was originally created in the corresponding Tealium iQ profile. These variables are automatically detected and pulled in as event-scoped attributes. When you modify a variable in Tealium iQ (and publish), the changes are instantly applied to the matching attribute in EventStream. Imported attributes are not editable. You must use Tealium iQ to manage them. Editing an Attribute Use the following steps to edit an attribute: Click the attribute you want to edit and click the pencil icon in the upper right corner. Make your changes and click Save. Save and publish your profile to apply the changes. Duplicating an Attribute Use the following steps to duplicate an attribute: Click the attribute you want to duplicate and then click the duplicate icon in the upper right corner. Edit if needed and then click Save. Save and publish your profile to apply the changes. Deleting or Removing an Attribute Use the following steps to delete (or remove) an attribute: Click the attribute you want to delete. Click the trash icon in the upper right corner of the box. If the attribute you attempt to delete is currently in use by a rule, enrichment, or an audience, the action will be prevented by not displaying the trash icon. A message displays that instructing you to remove the dependent element and retry. In the confirmation dialog, confirm whether or not you wish to delete the attribute. Save and publish your profile to apply the changes. ... View more

The Tealium Collect tag is Tealium's primary data collection tag. This article describes how to add and configure the Tealium Collect tag in your iQ Tag Management profile. In this article: Table of Contents Placeholder Prerequisites Contact your account manager to enable this functionality for your account. How it Works The Tealium Collect tag captures a mix of predefined data and dynamic data from the page. Using this tag, there is no need for mapping, the tag automatically sends everything set in utag.data on the initial page load or any object data passed with a utag.view/link call. For testing with proxy tools, note that this tag uses POST instead of GET. For additional information, see the EventStore Data Guide. You can leverage the Collect tag for the following features: AudienceStream, DataAccess, and EventStream The Collect tag provides AudienceStream with the data it needs to identify and take action on your audiences. The event data coming from the Collect tag can also be made available to DataAccess, where it can be analyzed using Business Intelligence (BI) tools of your choice. Read more about Live Events and how to capture this data. Enrich your Data Layer Data Layer Enrichment uses the Collect tag to gather attributes from your AudienceStream profile and make them available in your data layer. Reduce Pixel Requests With the Collect tag, you can use EventStream connectors or Tealium's Webhook connector to offload pixels from your website. Adding and Configuring the Collect Tag Use the following steps to add the Collect tag and configure the settings for the tag: Add the Collect tag to your iQ Tag Management profile from the tag marketplace. To locate the tag, use the search toolbar or look in the Big Data category. To learn how to add a tag, see Tags. Configure the tag settings, as follows: Title The default is 'Tealium Collect'. Leave as-is or replace with a unique name. Server Leave this field blank. Custom URLs entered into this field automatically default to HTTPS unless otherwise specified Tealium recommends leaving this field as-is. Data Enrichment Required. Enables AudienceStream data layer enrichment. Choose the frequency for enriching your data layer with AudienceStream data. None (default) – enrichment does not occur. Infrequent – (recommended) enrichment occurs once per visit/session. Frequent – enrichment occurs on every page load. Tealium Profile Optional. By default, this field is blank. Use to override the existing data collection endpoint, such as the AudienceStream profile that receives data from your site. Specify a value in this field only when the Server field is blank and your data collection profile for AudienceStream is something other than the current profile. Data Source Key Optional. The unique identifier of the data source you are tracking through Customer Data Hub. Leave this field blank for now. Data Collection Region Required. The geographic location of the data collection servers. The default option is "Global" (recommended). If you are not sure what to choose, contact your Account Manager. Sampling Percent Optional. For existing customers, the recommended value is 100% (default). For Free Trial or Demo users, this option allows large volume sites to run Tealium Collect data collection for a subset of visitors only. Leave the Advanced Settings as-is. Contact your Account Manager before changing any of these settings. (Optional) Enter descriptive notes for the tag. Go to the Load Rules tab and apply the default 'All Pages' rule. Save/Publish your profile. Best Practices Apply the following best practices in your implementation: Move the Collect tag to the bottom of the list of your tags so that it runs last. This allows the tag to gather all other tag and extension information and send it to the server. Do not add more than one (1) instance of this tag in your profile. Use the latest utag.js template. For additional information, see Release Notes - utag.js. Advanced For first-party CNAME of the Tealium Visitor Service endpoint used for Data Layer Enrichment, use a JavaScript extension to set this configuration as follows and then scope this extension to your Tealium Collect tag: u.visitor_service_override = "https://visitor-service.example.co.uk";  // Load Rules A common best practice is to use the default "All Pages" load rule to load this tag on all pages. Applying this rule reduces the number of events, which are limited only to link events in most implementations. In this scenario, applying the "All Pages" load rule stops the ability to end a trace because, in doing so, the kill_visitor_session event is triggered. If you are using an event-based load rule, it must to contain the following OR clause: Where ut.event equals (ignore case) kill_visitor_session , as shown the following example: Implementing with Mobile For deployments using Tealium's Android and iOS integration libraries, note the following: The default Mobile Publish Settings enable the direct Collect dispatch service by default. If using the Collect tag with Tag Management enabled for mobile, the Collect option should be toggled to OFF to prevent duplicate events. ... View more

See also:   Complete list of versions of utag.js. Update your copy of utag.js  to take advantage of the latest  fixes and enhancements . In this article: Table of Contents Placeholder Version 4.39 Released July 9, 2015 Adds support for the Tealium Collect Tag that writes visitor enrichment data to a profile-specific location in local storage. Version 4.38 Released June 16, 2015 Supports a new drop-down list for selecting when to execute an All-Tags-scoped Extension. After Load Rules (default selection) Before Load Rules (Not supported by v4.37 and below) After Tags (Not supported by v4.37 and below) NOTE: This feature is NOT compatible with versions 4.37 below as they may cause the Extension to run more than once. Added support for calling utag.view before all the Tags have loaded; this fixes a bug when calling utag.view to fire a specific Tag by its UID inside a DOM Ready-scoped Extension. Added support for calling utag.link for a specific Tag by its UID. Version 4.37 Released February 20, 2015 Fixed a bug that would incorrectly decode any instance of $ value in the utag_main cookie and render it as a separator instead. Following this fix, the utag_main cookie values will not be 'double decoded' anymore. Fixed a bug that caused the 'utag_main__ss' cookie to be set incorrectly when the readywait flag was set and /or the utag_data object was absent from the page. Version 4.36 Released January 9, 2015 You can now load new Tags with a utag.link() call. Previously you could only do this with utag.view() calls. Fixed a bug in which the utag.data object was not initialized for DOM Ready-scoped extensions when the waittimer and readywait flags were set to true. Added new built-in Data Layer variables: utag.data["ut.domain"] - The website's domain utag.data["ut.version"] - The version of utag.js loading on the site utag.data["ut.event"] - The type of event (link or view) utag.data["ut.account"] - The Tealium iQ account on the site utag.data["ut.profile"] - The Tealium iQ profile on the site utag.data["ut.env"] - The publish environment Fixed a bug in which manual utag.view and utag.link calls were not extending the session end cookie timestamp. This is especially useful for single-page apps and sites that rely on AJAX to keep the session open while the visitor interacts with the site. Fixed a bug for blocking Tags that prevented synchronously-loading Tags from being used as blocking Tags. Fixed a bug that prevented the loading of multiple synchronous blocking Tags from cache for older versions of Internet Explorer. Added debugging to output the Data Layer at the point right before All Tags-scoped extensions run. Version 4.35 Released December 5, 2014 Fixed a bug in which the Data Layer was not preserved for utag.view() calls made in rapid succession. Now a snapshot of the Data Layer is preserved for each call. Added more debugging output for manual utag.view() and utag.link() calls. Added a new utility function: utag.ut.typeOf(). For example, utag.ut.typeOf([]) returns the value "array". Version 4.34 Released October 15, 2014 Added an override (utag_cfg_ovrd) flag to utag.js in order to delay the loading of Tags until the DOM readyState "complete" (AKA "load") event. This flag provides a delay that may improve page display time speeds by causing all Tags with the Wait = Yes setting to execute even later. You can set this flag by entering the following code into a PreLoader-scoped JavaScript Code extension: var utag_cfg_ovrd = {}; utag_cfg_ovrd.dom_complete = true; Fixed a bug for Internet Explorer (IE) in which the DOM readyState was reported as "interactive" prematurely. An extra delay for readyState "complete" was added for older versions of IE. Version 4.33 Released September 24, 2014 Added two new DOM Variables (formerly Data Sources): browser height (dom.viewport_height) and browser width (dom.viewport_width). You can use these in Load Rules to detect when a visitor is using a certain devices to browse your site. For example, when this value is less than 480, you might assume the visitor is using a phone device. Try this on your phone for fun: http://viewportsizes.com/mine/. Added support for custom attributes on iframes/scripts to the utag.ut.loader function. Fixed a bug in which Tags were not loading in order indicated in the Tags tab when fired by a manual utag.view call. ... View more

The GPT, primarily an Ad Tag. allows you to define ad slots and the criteria or audience you'd like to target through the ad. You may enable this Tag to display a single ad or multiple ads by suitably configuring the Tag. Prerequisites Adding the Tag Configuring the Tag Applying Load Rules Setting up Mappings Configuring the Tag for multiple ad slots Using the JavaScript Code Extension Vendor Documentation Prerequisites DFP Account Network Code Ad unit Ad slot creative size Adding the Tag This Tag is available in Tealium's Tag Marketplace, which is home to a large selection of vendor Tags. Click here to learn how to add a Tag to your Tealium iQ profile.  Configuring the Tag   Here's how to set up an instance of this Tag for a single ad slot. Title: Enter a descriptive title to identify the Tag instance. Or you can choose the default "Google Publisher Tag(GPT)". NC+TAU: Enter the Network Code (NC) and the Targeted Ad Unit (TAU) of the ad slot. These values are available in your DFP account. "<em>Example </em>:" /1234/travel/asia/food NC = 1234 and Targeted Ad Unit = /travel/asia/food Enter the Width and Height of the ad slot. Div ID: Enter the ID of the <div> container for the ad slot. The general format is "div-gpt-ad-#########-#". Example:"div-gpt-ad-123456789-0"  Collapse Empty Div's: Choose whether or not you want the slot to collapse in the event it is not filled by an ad. The default value is set to "Yes". Toggling to "No" will display empty slots. Library: Select where you want the gpt.js library code to load from: Google (default): Loads the library code from Google's servers. Tealium (RECOMMENDED): Loads the library code via Tealium's code on your webpage. This setting is recommended since it reduces the number of network requests leading to faster page load. NOTE: You have the option to configure these settings from the Mapping Toolbox.   Applying Load Rules Load Rules determine when and where to load an instance of this Tag on your site. The 'Load on All Pages' rule is the default Load Rule. To load this Tag on a specific page, create relevant Rule conditions to apply to the Tag. Best Practice: Load this Tag on any page that contains the target ad slot.   Here's a sample Load Rule that loads the Tag if the pathname contains "/food".   Setting up Mappings Mapping is the simple process of sending data from a data source, in your Data Layer, to the matching destination variable of the vendor Tag. The destination variables for this Tag are available in the Data Mapping toolbox. For instructions on how to map to a Tag destination, see Mapping Data Sources.     Destination Name Destination Variable Description Network Code networkcode This code is available in the Admin tab of your DFP account Targeted Ad Unit adunit This is the target Ad Unit Height height Height of the ad slot Width weight Width of the ad slot Set Slot-level Targeting setTargeting_slot Sets the "key:value" parameters for the target ad slot Example: .setTargeting("interests", "sports"); Set Page-level targeting myvar Sets the "key:value" parameters of all ad slots on a page NOTE: Replace "myvar" with your custom targeting parameter name. Example: googletag.pubads().setTargeting("topic","sports"); Multiple Slot Configs gptSlots Define an array of slots for a single page (more details below) NOTE: Make sure the data source being mapped from contains an array Collapse Empty DIVs collapseEmptyDivs Collapses ad slots that do not get filled NOTE: Make sure the data source value contains either "true" or "false"   Configuring the Tag for multiple ad slots Adding and configuring the GPT for a single ad slot is very simple and straightforward. Employing the same process to configure multiple ad slots becomes tedious as you would have to to add an instance of GPT for all the ads you wish to display. The quick alternative is to store all slot configurations in an array then map the array to the 'Multiple Slot Configs' destination in the GPT instance. To create such an array, you can use the JavaScript Code Extension. Make sure to define the slot configs for every ad in this order: [[Network Code + Targeted Ad Unit, Eligible Creative Size(s), Ad Container DIV ID, Slot-Level Targeting Name/Value Pairs]] Using the JavaScript Code Extension Write a JavaScript code that uses the 'googletag.cmd.push' function to define an array of slot configurations for all the ads you wish to display on a page.  Navigate to the Extensions tab and add the "JavaScript Code Extension" from the Extensions marketplace. Scope the Extension to "Google Publisher Tag(GPT)". Write the JavaScript code as you would in any editor. Do not include the <script> tags around the code. Here's a sample code for configuring 3 ad slots using a single GPT: googletag.cmd.push(function() { googletag.defineSlot("/111/example.com/electronics", [700, 200], "div-gpt-ad-987654321-0").addService(googletag.pubads()).setTargeting("slot_var", "tv"); googletag.defineSlot("/222/example.com/electronics", [250, 170], "div-gpt-ad-987654321-1").addService(googletag.pubads()).setTargeting("slot_var", "dvd player"); googletag.defineSlot("/333/example.com/electronics", [300, 100], "div-gpt-ad-987654321-2").addService(googletag.pubads()).setTargeting("slot_var", "smartphone"); googletag.pubads().enableSingleRequest(); googletag.pubads().enableSyncRendering(); googletag.enableServices(); }); TIP: You may choose to use the "u.gptSlots.push()" method instead of "googletag.cmd.push" and reference the NC+TAU value from a data source. Example: u.gptSlots.push([b.GPT_SlotID, [[728, 90]], 'div-gpt-ad-987654321-0', {"place":"london","theme":"sports"}]); Vendor Documentation Getting Started with GPT Setting targeting and sizes with GPT  Collapsing empty div elements Tag Samples  ... View more

When you make changes to your configuration in iQ Tag Management, the interface provides visual cues to alert you of the unsaved changes. The article shows how to know when you have unsaved changes and how to save and publish them. Before you begin, learn about saving and publishing: About Saving and Publishing - Getting Started with iQ This article covers the following topics: Table of Contents Placeholder Save/Publish Window Clicking the Save/Publish button displays the Save/Publish window. The following image shows the entire dialog and the next section describes each step of the save and publish process. When you are ready to save and publish your settings, click Save/Publish. Use the following steps to save and publish your changes: Select one of the following save options: Save Use this option to overwrite the current revision. You will not be able to revert to the previous revision. Save As Use this option to create a new version. preserving  a copy of the previous version. This i s the default setting and the recommended save method as it provides the ability to rollback changes and retrieve previous versions. In the Title field, enter a title or keep the default title. This is a required field. By default, the Title field displays a date and timestamp. In the Notes field, enter notes about changes you made to the version. The notes entered in this field are useful if you need to rollback to this version in the future. This is a required field, you cannot save the version without entering notes. Select zero or more of the three default publish environments (Dev, QA, or Prod) or a custom environment. Other information about your save and publish: Your Changes, An itemized list of your unsaved changes. Version History Historical details include the environment the version was published to, a timestamp, the author of the change, and relevant notes. Code Center  Click this button to get the code needed to place on your webpage in order to implement the Tealium Universal Tag (utag.js). Learn more about the  Code Center. Configure Publish Settings  View or edit your publish and account settings. Learn more about the  Publish Settings. Validating When you complete a save and publish of your account, new code is generated and the files on the CDN are updated. This process is normally instant, but it can take up to a few minutes. The primary tool used for verifying the status of the Universal tag (utag.js) on your site is Web Companion. Learn more about using Web Companion. Version Number / Timestamp The version number, or timestamp of the current revision, is the best way to verify that your changes are live on the site. Match the timestamp from Web Companion to the date and time of your last publish to verify that your changes are live. Compare the timestamp to the version displayed in Web Companion once the version has been reloaded on the page. The timezone reported in   Tealium iQ   is GMT while the timezone is reported locally within   Web Companion.   ... View more

This article describes how to configure tag data mappings to send data from your data layer to your vendor or to override tag configuration values. In this article: Table of Contents Placeholder About Data Mappings A data mapping is a connection between a data layer variable and a vendor tag. Data mappings determine which variables are used by a tag.  For example, a tag might collect page name information in a parameter named pName , but your data layer might store this value in a variable named page_name . To send the value of page_name to pName , you create a data mapping. Once the mapping is configured, the value of page_name will always be passed to the vendor parameter  pName when that tag is triggered. Data Layer Variable > Vendor Parameter Each vendor tag has a list of available parameters that can be mapped called a mapping toolbox. In this window, browse the categories to find the desired vendor parameter(s). Variables vs. Custom Values There are two types of data mappings: variable mappings and custom values. Mapping a variable is the most common type since it allows dynamic values to be passed to the same vendor parameter. However, a custom value mapping is a convenient method for applying special logic in a mapping without using an extension. The custom value can be a plain-text value or a snippet of JavaScript code. Example: Variable Data Mapping A tag vendor has a parameter for currency code, named curr , to be set to the three-character code matching the currency of a transaction. If the tag will be loaded on pages that handle all types of currencies you will likely have a data layer variable called site_currency or currency_code that will be set to the appropriate value based on the activity of the user. The expected values might be "USD", "CAD", "GBP", "EUR", "JPY", etc. The data mapping would look like this: Example: Custom Value Data Mapping A tag vendor has a parameter for currency code, named curr , but the tag will only be deployed to a single geographic region where the currency will always be the same (such as "CAD"). In this case, a data layer variable is not necessary and the expected currency code, "CAD", can be set directly as a custom value mapping, like this: Example: Custom Value with JS Code The custom value can also be JavaScript code. This option is used if you want to pass a JavaScript number, boolean, or array value to the vendor parameter. You can use advanced statements or even an inline function. In this example, the mapping will be set to "GBP" if the hostname contains "co.uk", otherwise set to "USD", using the following line of JavaScript.   location.hostname.indexOf("co.uk") > -1 ? "GBP" : "USD" To reference a data layer variable such as page_name , use the b object like this b['page_name'] . Learn more about the b object. Creating a Data Mapping Vendor tag parameters (also called destinations) are built into the Data Mappings configuration screen for the tag. This is where you add and manage data mappings. Use the following steps to create a new data mapping: Expand a tag to view the details for that tag. Under Mapped Variables, click Edit. Select a data layer variable from the Variables drop-down or click + Add Variable to use a new one. Click Select Destination. The mapping dialog displays the supported vendor parameters. Browse the categories of vendor parameters in the left panel and check the box next to the desired destination. Click Done. The new data mapping displays. Repeat Steps 2 through 6 to map additional variables. When complete, click Apply. Creating a Custom Value Mapping Use the following steps to create a data mapping that uses a custom (static) value instead of a data layer variable: Expand a tag to view the details for that tag. Under Mapped Variables, click Edit. Expand the  Variables drop-down list or click Use Custom Value. Click Select Destination. The mapping dialog displays the supported vendor   parameters. Select the type of value to set and enter a value. Text: a simple text value. JS Code: a native JavaScript value, such as a Number, Boolean, Array, Object, or even an inline function. Browse the categories of vendor parameters   in the left panel and check the box next to the desired destination. Click   Close . The mapped variable displays. Repeat Steps 2 through 6 to map additional custom values. When complete, click   Apply. Mapping Precedence When two or more variables are mapped to the same destination, such as page_name > pageName and Document Title > pageName, the last mapping takes precedence. Data mappings can be reordered to account for this precedence. In this example, if both page_name and document title are populated, the destination variable pageName will receive the value from document title . If the variables are populated, the last mapping takes precedence. If a variable does not have a value, the mapping is not applied. Creating a Custom Data Mapping While the built-in destinations cover most of your mapping needs, you can optionally define a custom data mapping to send data to a vendor parameter that you name.  Use the following steps to create a custom data mapping: Expand a tag to view the details for that tag. Under Mapped Variables, click Edit. From the variable drop-down list, click Use Custom Value. Click + Add Custom Destination in the top panel or in the lower left panel.  Type a name for the custom variable and click OK in the top panel or + Add if you used the bottom panel option. Repeat the steps to add more custom mappings. When complete, click Done. The custom mapping displays in the Data Mappings tab. Editing a Custom Data Mapping Use the following steps to edit the destination variable: Expand a tag to view the details for that tag. Under Mapped Variables, click Edit. Click the destination variable name in the top panel. The name becomes a text field. Type the new name. Click OK to apply the changes. When complete, click Done. Mapping an AudienceStream Attribute AudienceStream attributes are enriched attributes about your visitors that are sent back to your website for use with personalization. Requirements The following requirements must be in place to map an AudienceStream attribute: Data Layer Enrichment  Your iQ profile must be populated by attributes from the matching AudienceStream profile. Those attributes will be made available as data mappings in the variables drop-down menu. They are organized by attribute types and are clearly labeled as "AudienceStream" variables. (Learn more) AudienceStream Capable Tags Tags marked as "AudienceStream Capable" in the Tag Marketplace have the ability to map attributes from AudienceStream to the tag's destinations. Look for this label in the tips panel when adding a tag. You can optionally filter your tag search results by clicking AudienceStream Capable in the left panel. Managing Data Mappings Edit a Destination Use the following steps to edit a destination for a mapped variable: Expand a tag to view the details for that tag. Under Mapped Variables, click Edit. Click Edit next to the mapping you want to modify. The mapping dialog displays. Edit any of the following: Change the destination name Map to another destination Remove the destination Click Done. Repeat to edit more mappings. When complete, click Apply . Delete a Destination Use the following steps to delete a destination for a mapped variable: Expand a tag to view the details for that tag. Under Mapped Variables, click Edit. Click the trash icon next to the mapping you want to remove. Click Apply to confirm. No warning or confirmation message displays. The destination dropped (deleted) is removed and cannot be restored.  Reorder Mappings You can drag and drop data mappings in your preferred order. This is helpful if you want to order your mappings alphabetically for better organization. The only time ordering matters is when two or more data layer variables are mapped to the same vendor destination. In this case, the last mapping takes precedence. ... View more

The Facebook Pixel tag combines the functionality of the Facebook Custom Audiences Pixel and the Conversion Tracking Pixel. This is the legacy version of the tag and will soon be deprecated. (See new version) This article describes how to set up the tag in your Tealium iQ profile. Table of Contents Placeholder Prerequisites Facebook Ads Account Upgraded Facebook Pixel (or legacy Custom Audiences pixel) Conversion Pixel (legacy) Tag Configuration First, go to the Tealium tag marketplace and add the Facebook Pixel tag to your profile. (Learn more). The best practice is to configure a single tag instance per pixel ID for standard PageView and event tracking. After adding the tag, configure the settings described in the following table:  Setting  Description Title Enter a unique name to identify the tag Important if you are adding multiple instances of this tag Facebook Pixel ID Your Facebook Pixel ID This appears as a long series of numbers in the code snippet You may add multiple pixel IDs as a comma-separated list Example fbq('init', '12345678901234') Conversion Pixel ID  Required only for tracking legacy Conversion Pixel (deprecated) The ID appears in the code snippet as: fb_param.pixel_id = ' 12345 '; –   OR  – fbq('track', ' 12345 ') OR fbq.push(['track', ' 12345 ', { }]); Allow Default Page View  Triggers the PageView event on all pages True Default value Turns on automatic PageView tracking for non-conversion events False Turns off PageView triggering when tracking conversion events If you do not want this default behaviour, you can turn it off using the flag disablePushState . When you set this flag to true , it will stop sending PageView events on history state change.     Default Event to Send  Select the event you wish to trigger by default This is primarily for use with the Conversion Pixel Advanced Matching Enables Facebook's Advanced Matching service. ( Learn more ) This is enabled by default, though customers must add data mappings to enjoy the benefits of Advanced Matching.  Auto calculate number of items Choose whether or not to automatically count the items at checkout Default value is 'True' Enable trackSingle Enables the use of trackSingle and trackSingleCustom for Facebook event tracking calls. These trigger tracking calls only for the pixel IDs configured in this tag in scenarios where multiple Facebook pixels are loaded. Default value is 'True' Example fbq('trackSingle', 'FB_PIXEL_ID', 'Purchase', customData ) - OR - fbq('trackSingleCustom', 'FB_PIXEL Enable trackCustom Enables the use of trackCustom  for Facebook event tracking calls. You can track custom events by calling the  fbq('trackCustom')  pixel function, with your custom event name and (optionally) a JSON object as its parameters. Example To track visitors who share a promotion in order to get a discount, you could track them using the custom shown in the following example: fbq ('trackCustom','ShareDiscount',{promotion:'share_discount_10%'}); Load Rules Load rules determine when and where to load an instance of this tag on your site . Recommended Load Rule: For tracking standard PageView and events, use the  default All Pages  rule For tracking legacy Conversion Pixel, apply custom rule conditions to load the tag on specific conversion pages. Data Mappings Mapping is the process of sending data from a Data Layer Variable to the corresponding destination variable of the vendor tag. The destination variables for the Facebook Pixel tag are built into the Data Mapping tab.  For instructions on how to map a variable to a tag destination, see Data Mappings.The following sections describe available categories: Standard Use these mappings to override the tag configuration settings. This can be useful if you want to set values dynamically based on your data layer. Destination Name Destination Variable Description Facebook Pixel ID cust_pixel Numeric identifier(s) of the Facebook Pixel Conversion Pixel ID conv_pixel Numeric identifier of the legacy conversion pixel Allow Init Page View [true/false] page_view 'init' track call List of Events to fire evt_list Events listed either as comma-separated values or an array in your variable  Enable trackSingle [true/false] track_single Enables use of trackSingle and trackSingleCustom for event tracking. Restricts event tracking to the pixel ID(s) added to the Facebook Pixel configuration in Tealium iQ in situations where multiple Facebook pixels are loaded. Enable trackCustom [true/false] track_custom Enables the use of trackCustom for Facebook event tracking calls.   Custom event names must be strings, and cannot exceed 50 characters in length. Advanced Matching With this additional data, you can report and optimize your ads for more conversions and build larger re-marketing audiences. You can pass the customer identifiers that you collect from your website during the check-out, account sign-in or registration process as parameters in the pixel. In Advanced Matching, the case of the term entered is normalized unless the item to be matched is already recognized.   Destination Name Destination Variable Description Email   em Email First Name   fn First name Last Name   ln Last name Phone Number   ph Numeric value of phone number Gender   ge f or m Date of Birth   db [ yyyymmdd ] City   ct City State   st 2-letter code Zip   zp Zipcode  E-Commerce Since the Facebook Pixel tag is e-commerce enabled, it will automatically use the default E-Commerce Extension mappings. Manually mapping in this category is not needed unless you want to override any extension mappings or your desired e-commerce variable is not offered in the extension. Destination Name Destination Variable Description E-Commerce Extension Variable Order ID order_id Unique identifier assigned to the final order _corder Sub Total sub_total Sub total amount of the final order _csubtotal Currency order_currency Currency used in the payment _ccurrency List of Product IDs product_id Unique identifier of each product in the product array _cprod List of Product Names product_name Name of each product in the product array _cprodname List of Categories product_category Category of each product in the product array _ccat List of Prices product_unit_price Unit price of each product in the product array _cprice Limited Data Use Variable Description   lmt_data.use_ldu (Use LDU) If true , use Facebook’s Limited Data Use option If false , do not use Facebook’s Limited Data Use option lmt_data.ldu_types.geolocate  (LDU should Geolocate) If true , the LDU geolocates the user. If false , the LDU doe snot geolocate the user. If “Use LDU” is enabled, then “LDU should Geolocate” is also enabled by default. lmt_data.ldu_types.california  (LDU is California) If true , sets the state and country California-specific values inside the template. Only enable this option if the user is located in California and needs to be processed with Limited Data Use. If false , does not set the user’s state and country California-specific values inside the template. Events Map to these destinations for triggering specific events on a page. Events are used for tracking conversions and building targetable audiences for your Facebook ads.  The "Purchase" event is automatically triggered when an Order ID value is available, either through the E-Commerce extension or a direct data mapping. Use the following steps to map an event: In the Trigger field, enter the value of the variable you are mapping to the destination that corresponds to the event selected. For example, if you want to trigger the Purchase event when event_name="order" is in your UDO, you would enter "order" (assuming you are currently mapping the variable event_name ). In the Event field, select the desired event from the drop-down list (e.g. Purchase). Click + Add. Custom Events For custom events, select Custom and enter a name for the custom event. In this following example the custom event "InboundLead" will be triggered when the variable event_name  equals inbound_lead_event . To edit a custom event, single click on the destination input field to edit the event name directly. The values are entered in the form: {VARIABLE_VALUE}:{DESTINATION_EVENT} . The l eft-side of the colon is the variable value that will trigger the event, such as inbound_lead_event The right-side of the colon is the custom event name, such as InboundLead . Custom Event Data Map to these destinations if you wish to pass a custom parameter with a custom Event that you mapped in the   Events tab. Use the following steps to map a Custom Event Data variable:  In the Event Name  field, e nter the name of the custom event exactly as specified in the Events tab. In the Parameter  field, ente r the name of the parameter you want to send. Click + Add. Full List of Standard Events Destination Event Event Description AddPaymentInfo Visitor adds payment details during the checkout process AddToCart Visitor adds an item to the cart AddToWishlist Visitor adds an item to the wishlist CompleteRegistration Visitor completes a registration form Example: visitor successfully subscribes to a newsletter Contact When a person initiates contact with your business via telephone, SMS, email, chat, or other method. Conversion For legacy Conversion Pixel only; requires the Conversion Pixel ID to be set Custom Visitor action is treated as a custom event Can be used for reporting custom audiences and custom conversions CustomizeProduct When a person customizes a product. InitiateCheckout Visitor takes the first step to begin checkout process Example: visitor clicks "Go to Checkout" button Lead Visitor action indicates his or her buying intent Example: visitor signup for a trial product PageView Visitor views any page on your site Purchase Visitor successfully completes the last step in the checkout process This event is required for tracking conversions; make sure to map it in the Events Tab Schedule When a person books an appointment to visit one of your locations. Search Visitor performs a search action StartTrial When a person starts a free trial of a product or service you offer. SubmitApplication When a person applies for a product, service, or program you offer. Subscribe When a person applies to start a paid subscription for a product or service you offer. ViewContent Visitor views a specific page, indicating their browsing intent Parameters Map to these destinations if you wish to pass additional data with the event(s) that you mapped earlier. Parameters are only used with pre-defined events. See the Custom Event Data section to learn how to pass a parameter with a custom event. Use the following steps to pass a parameter with a predefined event: In the Event field, select a Facebook event from the drop-down list. In the Parameter field, select a Facebook parameter from the drop-down list. For a Custom parameter, enter a name to identify the parameter. Click + Add.   Full List of Predefined Parameters Destination Parameter Description Value Value associated with the event Currency Currency associated with the Value parameter Content Name Name of the product or page Content Type Type of the product or page associated with the event Content IDs Any identifier(s) associated with the event Content Category Category of the product or page Number of Items Number of items at checkout Search String Keyword/term used in the search action Order ID Unique identifier of the final order Status Status of the CompleteRegistration event Custom Custom parameter to be passed with a predefined Event Hotel Parameters Map to the destinations listed in the following table to send hotel-related search and hotel booking details with the event(s) you mapped earlier. Full List of Hotel Parameters  Parameter Description Content Type Required Type of the product or page associated with the hotel. Ensure that the variable value equals 'hotel'. Content IDs Required Unique identifier(s) associated with the hotel. Destination Required String value describing the city, state, or country where the hotel is located. Example: San Fransisco. Check-in Date Required The date on which the visitor will be checking in to the hotel Corresponds to timezone of the hotel The following date formats are supported: YYYYMMDD YYYY-MM-DD YYYY-MM-DDThh:mmTZD YYYY-MM-DDThh:mm:ssTZD Check-out Date Required The date on which the visitor will be checking out of the hotel Corresponds to timezone of the hotel The following date formats are supported: YYYYMMDD YYYY-MM-DD YYYY-MM-DDThh:mmTZD YYYY-MM-DDThh:mm:ssTZD Value Required Relative value of the event to the advertiser Required for the Purchase event Currency Required Currency associated with the Value parameter Required for the Purchase event  Optional Hotel Parameters Parameter Description City Optional City where the hotel is located Region Optional State/District where the hotel is located Country Optional Country where the hotel is located Number of Adults Optional Number of adults specified in the booking/search Number of children Optional Number of children specified in the booking/search Suggested Hotels Optional Identifiers of other hotels recommended for the visitor User Score Optional Relative value of the visitor to the advertiser Must contain a numerical value Hotel Score Optional Relative value of the hotel to the advertiser Must contain a numerical value Purchase Currency Optional Currency associated with the hotel booking transaction Optional Hotel Parameters for Search Events Only Parameter Description Preferred Star Ratings Optional Search criteria is filtered by the hotel's star ratings Preferred Price Range Optional Search criteria is filtered by room rates Preferred Neighborhoods Optional Search criteria is filtered by location neighborhood Journey Parameters Map to the destinations listed in the following table to send visitor's travel details (flight or route journey) with the event(s) you mapped earlier. Full List of Journey Parameters Parameter Description Content Type Required Indicates whether the journey type is flight or non-flight The variable value must equal "flight"* for flight journeys and "route" for non-flight journeys. Origin Required String value describing the city, state, or country where the journey begins. Example: San Fransisco, California, USA. Destination Required String value describing the destination city, state, or country. Example: Toronto, Ontario, Canada. Departing Departure Date Required Date and time when the outbound journey begins The following date formats are supported: YYYYMMDD YYYY-MM-DD YYYY-MM-DDThh:mmTZD YYYY-MM-DDThh:mm:ssTZD Returning Departure Date Required Date and time when the return journey begins The following date formats are supported: YYYYMMDD YYYY-MM-DD YYYY-MM-DDThh:mmTZD YYYY-MM-DDThh:mm:ssTZD Value Required Relative value of the event to the advertiser Required for the Purchase event Currency Required Currency associated with the Value parameter Required for the Purchase event Required Flight Parameters The following parameters are   required   when the 'content type' value equals 'flight':   Parameter Description Origin Airport Required IATA code (i.e. three-letter airport identifier) of the origin airport Destination Airport Required IATA code (i.e. three-letter airport identifier) of the destination airport Optional Journey Parameters Parameter Description Origin City Optional Name of the city where the journey begins Origin Region Optional Name of the state/region where the journey begins Origin Country Optional Name of the country where the journey begins Destination City Optional Name of the destination city Destination Region Optional Name of the destination state/region Destination Country Optional Name of the destination country Departing Arrival Date Optional Date and time on which the visitor arrives at their destination The following date formats are supported: YYYYMMDD YYYY-MM-DD YYYY-MM-DDThh:mmTZD YYYY-MM-DDThh:mm:ssTZD Returning Arrival Date Optional Date and time on which the visitor returns to the origin, completing the journey The following date formats are supported: YYYYMMDD YYYY-MM-DD YYYY-MM-DDThh:mmTZD YYYY-MM-DDThh:mm:ssTZD Number of Adults Optional Number of adults in the travel Number of children Optional Number of children in the travel Number of Infants Optional Number of infant babies in the travel Travel Class Optional Indicates the type of class the visitor will be travelling in. For 'flight' journey, the variable should contain enum values such as economy, premium, business, first. For 'route' journey, the variable should contain a custom string value. Example: Economy User Score Optional Relative value of the visitor to the advertiser Must contain a numerical value Purchase Value Optional Price of the travel booking Recommended for Purchase and InitiateCheckout events. Purchase Currency Optional Currency used in the booking transaction Optional Journey Parameters for Search Events Only Parameter Description Preferred Number of Stops Optional Search criteria is filtered by the number of stopovers Set the variable value to '0' for direct flights and '1' if the visitor has specified the number of stopovers. Use Cases This section provides use cases that represent real-life scenarios. Use Case: Tracking PageView and Standard/Custom Events Set the PageView event to be fired automatically on all pages and trigger all non-conversion via data mappings. Use the following steps to set up this use case for your environment: Configure the following settings: Pixel ID: FB_PIXEL_ID Allow Default Page view: True Default Event to Send: None Load the tag on all pages (default rule). Map the variable event_name to the non-conversion event(s) of choice. Use Case: Tracking PageView and Conversion Event (Deprecated) Triggering a conversion event requires the Conversion Pixel ID. You may do this in the same tag instance you are using for tracking PageView and non-conversion events. Use the following steps to set up this use case for your environment:   Configure the following settings: Pixel ID: FB_PIXEL_ID Conversion Pixel ID: CONVERSION_PIXEL_ID Allow Default Page view: True Default Event to Send: None Load the tag on all pages (default rule). Map the variable event_name to the conversion event(s) of choice. Use Case: Tracking Legacy Conversion Pixel Only (Deprecated) The Conversion Pixel needs to be tracked in a separate tag instance. In this tag instance, leave the Pixel ID blank and disable automatic pageview tracking. Because you are not tracking specific events, no data mappings are required. Use the following steps to set up this use case for your environment: Configure the following settings: Conversion Pixel ID: CONVERSION_PIXEL_ID Allow Default Page view: False Default Event to Send: Conversion Apply custom load rules to load this tag on specific conversion pages. Use Case: Multiple Pixels on A Single Page The following use cases represent scenarios that can be used for multiple pixels on a single page: Shared Event Tracking If you want multiple Facebook Pixels to share pageview and event tracking, you can add a comma-separated list of those pixel IDs to the Facebook Pixel ID field in the tag configuration settings. Having several Facebook Pixels with their own pixel IDs may share event tracking with other Facebook Pixels on the page if their Enable trackSingle setting is 'false', although this may result in inconsistent tracking behavior and is not recommended. Individual Event Tracking If you are loading more than one Facebook Pixel on a single page, and you wish to keep the tracking events from being recorded for all of the pixels on that page, then make sure the Enable trackSingle setting is 'true'. This setting will fire event tracking only for the pixel IDs added for that tag. If your Facebook Pixel in Tealium iQ was added before March of 2018, you may not be able to take advantage of the trackSingle feature. In this case, update your Facebook tag template to the latest version. Note that the trackSingle setting is set to true be default. You must map to track_single and set the value to 'false' to override and disable this feature. Versions that predate March 2018 If you added your tag after March of 2018, refer to the use cases above when setting up multiple Facebook pixels Older versions of the Facebook Pixel were not designed to be loaded more than once on a single page. The Facebook JavaScript library initializes a single instance of the fbq object, which is used for all tracking that occurs on the page (thus reusing the same pixel ID). If you require more than one Facebook pixel, each with a different pixel ID, to be fired on a single page, and you are unable to update the tag template, then we recommend implementing the <noscript> version of the pixel using the Tealium Generic tag. Example Scenario Example of Facebook Pixel <noscript> code: <noscript> <img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id={{FACEBOOK_PIXEL_ID}}&ev=PageView&noscript=1" /> </noscript> In this scenario, the URL of the hidden image pixel can be configured as follows: Add the Tealium Generic tag. Set the Title to "Facebook Pixel (custom)". Set the Base URL to "https://www.facebook.com/tr" Set the  Query String  to id={{FACEBOOK_PIXEL_ID}}&ev=PageView&noscript=1" . Set the desired  Load Rule  and  Data Mappings . Click  Apply . Facebook Dynamic Ads for Tealium iQ For additional information about how to set up Facebook Dynamic Ads in Tealium iQ, see the TLC article How to Set up Facebook Dynamic Ads in Tealium iQ. Vendor Documentation See the following vendor documentation for more information: Migrating from Deprecated Pixels Reference: Standard and Custom Events The Facebook Pixel FAQ Advertiser Help Center: Using Facebook Pixel with Tealium Conversion Tracking with the Pixel ... View more

This article lists the operators available when building conditions for audiences and rules. Some operators only apply to certain attribute types, which is indicated in the "Applies to" column. The string condition "matches regular expression (Regex)" is available as an Experiment. Condition Description Applies to array contains An item in the array is an exact match to the value specified. True ["iOS", "Android"] array contains "Android" False ["Women's Clothing", "Shoes"] array contains "Women" Array array does not contain No item in the array is an exact match to the value specified. True ["iOS", "Android"] array does not contain "Samsung" False ["Women's Clothing", "Shoes"] array does not contain "Shoes" Array contains Attribute value includes the value you specify. True "user@tealium.com" contains "tealium" ["iOS", "Android"] array contains "Android" False ["Women's Clothing", "Shoes"] array contains "Women" Array String Tally Visitor ID contains (ignore case) Attribute value includes the value you specify. String Visitor ID does not contain Attribute value excludes the value you specify. Array String Visitor ID Tally does not contain (ignore case) Attribute value excludes the value you specify. Array String Visitor ID Tally contains partial string Attribute value partially matches the value you specify. True ["Women's Clothing", "Shoes"] array contains "Women" False ["Women's Clothing", "Shoes"] array contains "Tops" Array Tally Visitor ID contains partial string (ignore case) Attribute value partially matches the value you specify, regardless of case. Array Tally Visitor ID equals Attribute value matches the whole value you specify True "purchase" equals "purchase" 0 equals 0 False "Luggage" equals "luggage" 0 equals 1 Number String Visitor ID equals (ignore case) Attribute value matches the whole value you specify. String Visitor ID does not equal Attribute value does not match the whole value you specify. Number String Visitor ID does not equal (ignore case) Attribute value does not match the whole value you specify. String Visitor ID less than Attribute value is less than the value you specify. Number Date less than or equal to Attribute value is either less than or equal to the value you specify. Number Date greater than Attribute value exceeds the value you specify. Number Date greater than or equal to Attribute value either exceeds or equals the value you specify. Number Date is assigned Attribute exists, but may or may not have a value. True "Shirts" is assigned ["iOS", "Android"] is assigned [] is assigned "" is assigned 0 is assigned Is VIP is assigned Number Timeline List Badge String Tally Visitor ID Date is not assigned Attribute does not exist. Number Timeline List Badge String Tally Date Visitor ID is empty Tealium iQ variable does not contain any value ie. value is undefined, null, or blank string. True { page_name : undefined } { page_name : null } { page_name : "" } { product_id : [] } Imported from iQ is not empty Tealium iQ variable contains any value ie. value is a string containing one or more characters, a number with a value (including 0), or an array with one or more items. True { page_name : "Title" } { page_num : 1 } { product_id : ["WidgetXYZ"] } Imported from iQ is true Boolean value equals "true". Boolean is false Boolean value equals "false". Boolean occurred less than Date value is not yet past the number of minutes/hours/days/weeks/months you specify. Date occurred more than Date value is past the number of minutes/hours/days/weeks/months you specify. Date is started Funnel is initiated for the visitor/visit. Funnel is completed Funnel has ended for the visitor/visit. Funnel step completed Step is successfully completed for the visitor/visit. Funnel step not completed Step is not completed for the visitor/visit. Funnel is executed Tag has successfully fired on the page. Tags in your Tealium iQ profile Extended Rule Condition for Tally When using the contains operator, you can create a rule condition to check if the key for a tally contains a specific value. Only available using the contains operator. Use the following steps to include a Tally key and its value in a rule: Add a new Rule condition or select an existing rule to edit. Under Conditions, select your Tally from the first drop-down list. Select the contains operator in the next drop-down list. In the next drop-down list, select Custom Value. Enter the key that you expect in the Tally. Click the plus (+) button to the right and select the operator with which to evaluate the key you specified. Specify the value you want to evaluate against the key. You can use an attribute or simply type in a custom value for this purpose. Click Finish. You have successfully created the rule. Provides a built-in date picker for selecting a custom MM/DD/YY. ... View more

Tealium Search Engine Optimization (SEO) tag adds JSON-LD format data to your pages which allows search engines (i.e. Google) to customize the way search results are displayed for your site. This article describes how to set up the tag in Tealium iQ. Table of Contents Placeholder Tag Configuration First, go to the tag marketplace and add the Tealium SEO Tag to your profile (learn more about how to add a tag). After adding the tag, configure the below settings: Homepage URL: Enter the complete homepage URL (including the protocol). Site Name: Enter the name of your site/company. Search URL: Enter the search URL and replace the query string value with "search_term_string". For example, if your search URL is http://query.example.com/search?q=smartphones . Replace the value of "smartphones" with "search_term_string" so the final URL becomes: http://query.example.com/search?q=search_term_string Use Path for Breadcrumb: Choose whether or not you want to auto-generate the path breadcrumb. Yes (default): uses the pathname to build the breadcrumb. No: uses the Data Mappings to build the breadcrumb. Build Product Data: Choose whether or not to automatically add the product details. Yes (default): Use the E-Commerce extension to automatically build product data for product pages (recommended for E-Commerce sites). No: Does not add product data. Load Rules Load rules determine when and where to load an instance of this tag on your site. Recommended load rule: All Pages. 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 destination variables for the Tealium SEO Tag are built into its data mapping tab. Available categories are: Standard Destination Name Description Site Name Your company or site name Homepage URL The complete homepage URL List of Breadcrumb Names Array of breadcrumb names List of Breadcrumb URLs Array of breadcrumb URLs Custom JSON-LD Data Sets a specific value in the JSON-LD object. Add custom data by replacing "custom" with your data name. Supports dot notation nesting e.g. json_ld.contactPoint.@type   How to Create Custom JSON-LD Data Mappings Custom JSON-LD data is created using data mappings and dot-notation naming. You will need to know what the final JSON-LD should look like in your page in order to determine the mappings. Let's use the example of creating a contactPoint object. In the final JSON-LD, the contactPoint object might look like this: <script type="application/ld+json"> { "@context" : "http://schema.org", "@type" : "Organization", "url" : "http://www.example.com", "contactPoint": { "@type": "ContactPoint", "telephone": "+1-888-555-1212", "contactType": "sales" } } </script> In the tag, the entire object is represented by the json_ld name in the data mappings. From there, each item within the final object is referenced by using dot-notation. For example, to set all of the values from the example above, you would create the following data mappings:  json_ld.@context json_ld.@type json_ld.url The tag will create sub-objects within the final JSON-LD based on the dot-notation structure you specify in the mappings. To create the contactPoint object in the example above, create data mappings with contactPoint at the second level and each property at the third level: json_ld.contactPoint.@type json_ld.contactPoint.telephone json_ld.contactPoint.contactType In this case, let's assume you have a data layer variable named contact_phone that contains the phone number to set within the contactPoint telephone property.  First, create a data mapping for contact_phone and select the Custom JSON-LD Data destination. Second, click the json_ld.custom name to edit it, then change the value to json_ld.contactPoint.telephone . The final data mappings might look like this, depending on the names of your variables: E-Commerce Since the Tealium SEO Tag is e-commerce enabled, it will automatically use the default E-Commerce Extension mappings. Manually mapping in this category is generally not needed unless: you want to override any Extension mappings your desired ecommerce variable is not offered in the Extension Use the following mappings if Build Product Data is set to Yes. Destination Name Description List of Product Names Array of product names. List of Product Brands Array of product brands. List of Product SKUs Array of product SKUs. List of Prices Array of prices. List of Product Image URLs Array of image URLs. List of Product Part Numbers Array of product part numbers. List of Product Rating Values Array of product ratings. List of Product Review Counts Array of product review counts. List of Product Descriptions Array of product descriptions. Product Price Currency Array of product currency. Creating Custom JSON-LD with Data Mappings Custom JSON-LD data is created using data mappings and dot-notation naming. You will need to know what the final JSON-LD should look like in your page in order to determine the mappings. Let's use the example of creating a   contactPoint   object. In the final JSON-LD, the contactPoint object might look like this: <script type="application/ld+json"> { "@context" : "http://schema.org", "@type" : "Organization", "url" : "http://www.example.com", "contactPoint": { "@type": "ContactPoint", "telephone": "+1-888-555-1212", "contactType": "sales" } } </script> In the tag, the entire object is represented by the   json_ld   name in the data mappings. From there, each item within the final object is referenced by using dot-notation. For example, to set all of the values from the example above, you would create the following data mappings:  json_ld.@context json_ld.@type json_ld.url The tag will create sub-objects within the final JSON-LD based on the dot-notation structure you specify in the mappings. To create the   contactPoint   object in the example above, create data mappings with   contactPoint   at the second level and each property at the third level: json_ld.contactPoint.@type json_ld.contactPoint.telephone json_ld.contactPoint.contactType In this case, let's assume you have a data layer variable named   contact_phone   that contains the phone number to set within the contactPoint telephone property.  First, create a data mapping for   contact_phone   and select the Custom JSON-LD Data destination. Second, click the   json_ld.custom   name to edit it, then change the value to json_ld.contactPoint.telephone . The final data mappings might look like this, depending on the names of your variables: Creating Custom JSON-LD with JavaScript You can inject custom JSON objects using the JavaScript Code Extension scoped to this tag. The tag exposes a JavaScript utility function for adding custom objects called u.injectJSONLD() . It takes one parameter, an array of objects. Example of adding a ContactPoint Schema: u.injectJSONLD([{ "@context": "http://schema.org", "@type": "Organization", "url": "https://www.example.com", "contactPoint": [{ "@type": "ContactPoint", "telephone": "+1-877-555-1212", "contactType": "Lead", "contactOption": "TollFree", "areaServed": "US" }] }]); Vendor Documentation Intro to Structured Data schema.org - Full Hierarchy Site name and breadcrumb data - Google Developers Product Data - Google Developers ... View more