Tealium Learning Center

This article describes the visitor ID attribute and how to use it. In this article: How it Works Before you begin, familiarize yourself with the following: Using Attributes Using Enrichments About Visitor Stitching Identifying your visitors is a critical step in making full use of Tealium AudienceStream CDP. When certain qualifying visitor events occur, such as a user registering or completing a purchase, there is an opportunity to uniquely identify that visitor using an event attribute such as email_address_hash 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. Visitor stitching uses a visitor ID attribute to identify users across sessions and devices. A visitor ID attribute is configured in AudienceStream to uniquely identify visitors. When you create a visitor ID attribute, you add an enrichment to set the value to a user identifier, which is an event attribute, such as email_address_hash or customer_id . For visitor stitching to work properly, you must choose a unique user identifier, create a rule to determine when to identify a visitor, and verify that the chosen attribute is unique for each visitor. Visitor stitching is disabled by default. Contact your account manager to enable it. The visitor ID attribute is available in the following scope: Visitor. System Requirements A visitor ID attribute 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. A 10-character identifier with only 2 different characters ( "a1a1a1a1a1" ) is invalid. Enrichment – Attributes with a data type of Number cannot be used to enrich a visitor ID attribute.  UTF-8 character sets are supported. The system automatically validates these requirements. You do not need these rule conditions in your visitor ID attribute configuration. Best Practices A visitor ID attribute should follow these best practices: Uniqueness - Each visitor ID attribute 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 a hashed 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 IDs in AudienceStream. Verifying the Value - If you are using an email address, you may want to verify that the address contains the @ symbol.  You may also want to check the string for other values such as,  undefined ,  unknown , or  not set or any text that would not be a valid value for a visitor ID attribute. See Creating a Visitor ID Attribute for a guide to creating the most accurate visitor ID attribute possible. Setting a Value for a Visitor ID Attribute Set the value for a visitor ID attribute during a qualifying event, which is an event that occurs when a customer provides a reliable, unique means of identification, such as registering an account or completing a purchase. A visitor ID attribute should not be a marketing activation ID (such as a gid). These third-party identifiers can be stored as visitor attribute for use in connectors, but are not recommended as visitor IDs. Visitor ID Attribute Enrichment This enrichment stores a user identifier for a visitor in a visitor ID attribute. 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 attribute to customer_id when the user_register event occurs. After a visitor ID attribute 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" Related Articles Creating a Visitor ID About Visitor Stitching Anonymous Identifiers, User Identifiers, and Visitor ID Attributes  Visitor Stitching Scenarios  ... 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 The number attribute stores a numeric value for browsing metrics such as visits, page views, and events. Common examples include Lifetime Value, Order Total Transaction, or Days Since Last Purchase.  Numeric values are stored as decimals or integers. Choose the type that matches your needs: Decimal (default) Decimal values can have zero (0) or more decimal digits. Example: 12, 12.0, 12.345 Recommended for attributes that represent monetary values. Integer Only whole number values are stored. Example: 12, -4, 3214 Useful for number attributes that represent quantities, counters, or scores. The number attribute is available in the following scopes: Event, Visit, Visitor. There are no storage capacity limits for number attributes, but these attributes are still limited by the maximum size of the profile after encryption and compression. 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 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.  Numeric values are stored as decimals or integers. Choose the type that matches your needs: Decimal (default) Decimal values can have zero (0) or more decimal digits. Example: 12, 12.0, 12.345 Recommended for attributes that represent monetary values. Integer Only whole number values are stored. Example: 12, -4, 3214 Useful for number attributes that represent quantities, counters, or scores. There are no storage capacity limits for tallies, but these attributes are still limited by the maximum size of the profile after encryption and compression. 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)". Tally Tie Breaker Logic A tally tie occurs when multiple keys have the same value. When this happens, the favorite is chosen based on the following logic: If a tie occurs, the most recently incremented key becomes the favorite. If more than one key was incremented simultaneously using an array of values, the last entry processed becomes the favorite. If the order in which mulitple keys were incremented is unclear, the favorite is chosen using an alphabetical sort. Examples The events below describes some possible tally tie scenarios and the chosen favorite in each scenario. Event 1 There is only one key Apparel in this page_category event, so it becomes the favorite. // Recieved Event "page_category": { ["Apparel"] } // Result "page_category":{ "Apparel": 1 }, "page_category_favorite": "Apparel" Event 2 In this event, two keys Apparel  and  Accessories are received, causing a 3-way tie. Since  Accessories  is the last entry processed, it becomes the favorite. // Recieved Event "page_category": { ["Apparel", "Accessories"] } // Result "page_category": { "Books": 1, "Apparel": 1, "Accessories": 1 }, "page_category": "Accessories" Event 3 In this event, one key Apparel is received making it the key with the highest value, therefore, it becomes favorite. // Recieved Event "page_category": { ["Apparel"] } // Result "page_category": { "Accessories": 1, "Apparel": 2, "Books": 1 }, "page_category_favorite": "Apparel" Scope The tally attribute is available in the following scopes: Event, Visit, 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. The number attribute stores a number for browsing metrics such as visits, page views, and events. Common examples include Lifetime Value, Order Total Transaction, or Days Since Last Purchase. To specify the number type, select Decimal or Integer from the Type drop-down list. Decimal Default value. Decimal values can have zero (0) or more decimal digits. Example: 12, 12.0, 12.345 Required for attributes that represent monetary values. Integer Only whole number values are stored. Example: 12, -4, 3214 Useful for whole number attributes that represent quantities, counters, or scores. 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

Load rules are conditions that define when and where to load a tag. Load rules can also be linked to consent and to the following extensions: Currency Converter Data Validation Channels This article provides information on adding and managing load rules. In this article: How it Works A load rule determines when a tag loads on your site or app. A load rule is one or more conditions that are based on the values in the data layer. For example, a load rule condition that identifies your search page might be: page_type equals search The default load rule is All Pages. Boolean Logic Multiple conditions can be combined using Boolean logic to form more complex load rules. For example, to load a tag on the search page, but only when the user is not logged in, the load rule conditions might be: page_type equals search AND is_logged_in equals 1 This complex logic can be combined into a single rule or created as two rules and then enforced using the Match All Rules setting. AND Logic Use AND logic to create a rule that is true only when all of the conditions evaluate to true. For example, a rule that combines 3 conditions using AND logic evaluates to true only if each individual condition also evaluates to true. If any of the conditions evaluate to false, then the entire rule also evaluates to false. OR Logic Use OR logic to create a rule that is true when any of the conditions evaluate to true. For example, a rule that combines 3 conditions using OR logic evaluates to true if any of the individual conditions also evaluate to true. A rule that uses OR logic only evaluates to false if all of the individual conditions also evaluate to false. Comparison Operators Each rule condition uses a comparison operator and a variable from the data layer. The following table lists the available comparison operators that can be used in load rule conditions. For operators that include (ignore case) in the name, the text value of the variable is converted to lowercase before the comparison. Comparison Operator When a tag loads on a page contains contains (ignore case) The variable contains the specified sequence of characters. does not contain does not contain (ignore case) The variable does not contain the specified sequence of characters. does not end with does not end with (ignore case) The variable does not end with the specified sequence of characters. does not equal does not equal (ignore case) The variable does not equal the specified value. does not start with does not start with (ignore case) The variable does not start with the specified string of characters. ends with ends with (ignore case) The variable does not end with the specified string of characters. equals equals (ignore case) The variable equals the specified value. greater than The variable is greater than the specified value. greater than or equal to The variable is greater than or equal to the specified value. is badge assigned The badge is assigned to the visitor. For use with data layer enrichment. is badge not assigned The badge is not assigned to the visitor. For use with data layer enrichment. is defined The variable is defined in the data layer. is not defined The variable is not defined in the data layer. is populated The variable is defined in the data layer and is not blank or empty. is not populated The variable is defined in the data layer and is blank or empty. less than The variable is less than the specified value. less than or equal to The variable is less than or equal to the specified value. regular expression The variable matches the regular expression. starts with starts with (ignore case) The variable begins with the specified sequence of characters.  Managing Load Rules Load rules can be managed either from the Load Rules screen or from the expanded tag details screen.  In the list view on the Load Rules screen, shown below, the Used In column shows the number of tags that are using the load rule. The UID column displays the numeric identifier for each load rule. This value can be useful when debugging utag.js. Sort the List of Load Rules The list of load rules is sorted by UID, in ascending order, by default. You can also sort the list of rules by Name, Date Modified, or Modified By by clicking the column heading. Name – Sort load rules by rule name, in alphabetical order, or reverse alphabetical order. Date Modified – Sort load rules by modified date, most recent first or oldest first. Modified By – Sort load rules by email address of the last user that modified the load rule, in alphabetical order, or reverse alphabetical order. UID - Sort load rules by UID, either ascending or descending. Create a Load Rule Use the following steps to create a load rule: On the Load Rules screen, click + New Rule. The Add Rule dialog is displayed. Add a Title for the load rule, and optional Notes if needed. Use the drop-down lists to select a Variable and an Operator, then enter a Value. To add another condition using AND logic, do one of the following: Click + next to the default conditional statement. To create a copy of a conditional statement using AND logic by clicking the row menu and selecting Duplicate Row. The duplicate conditional statement can be edited as needed. To add another condition using OR logic, do one of the following: Click +OR. Create a copy of a condition using OR logic by clicking the condition menu and selecting Duplicate. The duplicate condition can be edited to create a new condition. To expand long values, such as a URL, do one of the following: Click the row menu and select Expand Value. Click the condition menu and select Expand All Values. To remove a condtional statement from a condition, click the row menu and select Remove Row. To finish, click Apply. Click Save/Publish. Assign Load Rules to a Tag To assign load rules to a tag, expand the tag details and click Edit in the load rules area. You can also create, edit, copy, activate, deactivate, and delete load rules from the tag details area. Select the checkbox next to the load rule that you want to scope to the tag. If you select more than one load rule, the following options are available to determine which Boolean logic to apply to the selected load rules: Match All Rules Select this option to apply AND logic to the load rules. The tag loads only when all of the selected load rules evaluate to true. Match Any Rule Select this option to apply OR logic to the load rules. This tag loads when any of the selected load rules evaluate to true. View Load Rule Details On the Load Rules screen, click a load rule. The detailed rule screen is displayed. The Configuration tab displays the title and logical conditions of the rule. The Tags tab displays a list of the tags scoped to the load rule. To go to a scoped tag, click the tag. The Consent tab displays information about consent that is linked to this rule. Add a Label to a Rule Labels can be used to organize and uniquely identify rules in your profile. Use the following steps to add an optional label to a load rule: In the detailed rule screen, click Apply Label. To apply an existing label, select a label. To create a new label, click Manage Labels. For more information, see Labels. When you have finished applying labels, close the Add New Label screen. To save the newly applied label, click Save/Publish. Activate or Deactivate a Load Rule Deactivating a load rule turns it off, but keeps it in your profile for future use. When a load rule is deactivated, it remains in the profile and can be reactivated later. When a deactiviated rule is linked to a tag or to consent, the deactivated rule is removed from the logic. If the deactivated rule is is the only linked rule, the all pages load rule is linked to the tag or consent. When a deactivated rule is linked to an extension, the extension is flagged with an error and the user must link an active rule. To deactivate a load rule, go to the Load Rules screen, then click the ON toggle button of the load rule that you want to deactivate. If the rule is in use, you need to confirm that you want to turn it off. The toggle button changes to display OFF. To reactivate a load rule, click the OFF toggle button. Delete a Load Rule You can delete a load rule to remove it from the profile. Deleting a load rule removes all instances of that load rule from the utag.js file. Use the following steps to delete a load rule: On the Load Rules screen, click the load rule that you want to delete. In the Details screen for the rule, click Delete. A confirmation dialog is displayed. To confirm, click Delete Load Rule, otherwise, click Cancel. If the load rule you want to delete is in use, a message is displayed with the details. To continue and delete the load rule, click Delete. Examples AND Logic The following example shows a load rule to identify the checkout page of the site for a customer that is buying shoes. This example uses an AND condition, so the following two conditions must be met: pathname contains checkout.html product_category contains (ignore case) shoes If both conditions are true, the load rule evaluates to true. If any of the conditions in an AND statement are false, the load rule evaluates to false. OR Logic The following example uses an OR condition. This rule loads a tag on a page if the pathname contains checkout.html OR if the product_category contains shoes . If one of the statements is true, the rule evaluates to true. If all of the statements in an OR statement are false, the load rule evaluates to false. When a rule contains multiple OR condidtions, evaluation of the rule stops when a true statement is found. The remaining statements are not evalutated because one true statement means the rule is true. Using URL Components in Load Rules The components of a URL can be useful when creating load rule conditions. A URL typically consists of the following components: Protocol – The method used to process the URL. For example, HTTP or HTTPS. Domain – The domain name. For example, www.tealium.com. Path – The section and page on the site. Hash – Begins with a hash mark (#) and identifies a section within the page. Query String – Begins with a question mark (?) and specifies key/value parameters containing dynamic data passed to the page. URL Example: http://www.tealium.com/app/solutions/?example=test&example2=test2#section3 Data Layer Variables In the data layer, the components of a page URL are stored in DOM variables, as follows: dom.domain : "www.tealium.com" dom.pathname : "/app/solutions/" dom.query_string : "example=test&example2=test2" dom.hash : "section3" dom.url : "http://www.tealium.com/app/solutions/?example=test&example2=test2#section3" Example using Domain If a site consists of several domains, you may need to create a load rule to load tags for pages in a specific domain. The following example shows a load rule for pages in domain1.com : Example Using Domain AND Pathname To load tags on the homepage for domain1.com , use the following rule: Example of Pathname to Specify a Section of a Domain To load tags on pages in the support section of domain1 , use the following rule: Example of Pathname AND Hash, OR Querystring To load tags for support pages containing a section named section2 or when there is a query string that contains support=true , use the following rule: Using Time-Based Conditions You can use time-based conditions, which specify a date and time range, in a load rule along with one or more variable conditions. The date and time range specifies a time period in which the rule is active. The time/time zone used for the load rules is determined by the visitor's browser, not the server or the visitor's time/time zone. Use the following steps to add a date range condition to a load rule. Click Add a date range condition. The date and time range dialog is displayed. Click in the Start Date field to select a start date from the calendar. Click the default time to select a different start time. Click in the End Date field to select an end date from the calendar. Click the default time to select a different end time. Click Apply. Special Considerations The following special considerations may apply: If no time range is specified, the default values any day and any time are used. The date or time that is highlighted when you click on a field is the current date or time. You can specify only one date range condition per load rule. To apply more than one date range to a tag, you must create another load rule with the second date range. To use UTC time instead of the browser's local time, see Time-based Load Rule using UTC. ... View more

This article describes how to add and configure connectors for Tealium EventStream API Hub and Tealium AudienceStream CDP. In this article: How it Works A connector is an integration that transmits data between Tealium and another vendor in real-time.  A connector offers actions that represent vendor-supported APIs. An action is triggered in real-time by an incoming event from a feed or a visitor joining or leaving an audience. An action sends data based on mappings that associate Tealium attributes to the expected vendor parameters. Terminology Connector A connector represents the connection to your vendor account. This is configured using credentials such as an account ID, username and password, or an API key. Action An action is a vendor operation, such as triggering an email, building a custom audience, or managing leads. Actions vary depending on the vendor service. Multiple actions can be associated with a single connector. Frequency Cap A connector action performs in real-time, but some actions are designed to have a wait period before they are triggered. The frequency cap allows you to set a downtime period for actions so that they do not trigger immediately. Learn more about Frequency Capping and Prioritization Source Source indicates the origin of the data being acted upon. A source can be an audience or an event feed. Consent Categories Each connector in the marketplace has one or more consent categories assigned for each available action. To view the consent category for a specific connector, click the Information icon next to the connector action. AudienceStream is categorized in the CDP consent category and DataAccess is categorized in the Big Data consent category. For additional information about server-side consent, see Consent Preferences Manager. Add a Connector Use the following steps to add an EventStream or an AudienceStream connector: Navigate to EventStream > Event Connectors or to AudienceStream > Audience Connectors. Click + Add Connector. Browse or search for a connector, then click the connector to add. The connector summary, including links to vendor documentation and configuration instructions displays. Click Continue. The Select Source screen displays. Select a Source To create an action, first select the type of data you want to send and configure the vendor service. Select a Source for EventStream Select a Data Source. Select an Event Feed and click Continue. Select a Source for AudienceStream Connector actions that send audience data are controlled by triggers that determine when to fire the action. Triggers can only be applied to an audiences and not to events. Select an Audience. Select a Trigger. Joined Audience - Trigger the action if a visitor joined the audience during this visit. For example, when a Cart Abandoner or Frequent Shopper joins an audience. Left Audience - Trigger the action if a visitor left the audience during this visit. In Audience at start of visit - Trigger the action at the beginning of the visit if the visitor is already in the audience. In Audience at end of visit -Trigger the action if the visitor is in the audience at the end of the visit. To limit how often this action triggers, toggle Frequency Cap to On, then select an Action Priority and an Action Cooldown Group. For more information, see Action Frequency Capping & Prioritization. Configuration In the Configuration step specify the credentials for your account with the vendor. This is usually an account ID, username and password, an API key, or other settings required by the vendor. In the Name field, enter a meaningful name for this instance of the selected connector. Under Authentication, provide your login credentials, token or password, Account ID, and any other information required for establishing a connection with the vendor service. Click Done. Action Settings Use the following steps to add actions for this connector: Click Continue to add a connector action. The Add Action dialog displays. In the Action Name field, type a unique name for this action. This list varies, depending on the connector. Select an Action Type. Complete the required fields for the action selected, using pre-populated drop-down lists where available. When  a value is selected or entered for required fields, COMPLETED is shown. Expand each section to complete any optional fields as needed. If the connector supports visitor segmentation, click Create Custom Audience to create a custom audience. Click Finish. Save and Publish your profile. The actions you configured will now fire when the trigger conditions are met. Map Attributes (Optional) A connector action sends data according to the mapping configured. Some connectors offer the ability to map vendor parameters to Tealium attributes. This section describes how to map these attributes when this option is available. Use the following steps to map Tealium attributes to the parameter expected by the vendor: Scroll to the bottom of the connector Actions list and click Custom Attributes to expand. Click + Add Mapping. In the Map field, select an attribute. This list is populated based on the Source you select. For example, choosing an audience displays all visit and visitor-scoped attributes but does not display event attributes. In the To field, select a vendor parameter to map the attribute data to. If the To option is preselected, you are required to send data to that endpoint. You can optionally enter a custom name if the vendor supports custom parameters. Click Back to modify, or click Finish. Save and Publish your profile. Test your Connector After you have added and configured a connector, you need to test it. The easiest way to test your connector is by using the Trace Tool, as follows: Start a new trace. Examine the real-time log. Check for the action you want to validate by clicking the Actions Triggered entry to expand. Find the action you want to validate and view the log status. Managing Connectors This section describes how to turn a connector off or on, copy a connector and the associated configuration settings, and delete a connector. Turn a Connector or Actions On or Off Use the On/Off toggle to turn on or off a connector or action. If you turn off a connector, all associated actions for that connector are also turned off. Duplicate a Connector Use the following steps to duplicate a connector and the actions associated with the connector: Navigate to the connector, expand the menu, and click Duplicate. A new, identical connector, including the associated actions, is shown in the list of connectors. The connector name is appended with " - copy". (Recommended) Expand the menu again and click Edit. Rename the connector and click Done. (Optional) To add or edit actions associated with the new connector, click + Add Action. Follow the normal steps to add actions and click Finish. Save and Publish your changes. Delete a Connector To delete a connector: Navigate to Connectors. If there are actions associated with the connector, they must be removed before the connector can be removed, as follows: Click on an action to expand it. Click the menu and then click Remove. If the connector is not shown in the list, select Show All Available Connectors. Connectors with no associated actions are not included in the list by default. Expand the connector menu, and click Remove. A confirmation message displays. Confirm that you want to delete the connector and click Remove. Get a Connector ID To get the connector ID: Navigate to Connectors. Expand the menu for the connector and click Get Connector ID. Copy an Action ID To copy the action ID: Navigate to Connectors. Select an action, then click Details. Click the copy icon for the Action ID. Deprecated Connectors and Actions Connectors and actions can be deprecated, which means they may be unsupported or removed in the future. Deprecation typically occurs when a connector or an action has been replaced with a newer version or a new connector or action that should be used instead. There are two types of deprecation, as follows: Functional Deprecation – The connector or action is deprecated, and may be removed in the future, but is still working. Full Deprecation – The connector or action is deprecated and no longer works. Actions for a fully deprecated connector are not executed. When a connector or an action is deprecated, an icon is shown next to the connector or action in the connector list. When you hover over the icon, a message is displayed that specifies whether the deprecated connector or action still works.  Screen Navigation Overview Screen The connector overview screen summary displays the following metrics as columns: Total Total actions triggered. Click the Information (i) icon to display the timeline for the total in this column. Success Number of action successes. Error Number of action errors. Data Source (EventStream) or Audience (AudienceStream) Data source or audience associated with the connector. Feed (EventStream) or Trigger (AudienceStream) Name of the feed or trigger for the action. Expand the Add Action menu to quickly access the Edit, Duplicate, Get Connector ID, or Remove features. Reporting Chart for Actions The following sections describe how to view the reporting chart, view error details, and download error reports. View the Chart When you click on a connector action, the chart displays the number of times the action executed each day.  You can view the graph for a rolling day, week, or month. Successful actions are shown in gray and errors are shown in red. Click any part of the chart to view a summary of the data for that display. View Sampled Errors Use the following steps to view sampled errors for a connector: Click an action for the connector you want to view. From the connector summary, select Rolling Day, Rolling Week, or Rolling Month. Below the graph, a list view of error messages is shown. Each entry in the list displays the error category, the number of sampled errors included in the report, a message with a description of the error, and the total number of occurrences of the error. To view the details for an error, click the right arrow next to the category to expand. The detailed view includes a sample of the affected code with a timestamp containing the day of the week, the date, and the time. Download Sampled Errors Use the following steps to download sampled errors for a connector: Click an action for the connector you want to view. From the connector summary, select Rolling Day, Rolling Week, or Rolling Month. Click Download Sampled Errors. A .csv file is saved to your default download location. Open the .csv file to examine the details or share the file with others for further collaboration. FAQ Restricted Data Connectors do not honor restricted data. This means that attributes marked as Restricted Data are always included, whether you are sending them through mappings or as part of the visitor profile. This cannot be changed. Learn more about Restricted Data. IP Whitelists If a connector you use has strict rules about which systems it accepts requests from, you can whitelist the IP addresses of the Customer Data Hub. The IP addresses that make connector requests can be found in the IP Addresses for Customer Data Hub. Retries When a connector action fails, it makes up to 2 additional attempts to trigger the action, which occur immediately. A retry is attempted when the following responses are received: "Connection reset" "Connection closed" "Connection reset by peer" A retry is not attempted when the following responses are received: "Response Timeout - Vendor API did not respond within 5000 milliseconds" The request payload was sent, but the vendor did not send a response within our allowed time of 5 seconds. It's possible that the request succeeded on the vendor's side but since it took longer than 5 seconds to get a response we treat it as a failure.  If the initial action fails, but a retry succeeds, it is logged as a success in the reporting chart. ... View more

This article describes how to use the template status checker (formerly the tag status checker) to scan your templates and display information about version numbers and the modification status. In this article: Requirements To use the template status checker you need the Manage Tag Templates permission. How It Works The template status checker tool compares each of your templates to the latest system version available. After running the tool, a status for each template is displayed based on its version and modification status. The status report allows you to quickly determine if updates are needed. Template Status Summary Window After completing the scan, a detailed report displays the following columns: Status The status or characteristics of the template in color-coded icons. The number that displays next to an icon is the number of templates detected with that status. Tag Name The name of the tag. Latest Version The latest version available to the tag template marked by the version number or the date. Version The version detected by the tool, displays as Latest or Old. UID The unique identifier (UID) for the template. Template Status Symbol Definitions The following statuses are reported. Note that a template may have more than one status. Symbol Status Description New Version Available Indicates that a newer version of the template is available. Latest Versions Indicates that this template matches the latest system version available. Not Customized Indicates that the template has not been modified from its original state when it was added. Customized Indicates that the template has been edited from its original state by a user. Deprecated Indicates that this version of the template is no longer supported or offered. It is likely that a new version of the template has been released to replace this one. Version Mismatch Indicates that the template does not match the currently selected version of the tag in the tag configuration settings. Unknown Indicates that the system is unable to determine the current state of the template. Unsaved Changes Indicates that this template has pending changes that have not been saved in the profile. Running the Template Status Checker There are two methods for activating the template status checker: From the Tags screen Click the Run Template Status Checker button that appears at the top of the list view. From the user admin menu From the user admin menu, click Template Status Checker. From the Tags Screen Use the following steps to check the status of your templates from the tags screen: Go to iQ Tag Management > Tags. In the header toolbar, click Run Template Status Checker. The Status column displays in the list of tags with a colored indicator for the status of each template. From the User Admin Menu Use the following steps to check the status of your templates from the user admin menu: From the user admin menu, click Template Status Checker. Select the type of scan to run. Full Scan Scans all active and inactive templates in your profile. Active templates Scans only active templates in your profile. Specific template Scans only the template you specify. Enter the name of the tag or consent manager component in the text field. Click Scan. The template status checker displays the results. Click a table row to view that template. Filter By Status After the template status checker runs, use the status results to filter the tag list by template status. Use the following steps to filter the tag list by template status: Select the Template Status drop-down list and click a status. The list of tags adjusts accordingly. (Optional) Click Re-Run to run the tool again. Additional Resources Managing Templates Release Notes - utag.js ... View more

Live Events and Feeds are used to manage and inspect incoming data. This article shows how to inspect incoming event data, create and manage feeds, and evaluate data quality. This article covers the following topics: Table of Contents Placeholder About Live Events Live Events shows data coming into the Customer Data Hub in real-time. The Live Events chart displays events coming from all data sources and all event feeds. Each bar in the chart has a height to indicate the volume of events detected. Click a bar to inspect the details of a sampling of those events. If you have active event specifications, the chart reflects the quality of the incoming data with green and red segments to represent valid and invalid events, respectively. Using Live Events Access Live Events by navigating to EventStream > Live Events. You control which events are displayed in the chart using the Data Sources and Event Feeds drop-down menus. The default selections are "All Data Sources" and "All Events". Adjusting these menus refreshes the chart and displays the event activity for the selected combination. If you select a specific event for Event Feed, Live Events displays data for that event only.  To compare an event feed to all event data, click Compare against All Events. For example, you can create event feeds for specific countries or regions, then compare a country or region event feed to all events. Using a Trace ID Use a Trace ID to filter out all incoming events except for the ones you trigger. A Trace ID is a temporary, unique identifier to be inserted into your event tracking code (or the Trace Tool) so that only specific events are displayed in Live Events. This is commonly used for testing purposes.  To set up a trace: Click Trace ID. The trace options modal displays. Click Start Trace and follow the instructions. Copy the generated Trace ID and click Continue. Open a new Chrome browser window with the page to test. Open Tealium Tools > Trace and enter the Trace ID. The Live Events now shows only events triggered during your traced session. You can start a new trace or rejoin an existing trace following the same steps.  Event Specification Filters If you have event specifications defined, Live Events displays the quality of your incoming data. Each bar in the chart is segmented according to the status of the event specifications applied. The following filters can be toggled on or off to adjust the display of the chart: Valid "Valid" events satisfy the requirements of an active event specification. This means that the events have a known value for the tealium_event attribute and all the required attributes from the specification. The more valid events you see the better. This means your installations are sending the data expected in your specifications. Invalid "Invalid" events match an event specification, but do not have the required attributes. This means that the events have a known value for the tealium_event attribute, but they are either missing required attributes or the attributes contain unexpected values. These issues can be resolved by fixing the installation code that is sending the events or, in some cases, adjusting the event specification. No Spec Events marked as "No Spec" do not have a matching event specification. This means that the events either do not have the tealium_event attribute or the value does not have a corresponding event specification.  Viewing Event Details Click a bar in the chart to view the event details from an incoming data sample. The data sample is limited to 10 events per bar in the chart. Events are primarily identified by the tealium_event attribute. The detected value of this attribute is displayed in the heading of the event detail. If tealium_event has a corresponding event specification, the event is displayed as either valid or invalid according to the requirements in the specification. The heading also displays the data source from which the event originated. The event attribute details are organized into the following attribute types: Universal Variable, JavaScript Page Variable, HTML Metadata, First-party Cookie, Query String Parameter, and Tealium-provided.   Defining Unknown Attributes An unknown attribute is an attribute detected in the incoming event that has not yet been created in your account as an event attribute with a data type (eg. string, number, Boolean, etc.). Before you can use an attribute in your account, it must be created as an event attribute. In the event details view, unknown attributes are indicated in the Data Type column as "Unknown". Unknown attributes can be defined directly from this screen by using the Quick Add action, as follows: Next to an "Unknown" attribute, click the more options icon and then click Quick Add. Select the desired data type. Click Define. The attribute now displays its new data type. Previewing and Activating Event Specifications A standard set of built-in event specifications are available to be added to your configuration. If an incoming event matches a built-in event specification that has not yet been activated, you can preview and activate the event from the event detail view. To preview and activate a matching built-in specification: Click Preview Event Spec. The event attributes changes to display a preview of the attributes required for that specification. This shows you how your event compares to the built-in specification. Click Create Event Specification. The Add Event Specification modal appears. Enter notes and adjust any additional attributes to be included. Click Finish. Publish your account to view the new specification applied to incoming events. Creating Custom Event Specifications Events with a custom value for tealium_event  display as "Unknown" in the event details view if they do not have an associated event specification. When this occurs, you can create a custom event specification directly from the event details view based on the detected value of tealium_event and the attributes of the event. To create a custom event specification for an unknown event: Click Create Event Specification. All event attributes from the active event are pre-populated in the event specification. Set the name of the specification (the value expected in tealium_event ). Set the Data Type for all unknown attributes. Adjust the list of attributes as desired: Add more attributes by clicking +Add Attribute. Remove pre-populated attributes by clicking the Remove button. Mark attributes as required or optional. Click Finish. Save and publish your account. About Event Feeds Event feeds are groups of events that match specific conditions based on their attributes. Feeds can be sent to connectors or a data storage solution such as EventDB or EventStore. The default event feed is named "All Events" and displays all incoming events. The default feed cannot be edited or deleted; however, additional feeds can be created to identify subsets of events based on their attributes. Event Feed Details By default, event feeds are listed in alphabetical order with "All Events" listed at the top. The list displays the following information: Total Volume – The total number of events detected from all data sources over the last 30 days. Assigned Actions – The number of connector actions linked to the feed. EventStore – Indicates if the feed is enabled for EventStore. EventDB – Indicates if the feed is enabled for EventDB. From the list of event feeds, click a feed to view the details. The details display the following: Feed Activity Chart – The number of events detected from all data sources over the selected time range. Conditions – The logic used to identify events in the feed. Assigned Actions – The connector actions linked to the feed. Creating Event Feeds Use the following steps to create an event feed: In the sidebar, go to EventStream > Live Events. Click + Add Event Feed. The Create Event Feed dialog displays. Set the Title and Notes. (Optional) Add Labels. Enable the feed for EventStore or EventDB. This setting requires your account to be enabled for DataAccess. Set the conditions for the feed. Click Save. Save and publish your account.   ... View more

Trace is a testing and inspection tool for your EventStream and AudienceStream configuration that allows you to capture your workflow as a visitor and watch how events and customer data are processed in real-time. This article describes how to start and stop a new trace, join an active trace, and view the overview panel and trace log.  In this article: Prerequisites The following items are required to use Trace: EventStream or AudienceStream If you do not already have access to one or both, contact your account manager to activate. Tealium Tools Browser Extension Tealium Tools is needed to start and end a trace session in your browser. How It Works Trace provides an inside view into the inner workings of EventStream and AudienceStream. The trace tool is critical for testing your configuration. You can use trace to observe the details of a predefined workflow, ensure that attributes update correctly, rules are correctly applied, and that actions trigger as expected. From the Trace interface, you can: Start or stop a trace Join an active trace View predefined workflows and event log details in real time Establish rules and view results Get replay code to replay, pause, or resume an event View a scrolling summary of actions, events, and audiences View the details of an event or processing step View snapshots of visitor profiles Get a Trace ID After you have saved your Customer Data Hub configuration and are ready to begin testing your enrichments, audiences, and actions, you need to get a Trace ID to use in the Trace tool. Use the following steps to get a Trace ID: Go to Server-Side > Trace. Click Start. A Trace ID is displayed. Copy the Trace ID. The lifespan of a trace ID is 24 hours from time of issue. Start a Trace Use the following steps to start a trace: Open a new Chrome browser window and navigate to the first page of the workflow to test. Open the Tealium Tools browser plug-in and click AudienceStream Trace. Paste or enter the Trace ID. If you are tracing a session across multiple domains, deselect Trace me as a new visitor. Click Start Trace. Click Exit and then press ESC to exit the tool. Return to the Trace ID screen in Customer Data Hub, and click Continue. As you navigate through your workflow in the browser window, trace sends information to the Customer Data Hub and displays a timeline of visitor activity.  The trace screen provides a summary of the events, actions, and functions, as well as a detailed list of all events, actions, and functions. For example: Start or Join a Trace Using the Slide-Out Screen If you have closed the trace screen, click Server-Side > Trace and the screen slides out again. You can use the trace screen to start or join a trace without leaving your current location in the product. When a trace is in progress, a blue arrow next to Server-Side > Trace pulses.   Replaying Trace Events from the Trace Screen From the trace screen, you can replay, pause, or resume an event by clicking one of the icons in the trace summary. The following table provides details on each of the trace icons. Play at normal speed. The default setting used to replay an event is normal speed. Play at twice the normal speed. Pause the ongoing trace. When paused, trace continues to process new events behind the scenes but does not display new log entries until you click pause again to restart. View the latest visitor profile. Displays a snapshot of the profile for the latest visitor in JSON format. Click OK to exit this window. Get code to replay events generates a curl command for each event. You can run the curl commands in a terminal window to replay an event in trace without having to recreate the configuration steps on the web page. To replay a single event, copy and paste the matching curl command in the terminal window and press Enter to run the command. To replay multiple events, click Download Bash Script to download the .sh file. Use the terminal window to run the .sh script.  Exit the current trace. If the trace is still active on the web page, you can rejoin the trace using the Trace ID. Viewing Event Details The following image shows the parts of the trace interface. The Trace Log is a real-time scrolling summary of actions, events, and audiences. The Overview Panel displays a snapshot of the detailed activity. Search  can be used to find specific attributes in the list of visitor and visitor-scoped attributes. The attributes in the list are grouped by data type (Numbers, Dates, and so on). Filters can be used to filter these attributes. Filters Filtering allows you to determine if the attributes and the configurations tied to them are functioning properly. Using filters, you can choose how to view the attributes and their values. You can filter attributes by Label (if you have added labels for attributes) or by Type, where Type is one of the following  All Shows all attribute types and values set up in your AudienceStream profile. Existing Shows only the attributes that acquired a value after AudienceStream processing. Modified Shows only the modified, or enriched, attributes. Trace Log In the trace log, clickable text is blue, other text is gray. The timestamp adjacent to the log entry displays the time of the log entry. To view the details of an event, click the blue event text to slide out a detailed view of the event. You can minimize the trace window to continue the process while moving on to other feature of the UI. Stop a Trace Use the following steps to end an active trace and associated visitor session. Open a new Chrome browser window and navigate to your site. Open the Tealium Tools browser plug-in and click AudienceStream Trace. Verify the Current Domain and Current Trace ID of the trace you want to stop. Click Stop Trace. Join an Active Trace Use the following steps to join a trace that is currently in progress: You must exit any active traces before you can join a trace. Click Server-Side > Trace. Click Join. Enter the known Trace ID for an active trace. Click Join. The trace log is displayed. Additional Information Starting a Trace from the Browser Console  Starting a Trace from an App ... View more

This article describes how to set up the Foresee Tag in your Tealium iQ profile. Table of Contents Placeholder Tag Configuration First, go to Tealium's Tag Marketplace and add the Foresee Tag to your profile (how to add a Tag?). After adding the Tag, configure the below settings: Title: The default is "Foresee". You may replace it with a custom name of choice. File Path: The URL where your Foresee files/configurations are hosted. E.g. "//gateway.foresee.com/sites/XXX/XXX/gateway.min.js" Load Rules Load Rules determine when and where to load an instance of this Tag on your site. 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 Foresee Tag are built into its Data Mapping tab. Available categories are: Standard Tag Destination Description File Path The URL where your Foresee snippet is hosted Vendor Documentation Foresee Developer Portal ... View more

Salesforce Marketing Cloud Journey Builder empowers you to guide customers on 1:1 journeys across channels and devices to deliver the right digital marketing solution, via the right channel. This article walks you through the process of setting up the Connector in your Customer Data Hub profile. This connector is no longer available in the connector marketplace. For the latest version of this connector, which includes OAuth 2.0 support, see  Salesforce Journey Builder with OAuth Connector Setup Guide. Table of Contents Placeholder Requirements Salesforce Marketing Cloud App Client Credentials Salesforce Marketing Cloud Account Journey Event Entry Definition Supported Actions Action Name Trigger on Audience Trigger on Streams Send Event to Initiate Journey ✓ ✗ Configure Settings Go to the Connector Marketplace and add a new Salesforce Marketing Cloud Connector. Read the Connector Overview article for general instructions on how to add a Connector. To configure your vendor, follow these steps: In the Configure tab, provide a title for the Connector instance. Provide your Marketing Cloud App client ID and client secret. Click Test Connection to verify API connectivity with the provided credentials. For more information, see: Get App Client Credentials. Action Settings - Parameters and Options Click Next or go to the Actions tab. It's where you'll set up Actions to trigger. This section describes how to set up Parameters and Options for each Action. Action - Send Event to Initiate Journey Parameters Event Entry Definition (REQUIRED): From this list, select an event entry definition that specifies the event data format to initiate journey. Contact Key (REQUIRED): Map an Attribute to uniquely identify the contact event data. Event Data (REQUIRED): Map Attribute(s) to contact event attributes. Attribute names must match Data Extension attributes for selected Event Definition (see: Entry Events and Data Definitions). Disable Auto Create Contact: By default, new contacts are created when sending event data with new contact keys. New contacts are then available to be injected into journeys. Check this option to disable automatic creation of contacts. For more information, see: Admit Contacts via API Vendor Documentation Get App Client Credentials Admit Contacts via API Entry Events and Data Definitions ... View more

LINE lets you interact directly with individual users through either a LINE official account or a LINE@ account. You can send interactive messages from your server to users at any time. This article describes how to set up the LINE Connector service in your Customer Data Hub profile. Table of Contents Placeholder Requirements LINE Channel Access Token (Get started with the LINE Developers Messaging API.) Supported Actions Action Name Trigger on Audience Trigger on Streams Push Message - Text ✓ ✗ Push Message - Image ✓ ✗ Push Message - Video ✓ ✗ Push Message - Audio ✓ ✗ Push Message - Location ✓ ✗ Push Message - Sticker ✓ ✗ Configure Settings Go to the Connector Marketplace and add a new LINE Connector. Read the Connector Overview article for general instructions on how to add a Connector. To configure your vendor, follow these steps: In the Configure tab, provide a title for the Connector instance. Enter the channel access token that you set up with LINE for your account. Provide additional notes about your implementation. Action Settings - Parameters and Options Click Next or go to the Actions tab. It's where you'll set up Actions and trigger them. This section describes how to set up Parameters and Options for each Action. Action - Push Message - Text Parameters Contact ID (Required): This is the ID received from the Webhook that is configured in the Channel Console in LINE Business Center. When a user performs an action such as adding your account or sending a message, an HTTPS POST request is sent to the Webhook URL. Message Data (Required): The content of the message to send to the user. This field is limited to 2000 characters and supports unicode emoticons. This field also supports the Tealium templating engine. Template Variables (Optional): If using the templating engine, template variables will be used. These fields map Attributes to variable names that are used in the message data. Action - Push Message - Image Parameters Contact ID (Required): This is the ID received from the Webhook that is configured in the Channel Console in LINE Business Center. When a user performs an action such as adding your account or sending a message, an HTTPS POST request is sent to the Webhook URL. Original Content URL (Required): The URL of the image to send to the user. The URL must use HTTPS and should not exceed 1000 characters. The image must be a JPEG with a maximum dimension of 1024x1024 and a maximum size of 1 MB. Preview Image URL (Required): The URL of the preview image to send to the user. The URL must use HTTP and should not exceed 1000 characters. The image must be a JPEG with a maximum dimension of 240x240 and a maximum size of 1 MB. Action - Push Message - Video Parameters Contact ID (Required): This is the ID received from the Webhook that is configured in the Channel Console in LINE Business Center. When a user performs an action such as adding your account or sending a message, an HTTPS POST request is sent to the Webhook URL. Original Content URL (Required): The URL of the video to send to the user. The URL must use HTTPS and should not exceed 1000 characters. The video must be a MP4 with a maximum duration of 1 minute and a maximum size of 10 MB. Preview Image URL (Required): The URL of the preview image to send to the user. The URL must use HTTP and should not exceed 1000 characters. The image must be a JPEG with a maximum dimension of 240x240 and a maximum size of 1 MB. Action - Push Message - Audio Parameters Contact ID (Required): This is the ID received from the Webhook that is configured in the Channel Console in LINE Business Center. When a user performs an action such as adding your account or sending a message, an HTTPS POST request is sent to the Webhook URL. Original Content URL (Required): The URL of the audio to send to the user. The URL must use HTTPS and should not exceed 1000 characters. The audio must be a M4A with a maximum duration of 1 minute and a maximum size of 10 MB. Duration (Required): The length of the audio file in milliseconds. Action - Push Message - Location Parameters Contact ID (Required): This is the ID received from the Webhook that is configured in the Channel Console in LINE Business Center. When a user performs an action such as adding your account or sending a message, an HTTPS POST request is sent to the Webhook URL. Title (Required): The name of the location to send to the user. Address (Required): The address of the location to send to the user. Latitude (Required): The latitude of the location to send to the user. Longitude (Required): The longitude of the location to send to the user. Action - Push Message - Sticker Parameters Contact ID (Required): This is the ID received from the Webhook that is configured in the Channel Console in LINE Business Center. When a user performs an action such as adding your account or sending a message, an HTTPS POST request is sent to the Webhook URL. Package ID (Required): The ID of the package to which a sticker belongs. Sticker ID (Required): The ID of the sticker to send to the user Vendor Documentation LINE Developers - Messaging API - Getting Started LINE API Reference - Webhooks LINE API Reference - Push Message LINE API Reference - Send Message Object (Text, Image, Sticker, etc.) Additional References Tealium Webhook - Template Variables Guide ... View more

This article covers the fundamentals of the utag.sync.js script and describes how to enable and install it on your website. In this article: Table of Contents Placeholder Prerequisites To complete the steps described in this article, you must have the following Tealium iQ Tag Management profile-level permissions (Learn more): Manage Tag Template This permission is required to add and manage tag templates. JavaScript Draft Promotion This permission is required to publish JavaScript extensions. How it Works Before You begin, it is important to learn the differences between synchronous (sync) and asynchronous (async) JavaScript and how it relates to your iQ Tag Management installation. (Learn more). The utag.sync.js script described in this article is an additional file that you can add to your pages to support A/B and multivariate testing tags, such as Adobe Target or Optimizely. The script is placed in the <head> section of your page code and loads synchronously to comply with the most common vendor requirements. The file content is managed in iQ Tag Management. This feature is required when using the Tealium Flicker-Free Adobe Target solution. Enable utag.sync.js By default, the utag.sync.js file is not published to the Content Delivery Network (CDN) when you save and publish your iQ Tag Management account/profile. It must first be enabled, saved, and applied at the profile level. Use the following steps to enable the utag.sync.js script: Click Save/Publish. Click Configuration Publish Settings. From the General Publishing tab, scroll down to the Implementation section and toggle the Generate utag.sync.js File option to On. Click Save. Save and Publish your changes to the desired environments. You must publish the latest version of this profile to all of your publish environments. Failure to do so will prevent any page referencing the utag.sync.js file from loading. Once enabled, the utag Sync scope is visible in the Scope drop-down list for a JavaScript or Advanced JavaScript extension. Edit the utag.sync.js File You can add code using one of the following two methods: Recommended: Use an extension set with the utag Sync scope (Learn more) Edit the tag template (Learn more) Add, edit, or modify the content of your utag.sync.js file, as follows: Navigate to the JavaScript Code or Advanced JavaScript Code extension for which you want to modify the file. Click the name of the extension to expand. Select utag Sync from the Scope drop-down list. In the Configuration section, place your cursor in the edit box and add, edit, or modify content as needed. Save and Publish your changes. Add utag.sync.js to Your Site The utag.sync.js script is designed to be placed in the <head> section of a page. For the best user experience as the page renders, the script should be placed in the same location that your vendor code would typically load to ensure that the vendor code loads before the content of the page. The path to the utag.sync.js file contains the following parameters: account The name of your iQ Tag Management account. profile The name of the profile in your iQ Tag Management account. The default value is main. environment (env) One or more publish environments: Dev, QA, Prod, or Custom. Example: <script src="https://tags.tiqcdn.com/utag/[account]/[profile]/[env]/utag.sync.js"></script> Use the following steps to retrieve your specific script from the Code Center for your account: Click Save/Publish in the upper right corner. The Save/Publish dialog displays. Click Code Center in the upper right corner. The Tealium Script tab displays code that you can use to cut and paste into your file. Click the Sample HTML tab to view sample HTML for the utag.sync.js placement. Cut and paste the sample HTML for use on your page as needed. Click OK and then click Cancel to close the window. Additional Information Accessing the Universal Data Object (UDO) The utag.sync.js file will likely load before the Universal Data Object ( utag_data ), therefore the code may not be able to reference those variables. Ensure that you thoroughly test any custom code that you intend to use. Publishing to Production Once utag.sync.js is enabled in the profile, all subsequent publishes to the Prod environment include this file. Advanced and Basic JavaScript extensions can be restricted from publishing to specific environments, which provides you with more control over the environments to which you deploy your sync changes. ... View more

Nielsen Digital Content Ratings (DCR) enables a comprehensive view of digital audiences for content, allowing digital and TV publishers to demonstrate and maximize the value of their content, and advertisers and agencies to plan in a better way across screens. This article describes how to configure the Nielsen DCR Tag in your Tealium iQ profile. Table of Contents Placeholder Tag Configuration First, go to Tealium's Tag Marketplace and add the Nielsen Digital Content Ratings (DCR) - Page Measurement Tag to your profile (how to add a Tag?). After adding the Tag, configure the below settings: Client ID: Your Nielsen client identifier. This is passed to Nielsen in the "nol_ci" key. Sub-brand ID: Your Nielsen Sub-brand ID. This is passed to Nielsen in the "nol_vc" key. App ID: Unique Nielsen ID assigned to player/site. This is passed to Nielsen in the "nol_apid" key. Publisher Name: User-defined string value for identifying your player/site. This is passed to Nielsen in the "nol_apn" key. Collection Environment: Location of Nielsen Collection Environment. This is passed to Nielsen in the "nol_sfcode" key. Use Path for Site Section: When set to "yes", the first folder in the web page's path is used for Site Section. If the first folder is absent or not available, the Site Section value will default to "home". The Site Section value can also be configured through Data Mappings (see below). Site Section reporting is limited to a maximum of 25 unique values (Site Section <= 25). Load Rules Load Rules determine when and where to load an instance of this Tag on your site. Recommended Load Rule: Load on 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 Nielsen Digital Content Ratings (DCR) - Page Measurement Tag are built into its Data Mapping tab. Available categories are: Standard Destination Name Description Client ID Nielsen Client ID. Overrides the value set in the Vendor Configuration. See Tag Configuration above for details. Sub-brand ID Nielsen Sub-brand ID. Overrides the value set in the Vendor Configuration. See Tag Configuration above for details. Site Section Allows you to send custom site sections (limited to a maximum of 25 unique values). This is passed to Nielsen in the "nol_assetname" key. If the mapping returns an empty value, then Site Section will be set to the default value of "home". NOTE: If you are mapping to this destination, be sure to turn off the "Use Path for Site Section" toggle in the Tag settings. Custom Segment A Custom Segment reporting is limited to a maximum of 25 unique values across custom segments A, B, and C (nol_segA + nol_segB + nol_segC <= 25). This passed to Nielsen in the "nol_segA" key. Custom Segment B Custom Segment reporting is limited to a maximum of 25 unique values across custom segments A, B, and C (nol_segA + nol_segB + nol_segC <= 25). This passed to Nielsen in the "nol_segB" key. Custom Segment C Custom Segment reporting is limited to a maximum of 25 unique values across custom segments A, B, and C (nol_segA + nol_segB + nol_segC <= 25). This passed to Nielsen in the "nol_segC" key. Vendor Documentation Static Page Measurement - Implementation Guide Static Lite Page Measurement - Implementation Guide ... View more

The AgilOne Webtag Library is specifically designed to capture data from your customer’s interactions with your web site or application. This article describes how to configure the Tag in your Tealium iQ account. Table of Contents Placeholder Pre-requisites Authentication Key (required for authenticating API calls to AgilOne) Tealium Event Extension (optional but highly recommended) Tag Configuration First, go to Tealium's Tag Marketplace and add the AgilOne Web Tag Tag to your profile (how to add a Tag?). After adding the Tag, configure the below settings: Tenant ID (REQUIRED): The tenant ID you received from AgilOne.You may specify the ID in this field or set it dynamically using Data Mappings. Load Rules Load Rules determine when and where to load an instance of this Tag on your site. Recommended Load Rule: Load on 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 AgilOne Web Tag Tag are built into its Data Mapping tab. Available categories are: Standard Destination Name Description Tenant ID (REQUIRED) Tenant ID Authentication Key (REQUIRED) Authentication Key Value Search Term The keyword used for searching the site Event Name Name of the event you want to trigger. Recommended for triggering events that are not already offered in the Tealium Event Extension. Event Entity URL URL of the page on which the event is happening Event Entity Time (Optional) timestamp of when the event is triggered. AgilOne recommends sending this value ONLY if the timestamp does not equal the time when the event is sent. Event Entity Custom Data * Additional data to send with the Event Entity * Not to be confused with the Event Custom Data category. E-Commerce Since the AgilOne Web Tag 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 Destination Name Description E-Commerce Extension Variable Order ID Unique Order ID _corder Order Total Total value of order _ctotal Order Subtotal Subtotal amount of the order _csubtotal Shipping Amount Shipping Amount _cship Tax Amount Amount of Tax _ctax Order Organization ID Order Organization ID NA Order Invoice Date Invoice Date for the Order NA Order Custom Data Custom Data for Order NA Customer ID Unique customer ID _ccustid List of Product IDs Array of Product IDs _cprod List of Transaction Item IDs List of Transaction Item IDs NA List of Names Array of Product Names _cprodname List of SKUs List of SKUs _csku List of Brands List of Brands _cbrand List of Categories Array of Product Categories _ccat List of Quantities Array of Product Quantities _cquan List of Prices Array of Product Prices _cprice List of Discounts List of Discounts _cpdisc  List of Organization IDs List of Organization IDs NA List of Product Types List of Product Types NA List of Product Subtypes List of Product Subtypes NA List of Product Shipping Revenues List of Product Shipping Revenues NA List of Product Organization IDs List of Product Organization IDs NA List of Product Ship Dates List of Product Ship Dates NA List of Product Invoice Dates List of Product Invoice Dates NA Product Custom Data Product Custom Data NA Customer Destination Name Description Customer Email Customer's email address Customer UUID Customer's UUID Customer Preference DNE Email opt-out value Customer Preference DNM Postal opt-out value Customer Preference DNC Phone opt-out value Customer Custom Custom data about the customer Current Cart Map to these destinations to send data for the current cart items. Destination Name Description Current Cart ID Unique cart identifier Current Cart Quantity Quantity of each item in the cart Current Cart Custom Data Custom data associated each item in the cart To send data for cart updates (addition or removal), use the _cprod E-Commerce mapping. Refer to the Sending Cart Updates section for more. Event Custom Data Use these mappings to send additional data for standard events only. Destination Name Description Event Custom Data for Product View Event Custom Data for Product View Event Custom Data for Search Event Custom Data for Search Event Custom Data for Category View Event Custom Data for Category View Event Custom Data for Brand View Event Custom Data for Brand View Event Custom Data for Cart Update Event Custom Data for Cart Update Event Custom Data for Checkout Event Custom Data for Checkout Triggering Standard Events Standard events supported by AgilOne are triggered through the Tealium Events Extension. That means you don't have to map the event name or trigger value for any event that is supported through the Extension. The Extension introduces standardized event names into your solution, along with a new Data Layer Variable called tealium_event . Each event is assigned a custom condition that matches your data layer implementation. When an event condition evaluates to true, the tealium_event is set to a pre-defined event value. Tealium's AgilOne Webtag template reads the predefined value and accordingly fires the event. For example, when the condition for "Add to Cart" evalutes to "true", tealium_event will be set to “cart_add” and the cart event fires on the cart page. Full list of events supported for AgilOne through Tealium Events Extension: Event Name tealium_event Variable Value Supporting Extension User Login user_login Tealium Events User Logout user_logout Tealium Events Search Page View search Tealium Events Product Detail Page View product_view Tealium Events Category Page View category_view Tealium Events Brand View brand_view -- Add to Cart cart_add Tealium Events Remove from Cart cart_remove Tealium Events Empty Cart cart_empty Tealium Events Checkout checkout Tealium Events To send additional custom data with a standard event, map in the Event Custom Data mappings under Standard Category. Triggering Non-standard Events If the event you want to trigger is not offered in the Tealium Events Extension, there is an alternative. You may use the Set Data Value Extension instead to set the event trigger and event condition. Then, map the trigger variable to the Event Name destination (under Standard Category). The Brand View event is an example of a non-standard event. Follow these steps to trigger the event: Add and configure a new Set Data Values Extension from the Extension marketplace. Scope it to AgilOne Webtag. Set the event_name Data Variable to the text "brand_view". Remember: the "brand_view" value is predefined in the template and cannot be changed. Add an event condition to evaluate the customer's brand view action. E.g.: event_type "equals" "brand_view". If you don't find the Variable you are looking, you may add it on the fly. Go to the Tag's Data Mappings tab and map the event_name Variable to the Event Name destination (Standard category). Sending Cart Updates Adding and removing items from a cart are treated as standard events and, therefore, easily triggered via the Tealium Events Extension. Sending data for the final cart (including the added or removed items) is a three-step process: Configure the Tealium Events Extension to trigger the cart addition/removal event. Go to the Tag's Current Cart mappings and map to the desinations of choice. Go to the E-Commerce Extension and map the newly added or removed cart item to _cprod . This will capture the updated cart items separately. When the add-to-cart/remove-from-cart event fires on a page, our Tag template will automatically piece together the added/removed item(s) with the current cart data and send the complete cart list. To correctly identify a removed cart item, you must map it to both E-Commerce cprod and Current Cart. Vendor Documentation AgilOne Resource ... View more

This is an overview of an example solution for integrating Tealium iQ with your Angular application. The integration works well with the example from Angular's CLI Quickstart and shows how to track both page views and events. If you are looking for the older AngularJS 1.x integration, visit http://github.com/Tealium/integration-angularjs Requirements Tealium iQ Tag Management account Angular application Get the Example Code Download - Tealium for Angular [Example] Installation The installation only requires one file to be added to your application. This service takes care of loading the Tealium utag.js library for your account and handling the tracking calls. To add the Tealium service to your application: Create the directory  ./src/app/tealium  in your application. Copy the file example/src/app/tealium/utag.service.ts into your application at  ./src/app/tealium . Initialization The installation adds a new class to your application called TealiumUtagService which is now available by registering it as a provider to a component. Add this class to your application constructor and initialize it with the setConfig() method using the following parameters: account - the name of your account profile - the name of your profile within your account environment - one of "dev", "qa", or "prod" // example constructor constructor(private tealium: TealiumUtagService) { this.tealium.setConfig({ "account" : "your_account", "profile" : "your_profile", "environment" : "prod" }); } See example/src/app/app.component.ts for a full example of importing the Tealium service to your application. Tracking Once TealiumUtagService has been initialized you can add tracking calls throughout the application code. Use the view() method to track page views and the link() method to track in-page events. Each method takes an object as the single parameter. For more information on view and link tracking, see Page Tracking and Event Tracking. // Content View event this.tealium.view({ "page_type" : "product", "product_id" : ["PROD123"] }); // Non-view event this.tealium.link({ "event_name" : "user_login", "customer_id" : "0123456789" }); Use the Universal Tag Debugger tool to validate that your code is working as expected.   ... View more

With the Pardot Connector, you can send one-to-one emails based off of audiences. This article describes how to set up the Pardot Connector service in your Customer Data Hub profile. This article covers the following topics: Table of Contents Placeholder Requirements Pardot Account Email and Password API User Key (this can be found in your Pardot account settings) Supported Actions Action Name Trigger on Audience Trigger on Streams Send Email to Prospect ✓ x Create or Update Prospect ✓ x Add Prospect to List ✓ x Opt-out Prospect from List ✓ x Remove Prospect from List ✓ x Configure Settings Go to the Connector Marketplace and add a new Pardot connector. Read the Connector Overview article for general instructions on how to add a connector. To configure your vendor, follow these steps: In the Configure tab, provide a title for the connector instance. Enter your email, password, & API user key that you obtained from Pardot. Provide additional notes about your implementation. Click Test Connection. Action Settings - Parameters and Options Click Next or go to the Actions tab to set up actions and their triggers. This section describes how to set up parameters and options for each action: Action - Send Email to Prospect Parameters Campaign (REQUIRED): Select the campaign you wish to use. If you don't see the campaign you're looking for, you may enter the campaign ID as a custom value. To find the campaign ID, open up the target campaign in Pardot and look for the numeric value at the end of the URL. For example, in this URL: https://pi.pardot.com/campaign/read/id/123 , the ID is "123". For more details about campaign IDs, refer to the articles Sending One To One Emails and Supported Parameters. Email Template (REQUIRED): Select the email template you wish to use. If you don't see the email template you're looking for in this list, you may enter your template ID as a custom value. Like campaign ID, your email template ID is the numeric value at the end of the email template URL in Pardot. A template url will look something like this: https://pi.pardot.com/emailTemplate/read/id/XXXX , where "XXXX" is the numeric ID. Prospect Identifier (REQUIRED): Select an identifier to find a prospect by. prospect_email: an email address associated with a prospect id: A Pardot ID associated with a prospect Options (Optional) Additional Email Options Configure this section to override the "Email Template" attributes. Template Support: "subject", "text_content", and "html_content" options support templating. For these ,reference the template name to generate message data from template. Option Description subject The subject of the email. If configured, the value should be the template key from the Templates section text_content The text body of the email. If configured, the value should be the template key from the Templates section. The template must contain either %%unsubscribe%% or %%email_preference_center%% html_content The HTML body of the email. If configured, the value should be the template key from the Templates section. The template must contain either %%unsubscribe%% or %%email_preference_center%% tags[] Configure an "array/set" attribute type for one or multiple tags. This is the name of the tag you'd like to create or associate with this email list_ids[] Configure an "array/set" attribute type for one or multiple lists. This is the ID of the list you'd like to mail to suppression_list_ids[] Configure an "array/set" attribute type for one or multiple lists. This is the ID of the list you'd like to suppress mailing to   If no email_template_id is provided then either (from_email & from_name) or from_user_id is required If the Email Template section is not configured, the "name", "subject", and either the "text_content" or "html_content" is required If the Email Template section is configured, the email template will be used first. "name", "replyto_email", "subject", "text_content", and "html_content" will override the template contents if they're provided Template Variables Provide template variables as data input for templates. See: Template Variables Guide Name nested template variables with dot notation. Example: items.name Nested template variables are typically built from data layer list attributes Templates Provide templates to be referenced in message data. See: Templates Guide Templates are injected by name with double curly braces into supported fields Example: {{SomeTemplateName}} Action - Create or Update Prospect Parameters Prospect Lookup Identifier: (Required) Select an identifier to find a prospect by. For more information, see: Creating and Updating Prospects Please select from one of the following options to lookup prospects by: Prospect Email (email): Email address Prospect ID (id): This is the prospect's unique ID Prospect FID (fid): This is the prospects CRM ID Campaign: (Required) Select the campaign you wish to use. If you don't see the campaign you're looking for, you may enter the campaign ID as a custom value. To find the Campaign ID, open up the target campaign in Pardot and look for the numeric value at the end of the URL. For example, in this URL: https://pi.pardot.com/campaign/read/id/123 , the ID is "123". Create If Not Exists: (Optional) Check if you want to allow prospect creation. Create Prospect Data Required: Email Address When a prospect is being created, field configurations from this section are used Update Prospect Data Required: When a propsect is being updated, field configurations from this section are used Action - Add Prospect to List Parameters Target List: (Required) List to add the prospect to. See: "create" option under Supported Parameters If you need to add a list that you don't see in the dropdown, you can find the list ID at the URL: https://pi.pardot.com/list/read/id/XXXX Prospect Identifier: (Required) Select an identifier to find a prospect by. prospect_email: An email address associated with a prospect id: A Pardot ID that the prospect is known by Action - Opt out Prospect from List Parameters Target List: (Required) List to add the prospect to. See: "create" option under Supported Parameters If you need to add a list that you don't see in the dropdown, you can find the list ID at the URL: https://pi.pardot.com/list/read/id/XXXX Prospect Identifier: (Required) Select an identifier to find a prospect by. prospect_email: An email address associated with a prospect id: A Pardot ID that the prospect is known by Action - Remove Prospect from List Parameters Target List (REQUIRED) List to add the prospect to. See: "delete" option under Supported Parameters If you need to add a list that you don't see in the dropdown, you can find the list ID at the URL: https://pi.pardot.com/list/read/id/XXXX Prospect Lookup Identifier: (Required) Select an identifier to find a prospect by. prospect_email: An email address associated with a prospect id: A Pardot ID that the prospect is known by Vendor Documentation How are prospects associated with campaigns? Sending one-to-one emails Supported Parameters ... View more

Cortex by Retention Science uses your data to identify and track subtle changes in customer behavior, predicting the best actions to drive maximum engagement. This article describes how to configure the Tag in your profile. Table of Contents Placeholder Tag Configuration First, go to Tealium's Tag Marketplace and add the Cortex Search Abandon Tag to your profile (how to add a Tag?). After adding the Tag, configure the below settings: Site ID: Enter the unique site identifier you received from Cortex. Load Rules Load Rules determine when and where to load an instance of this Tag on your site. Recommended Load Rule: Set up custom rule(s) to load this Tag on specific pages where you want to track search activity. 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 Cortex Search Abandon Tag are built into its Data Mapping tab. Available categories are: Standard Destination Name Description Site ID site identifier provided by Cortex User Email visitor email Search Term search keyword used by visitor E-Commerce Since the Cortex Search Abandon 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 Destination Name Description User ID unique visitor identifier Vendor Documentation Cortex Help Documentation ... View more

This article describes how to set up the AWS SQS connector in your Customer Data Hub account. In this article:  Table of Contents Placeholder Amazon SQS provides fully-managed message queues for micro-services, distributed systems, and server-less applications. Requirements AWS Account Required: sqs:SendMessage permission Optional: sqs:ListQueues permission Queue to send data to Connector Actions Action Name AudienceStream EventStream Send Event Data to Queue ✗ ✓ Send Visitor Data to Queue ✓ ✗ Send Customized Data to Queue (Advanced) ✓ ✓ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: Access Key Required Provide your IAM User's access keyAssociated IAM policy (for either IAM User or Assumed Role) Must grant 'sqs:SendMessage' permission. For additional information, see Access Control for Amazon SQS. Secret Key Required Provide your IAM User's secret key Region Required Select region Assume Role: ARN Optional Provide Amazon Resource Name (ARN) of role to assume. For example: arn:aws:iam::222222222222:role/myrole For additional information, see Switching to an IAM Role. Assume Role: Session Name Optional. Provide identifier for assumed role session Assume Role: External ID Optional Provide external identifier For additional information, see How to Use an External ID. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. The following sections describe how to set up parameters and options for each action. Action - Send Event Data to Queue Parameters Parameter Description Queue Required Select queue to send data to If your IAM policy does not grant 'sqs:ListQueues' permission, you will need to manually enter a Custom Value Custom values should be a URL For example:  https://sqs.us-west-2.amazonaws.com/0123456789/queue_name MessageGroupId   DelaySeconds   Print Attribute Names If attribute names are updated, the names in the payload will reflect the update See Using Amazon SQS Message Attributes Action - Send Visitor Data to Queue Parameters Parameter Description Queue Required Select queue to send data to If your IAM policy does not grant 'sqs:ListQueues' permission, you will need to manually enter a Custom Value Custom values should be a URL For example: https://sqs.us-west-2.amazonaws.com/0123456789/queue_name MessageGroupId   DelaySeconds   Include Current Visit Data   Print Attribute Names If attribute names are updated, the names in the payload will reflect the update Action - Send Customized Data to Queue (Advanced) Parameters Parameter Description Queue Required Select queue to send data to If your IAM policy does not grant 'sqs:ListQueues' permission, you will need to manually enter a Custom Value Custom values should be a URL For example:  https://sqs.us-west-2.amazonaws.com/0123456789/queue_name MessageGroupId   DelaySeconds   Custom Message Definition   Message Template Variables Optional: provide template variables as data input for templates For more information, see the Template Variables Guide Name nested template variables with the dot notation (Example: items.name) Nested template variables are typically built from data layer list attributes Message Templates Optional: provide templates to be referenced in either URL, URL Parameter, Header or Body Data (see: Templates Guide) Templates are injected by name with double curly braces into supported fields Example: {{SomeTemplateName}}) See Using Amazon SQS Message Attributes Vendor Documentation Access Control for Amazon SQS Switching to an IAM Role How to Use an External ID Using Amazon SQS Message Attributes How Amazon SQS Queues Work ... View more

The Amazon Kinesis Streams Connector enables you to build custom real-time applications that process or analyze streaming data for specialized needs. This article walks you through the process of setting up the Connector in the Customer Data Hub. Table of Contents Placeholder Requirements Amazon Web Services Account Identity and Access Management (IAM) User Credentials Kinesis Streams Supported Actions Action Name Trigger on Audience Trigger on Streams Send Event Data to Kinesis Stream ✗ ✓ Send Visitor Data to Kinesis Stream ✓ ✗ Send Customized Data to Kinesis Stream (Advanced) ✓ ✓ Configure Settings Go to the Connector Marketplace and add a new Amazon Kinesis Streams Connector. Read the Connector Overview article for general instructions on how to add a Connector. To configure your vendor, follow these steps: In the Configure tab, provide a title for the Connector instance. Provide your IAM user access and secret key. The policy statement attached to your IAM user instance must include the kinesis:PutRecord permission. For more details on policies for Kinesis Streams, see Kinesis Streams Resources Access). Select the region where you want to make the API calls. Assume Role Parameters: Required only if your IAM User is not setup with all necessary permissions (see: Switching to an IAM Role). ARN (required): Amazon Resource Name assigned to the role to assume. Session Name (required): Unique identifier of the assumed role session. External ID (optional): Unique identifier used by third parties when assuming roles in their customers' accounts (see: How to Use an External ID). Click Test Connection to verify API connectivity with the provided credentials. Action Settings - Parameters and Options Click Next or go to the Actions tab. It's where you'll set up Actions to trigger. This section describes how to set up Parameters and Options for each Action. Action - Send Event Data to Kinesis Stream Parameters Stream Name (REQUIRED): Select the stream to send data to. These options are available only if your configured policy is granted the kinesis:ListStreams permission. If the permission is not granted, you must manually enter the stream name as a Custom Value. Message Options (REQUIRED): Map Attribute(s) to a message option in the To drop-down list. See available options below. Print Attribute Names: Checking this box will display names for each event data Attribute in the message payload. And if the Attribute names change in Customer Data Hub, they are automatically reflected in the payload. Options - Message Options Option Description Partition Key REQUIRED: Determines which shard in the stream the message is sent to Explicit Hash Key A specific hash value that helps determine the shard in the stream the message is sent to. Overrides hashing the partition key. Sequence Number for Ordering Guarantees strictly increasing sequence numbers for messages from the same client and to the same partition key For more information, see: Put Record Request Parameters Action - Send Visitor Data to Kinesis Stream Parameters Stream Name (REQUIRED): Select the stream to send data to. These options are available only if your configured policy is granted the kinesis:ListStreams permission. If the permission is not granted, you must manually enter the stream name as a Custom Value. Message Options (REQUIRED): Map Attribute(s) to a message option in the To drop-down list. Include Current Visit Data: Checking this box will include current visit data in the message payload. Print Attribute Names: Checking this box will display names for each visitor data Attribute in the message payload. And if the Attribute names change in Customer Data Hub, they are automatically reflected in the payload. Action - Send Customized Data to Kinesis Streams (Advanced) Parameters Stream Name (REQUIRED): Select the stream to send data to. These options are available only if your configured policy is granted the kinesis:ListStreams permission. If the permission is not granted, you must manually enter the stream name as a Custom Value. Message Options (REQUIRED): Map Attribute(s) to a message option in the To drop-down list. Message Data (REQUIRED): Construct a custom message body. Map Attribute(s) to names for a simple, one-level JSON format, or reference a template name (surrounded in double curly braces) and select the Custom Message Definition option. Template Variables: Map Attribute(s) to template variable names. Template variables are available for substitution and rendering of all templates. Refer to our Template Variables Guide for details. Templates: Provide one or more templates to render. Typically, a single template is used to construct a message data. Refer to our Templates Guide for common syntax and extensions. Vendor Documentation What Is Amazon Kinesis Streams Kinesis Streams Resources Access Switching to an IAM Role How to Use an External ID Put Record Request Parameters ... View more

This article describes how to set up the Google Cloud Pub/Sub connectors. Tealium offers two Pub/Sub connectors in the Connector Marketplace: the Google Could Pub/Sub Connector (3-legged OAuth) and Google Cloud Pub/Sub (Service Account) Connector (2-legged OAuth).  In this article: Prerequisites Google Cloud Pub/Sub Connector This connector uses a three-legged OAuth flow using a client ID and secret with user input for authentication. Before configuring this connector, complete the following steps: Create an OAuth client ID credential in your Google Cloud project with an application type of web application. Update the Google Cloud web application settings to whitelist Tealium servers and provide the required callback upon successful connection. In the Google Cloud console, navigate to Credentials and edit the OAuth client ID settings with the following values. For each selection, add one of the values depending on the subdomain used in the URL of your Tealium instance. Authorized JavaScript origins: https://my.tealiumiq.com https://sso.tealiumiq.com https://[privatecloud subdomain].tealiumiq.com Authorized redirect URIs: https://my.tealiumiq.com/oauth/google/callback.html https://sso.tealiumiq.com/oauth/google/callback.html https://[private cloud subdomain].tealiumiq.com/oauth/google/callback.html Make note of the following configuration settings to use in the connector configuration Project ID Client ID Client Secret Google Cloud Pub/Sub (Service Account) Connector This connector uses two-legged OAuth flow, based on a Google Cloud service account for access. Before configuring the connector, create a service account in a Google Cloud project with a role of Pub/Sub Publisher. For more information about creating a service account, see Access Control with IAM in the Google Cloud documenation. After you create your service account, make note of the following configuration settings to use in the connector configuration: Project ID Service Account Email Service Account Key Configure Settings Navigate to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see the About Connectors article. After adding the connector, configure the following settings based on which connector you added: Google Cloud Pub/Sub Connector Google Cloud Project ID Required. Your Google Cloud Project ID. Client ID Required. The OAuth Client ID in your Google Cloud project with an application type of web application.  Client Secret Required. Enter the client secret assigned to you in your Google Cloud project. Google Cloud Pub/Sub (Service Account) Connector Google Cloud Project ID Required. Your Google Cloud Project ID. Client Email Required. The service account email address used in your Google Cloud project. Private Key Required. The private key generated for your Google Cloud project service account. Connector Actions Action Name AudienceStream EventStream Send Event Data to Topic ✗ ✓ Send Visitor Data to Topic ✓ ✗ Send Customized Data to Topic (Advanced) ✓ ✓ Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. If the Pub/Sub topic you are publishing to has a schema attached, use the Send Customized Data to Topic action to specify a strict JSON definition which matches your schema. Action - Send Event Data to Topic Parameters Parameter Description Project Topic Required Select the topic in your Pub/Sub project to publish the message to. Message Attributes Optional Map your attribute values to custom Pub/Sub message attributes. Enter the message attribute key in the To drop-down list. Print Attribute Names If attribute names are updated, the names in the payload automatically reflect the updated name in the published message. Action - Send Visitor Data to Topic Parameters Parameter Description Project Topic Required Select the topic in your Pub/Sub project to publish the message to. Message Attributes Optional Map your attribute values to custom Pub/Sub message attributes. Enter the message attribute key in the To drop-down list. Include Current Visit Data Checking this box will include both visitor data and current visit data in the published message. Print Attribute Names If attribute names are updated, the names in the payload automatically reflect the updated name in the published message. Action - Send Customized Data to Topic (Advanced) Parameters Parameter Description Project Topic Required Select the topic in your Pub/Sub project to publish the message to. Message Attributes Optional Map your attribute values to custom Pub/Sub message attributes. Enter the message attribute key in the To drop-down list. Custom Message Definition Required Provide values to construct message data. For template support, reference the template name to generate message data from the template. Map values to names for simple one-level JSON format, otherwise reference the template name and select only the Custom Message Definition option. Template Variables Optional Provide template variables as data input for templates. For additional information, see the Template Variables Guide. Name nested template variables with the dot notation. Example: items.name Nested template variables are typically built from data layer list attributes. Templates Optional Provide templates to be referenced in either message attributes or data. For more information, see the Templates Guide. Templates are injected by name with double curly braces into supported fields. Example: {{SomeTemplateName}} Vendor Documentation Quickstarts Setting Up Authentication for Server to Server Production Applications Topics and Messages ... View more

The Tealium Events extension defines standard conditions for the most commonly tracked events. It adds the tealium_event variable to your data layer where it can help simplify tag mappings, load rules, or other conditions. It can also be passed to Tealium EvenStream via the Tealium Collect tag. See the full list of available extensions. In this article: Table of Contents Placeholder Prerequisites utag v4.38 or higher. (See: How to upgrade utag.js) How It Works This extension introduces standardized event names into your solution, along with a new variable in your data layer called tealium_event . It covers the standard e-commerce customer journey and includes familiar events such as "Add to Cart", "Product Detail Page View", and "Purchase Complete". Since these events are typically represented in the data layer using page_type and event_name , this extension acts as a translation between your current page/event tracking conditions and the new standardized Tealium event names. Each event may be assigned to a custom condition that matches your data layer implementation. When an event condition evaluates to true, tealium_event is set to the pre-defined event value. For example, when the condition for "Add to Cart" evaluates to "true", tealium_event is set to “cart_add”. See the Standard Events section below. Using the Extension Before you begin, familiarize yourself with how extensions work. Once the extension is added, you may customize event conditions according to your implementation needs. The list of events are not changeable, but the event conditions are changeable. To customize an event condition: Click an event then click Edit. Adjust the condition logic as needed. Click Apply. Removing Conditions To prevent an event from being set, remove the condition and click Apply. This changes the event from being "Set" to "Not Set" and is no longer be evaluated in your configuration. In this example the condition for the "Email Signup" event has been removed, resulting in the event to be "Not Set". Standard Events Below is a table of standard events and default conditions in the extension. Events are listed in alphabetical order and are evaluated sequentially. The default conditions match our standard data layer recommendations, but they are customizable to match your exact implementation. Event tealium_event Default Condition Add to Cart cart_add event_name="cart_add" Category Page View category_view page_type="category" Checkout checkout page_type="checkout" Email Signup email_signup event_name="email_signup" Empty cart cart_empty event_name="cart_empty" Page View page_view page_type="generic" Product Detail Page View product_view page_type="product" Purchase Complete purchase page_type="purchase" Remove from Cart cart_remove event_name="cart_remove" Search Page View search page_type="search" Shopping Cart View cart_view page_type="cart" Social Share social_share event_name="social_share" User Log in user_login event_name="user_login" User Log out user_logout event_name="user_logout" User Register user_register event_name="user_register"   The tealium_event value is always set for the condition that last evaluated to "true". If more than one event condition evaluates to "true", the event lower in the list is set. Custom Events The Tealium Events extension provides a list of predefined events. A custom event uses a value defined by you and assigned to the variable tealium_event . Define these custom events directly in your data layer or by using the Set Data Values extension. Position custom events defined in an extension after the Tealium Events extension. To define a custom event using an extension: Add a Set Data Values extension. Drag the new extension below the existing Tealium Events extension to ensure it runs after it. In the Set drop-down list select tealium_event . In the text field type the name of your custom event. Add a condition to identify your custom event. Example of custom event using the Set Data Values extension: Examples The goal of the extension is to standardize the event name value into the tealium_event variable used in your configuration. Here are some uses for this variable: Event Mappings in Tags Simplify tag configurations that support page and event mappings by using a single variable, tealium_event , to configure these events. Load Rules Load rules use tealium_event to simplify their conditions. Customer Data Hub If you have the Tealium Collect tag all the variables in your data layer are passed along to Tealium EventStream, including tealium_event . This variable is made available as an imported event attribute to be used in enrichments, rules, and feeds. ... View more

Microsoft Dynamics 365 is a multifaceted CRM solutions platform to streamline processes and increase profitability in sales, marketing and service divisions. This article describes how to set up the Connector service in your Customer Data Hub profile. Table of Contents Placeholder Requirements Microsoft Dynamics 365 account Organization URI (root web address you received from Microsoft) Connector Actions Action Name AudienceStream EventStream Add or Update Contact ✓ ✗ Add Custom Entity to Contact ✓ ✗ Add or Update Lead ✓ ✗ Qualify Lead to Contact ✓ ✗ Update Custom Entity ✓ ✗ Create or Update Custom Entity ✓ ✗ Add Contact to Marketing List ✓ ✗ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: Organization URI: Required. Provide your Microsoft Dynamics root web address (example: https://your-domain.crm.dynamics.com). URL must be secure and if it does not specify https, then prefix "https://" will automatically be added. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Contacts, Leads, and Custom Entities from your Microsoft Dynamics account are dynamically populated as options in the To list. If you don't find the option you are looking for, you must add them in your account first. Action - Add or Update Contact Parameters Parameter Description Contact Data Required Map Attributes to the data options you want to add or update for the contact. Contact Lookup Required Map Attributes to the lookup options you want to use for searching the target contact. If the contact is found, its data will be updated. Otherwise a new contact will be created For a full list of Contact fields, see Contact EntityType. Action - Add Custom Entity to Contact Parameters Parameter Description Custom Entity Required: select custom entity Custom Entity to Contact Relationship Required: select lookup field that associates custom entity with contact (see: Entity Relationships) Action - Add or Update Lead Parameters Parameter Description Lead Data Required Map Attributes to the data options you want to add or update for the lead. Lead Lookup Required Map Attributes to the lookup options you want to use for searching the target lead. If the lead is found, its data will be updated. Otherwise a new lead will be created. For full list of fields see: Lead EntityType Action - Update Custom Entity Parameters Parameter Description Custom Entity Required Select custom entity Action - Create or Update Custom Entity Parameters Parameter Description Update Strategy Required Select applicable update strategy Create Only: create new entity without lookup Update Only: lookup existing entity and update it Create or Update: lookup existing entity and if found update it, otherwise create new entity Custom Entity Required Select custom entity Action - Add Contact to Marketing List Parameters Parameter Description Marketing List Required Select marketing list to add contact to Only static and non-locked lists targeting contacts are shown Vendor Documentation For additional information, see the following vendor documentation: Lead EntityType Contact EntityType Create a New Entity Create and Edit Entity Relationships ... View more

With the Simility Tag, you can collect user data for detecting fraudulent activities. This article shows you how to add and configure the Tag in your Tealium iQ profile. Table of Contents Placeholder Prerequisites Simility account Tag Configuration First, go to Tealium's Tag Marketplace and add the Simility Tag to your profile (how to add a Tag?). After adding the Tag, configure the below settings: Customer ID: The unique identifier that you (or your company) received from Simility during signup. Customer ID is required; you may specify it in this field or set it dynamically via Data Mappings. Zone: The location of the datacenter hosting your data. Available options are “US” (default) and "EU". Simility Lite: This is turned ON by default. If you turn it OFF, you must send additional user information such as geo-location, mouse movements, etc. Simility Lite Level: The numeric (decimal) value you received from the Simility support team. Simility Lite and Simility Lite Level settings are advanced configurations. For more details on these, please contact the Simility support team. Load Rules Load Rules determine when and where to load an instance of this Tag on your site. 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 Simility Tag are built into its Data Mapping tab. Available categories are: Standard Destination Name Description Simility Customer ID (Required) Customer/Account ID provided to you by Simility during signup Simility Lite Boolean value (true/false) to determine whether or not Simility Lite is enabled Simility Lite Level The decimal value you received from the Simility support team Zone The location of the datacenter hosting your data. Make sure the Variable you are mapping contains either “us” or “eu”. Session ID (Required) Unique id of the user session Event Types (Required) A comma-separated string of events associated with the user activity being tracked Mapping to a Standard destination overrides its corresponding Tag Setting. Transaction Info Allows you to send transaction data, e.g. user, orders, transactions, applications, profile, etc. Data is sent through the transaction_info object in the payload. Destination Name Description Entity Entity type of the payload; required if using the transaction_info object Transaction ID Unique id of the transaction; required if using the transaction_info object First Name First name of the user Last Name Last name of the user User ID Username of the user Email Email id of the user Is First Order Boolean value (true/false) to determine whether it's the user's first order Number Of Retries Number of attempts to place the order Custom Field Custom data related to the user's transaction. Replace "custom" with your custom parameter name. E.g. field.order_categories Custom Nested Field Send transaction data in a nested form. E.g. field.order_details.is_first_order Example Payload Notice how the transaction info mappings are wrapped in the transaction_info object whereas all non-transaction mappings are outside the object. var similityContext = { "customer_id": "acme", "session_id": "1234", "user_id" : "user1234", "simility_lite": true, "transaction_info": [{ "entity": "orders", "id": "xyz101", "fields": { "first_name": "John", "last_name": "Doe", "user_id": "user1234", "email": "johndoe@example.com", "order_categories": ["123", "456", "789"], "order_details": { "is_first_order": true, "num_retries": 1 }, } }] }; E-Commerce Since the Simility 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 Destination Name Description E-Commerce Extension Variable Order ID Unique Order ID _corder Order Total Total value of order _ctotal Customer ID (Required) Unique customer ID. _ccustid List of Product IDs Array of Product IDs _cprod List of Names Array of Product Names _cprodname List of Categories Array of Product Categories _ccat List of Quantities Array of Product Quantities _cquan List of Prices Array of Product Prices _cprice Vendor Documentation Simility Javascript ... View more

Emarsys is a comprehensive cloud-based B2C (Business to Consumer) marketing platform that fully maximizes customer value through data science and artificial intelligence marketing. This article describes how to set up the Emarsys connector in your Customer Data Hub account. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add Contact to Contact List (deprecated v1) ✓ ✗ Add Contact to Contact List ✓ ✗ Create or Update Email Contact (deprecated v1) ✓ ✗ Create or Update Email Contact ✓ ✗ Remove Contact From Contact List (deprecated v1) ✓ ✗ Remove Contact From Contact List ✓ ✗ Trigger Transactional Email (deprecated v1) ✓ ✗ Trigger Transactional Email ✓ ✗ Unsubscribe Contact From Email Campaign ✓ ✗ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: Username: Username with permissions to access Emarsys APIDon't have a username and password? Get started Password: Password for provided username Environment: Environment to make API calls against Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Add Contact to Contact List (deprecated v1) Parameters Parameter Description Target Contact List Required The contact list to add the contact to Use Custom Value if you know and want to configure the ID of the target contact list manually. First Name   Last Name   E-Mail   Date of Birth   Gender   Marital Status   Children   Education   Title   Address   City   State   ZIP Code   Country   Phone   Fax   Job Position   Company   Department   Industry   Phone (office)   Fax (office)   Number of Employees   Annual Revenue (in OOO EUR)   URL   Preferred e-mail format   Opt-in   Registration Language   Mobile   First Name of Partner   Birth Date of Partner   Anniversary   Company Address   Zip Code (office)   City (office)   State (office)   Country (office)   Salutation   Action - Add Contact to Contact List Parameters Parameter Description Target Contact List Required The contact list to add the contact to Use Custom Value if you know and want to configure the ID of the target contact list manually. Action - Create or Update Email Contact (deprecated v1) Parameters Parameter Description Create If Not Exists When enabled, if the contact does not exist, it is created automatically Source ID An optional ID assigned to a customer's external application, and is used to identify contacts created or modified by the external applications Contact Identifying Field Required This is the field used to identify a contact First Name   Last Name   E-Mail   Date of Birth   Gender   Marital Status   Children   Education   Title   Address   City   State   ZIP Code   Country   Phone   Fax   Job Position   Company   Department   Industry   Phone (office)   Fax (office)   Number of Employees   Annual Revenue (in OOO EUR)   URL   Preferred e-mail format   Opt-in   Registration Language   Mobile   First Name of Partner   Birth Date of Partner   Anniversary   Company Address   Zip Code (office)   City (office)   State (office)   Country (office)   Salutation   Action - Create or Update Email Contact Parameters Parameter Description Create If Not Exists When enabled, if the contact does not exist, it is created automatically Source ID An optional ID assigned to a customer's external application, and is used to identify contacts created or modified by the external applications Contact Identifying Field Required This is the field used to identify a contact Use Custom Value if you know and want to configure the ID of the target contact field manually. Action - Remove Contact From Contact List (deprecated v1) Parameters Parameter Description Target Contact List Required The contact list to remove the contact from Use Custom Value if you know and want to configure the ID of the target contact list manually. First Name   Last Name   E-Mail   Date of Birth   Gender   Marital Status   Children   Education   Title   Address   City   State   ZIP Code   Country   Phone   Fax   Job Position   Company   Department   Industry   Phone (office)   Fax (office)   Number of Employees   Annual Revenue (in OOO EUR)   URL   Preferred e-mail format   Opt-in   Registration Language   Mobile   First Name of Partner   Birth Date of Partner   Anniversary   Company Address   Zip Code (office)   City (office)   State (office)   Country (office)   Salutation   Action - Remove Contact From Contact List Parameters Parameter Description Target Contact List Required The contact list to remove the contact from Use Custom Value if you know and want to configure the ID of the target contact list manually. Action - Trigger Transactional Email (deprecated v1) Parameters Parameter Description External Event Required Select event set to trigger email First Name   Last Name   E-Mail   Date of Birth   Gender   Marital Status   Children   Education   Title   Address   City   State   ZIP Code   Country   Phone   Fax   Job Position   Company   Department   Industry   Phone (office)   Fax (office)   Number of Employees   Annual Revenue (in OOO EUR)   URL   Preferred e-mail format   Opt-in   Registration Language   Mobile   First Name of Partner   Birth Date of Partner   Anniversary   Company Address   Zip Code (office)   City (office)   State (office)   Country (office)   Salutation   Content Personalization Data to Set Optional Place holder in email and the value to replace it with Action - Trigger Transactional Email Parameters Parameter Description External Event Required Select event set to trigger email Content Personalization Data to Set Optional Place holder in email and the value to replace it with Action - Unsubscribe Contact From Email Campaign Parameters Parameter Description Launch List ID (Required) Email Campaign ID (Required) Contact ID (Required) ... View more

Microsoft Azure Service Bus is a cloud messaging service between applications and services. This article describes how to configure the service in the Customer Data Hub. Table of Contents Placeholder Requirements Microsoft Azure Account Service Bus Shared Access Policy Credentials Queue or Topic to send data to Supported Actions Action Name AudienceStream EventStream Send Event Data to Queue or Topic ✗ ✓ Send Visitor Data to Queue or Topic ✓ ✗ Send Customized Data to Queue or Topic ✓ ✓ Configure Settings Go to the Connector Marketplace and add a new Microsoft Azure Service Bus Connector. Read the Connector Overview article for general instructions on how to add a Connector. To configure your vendor, follow these steps: In the Configure tab, provide a title for the Connector instance. Enter Service Bus Namespace, Shared Access Policy Name and Key. For more information, see Namespace & Shared Access Policies. Click Test Connection to verify API connectivity with the provided credentials. Shared Access Policies can claim three type of permissions: Send , Listen and Manage . Provided policy must claim at least Send permission. Action Settings - Parameters and Options Click Next or go to the Actions tab. It's where you'll set up Actions to trigger. This section describes how to set up Parameters and Options for each Action. Action - Send Event Data to Queue or Topic Parameters Queue or Topic (REQUIRED): Select a queue or topic option from this list. These options are available only if your configured policy is granted the Manage permission. If the permission is not granted, you must manually enter a queue/topic as a Custom Value. User Properties: Map Attribute(s) to a message user property in the To dropdown (entered as a Custom Value). Broker Properties: Map Attribute(s) to the message broker property of choice in the To dropdown. See available options below. Print Attribute Names: Checking this box will display names for each event data Attribute in the message payload. All Actions support Message User and Broker properties. They provide useful and convenient information about a message using key-value pairs. But they are set as HTTP headers and do not reside within the message body. For more information see Message User & Broker Properties Options - Broker Properties Option Description Content Type Sets HTTP header Content-Type for message consumers Correlation ID Unique identifier of the correlation Session ID Can be used to partition and route messages to particular consumers Message ID Overrides default auto-generated Message ID Label Application label Reply To Can be used to specify where to send a response for message consumers Time to Live in Seconds Expire message after X number of seconds (overrides queue/topic level) To Send to address Scheduled Enqueued Time Scheduled date and time at which the message is enqueued Reply to Session ID Similar to Reply To but targets a session for a response Partition Key Unique identifier of the partitioned queue or topic Action - Send Visitor Data to Queue or Topic Parameters Queue or Topic (REQUIRED): Select a queue or topic option from this list. These options are available only if your configured policy is granted the Manage permission. If the permission is not granted, you must manually enter a queue/topic as a Custom Value. User Properties: Map Attribute(s) to a message user property in the To dropdown (entered as a Custom Value). Broker Properties: Map Attribute(s) to the message broker property of choice in the To dropdown. See available Broker Properties options. Include Current Visit Data: Checking this box will include current visit data in the message payload. Print Attribute Names: Checking this box will display names for each visitor data Attribute in the message payload. Action - Send Customized Data to Queue or Topic (Advanced) Parameters Queue or Topic (REQUIRED): Select a queue or topic option from this list. These options are available only if your configured policy is granted the Manage permission. If the permission is not granted, you must manually enter a queue/topic as a Custom Value. User Properties: Map Attribute(s) to a message user property in the To dropdown (entered as a Custom Value). Broker Properties: Map Attribute(s) to the message broker property of choice in the To dropdown. See available Broker Properties options. Message Data (REQUIRED): Construct a custom message body. Map Attribute(s) to names for simple one level JSON format, or reference a template name (surrounded in double curly braces) and select the Custom Message Definition option. Template Variables: Map Attribute(s) to template variable names. Template variables are available for substitution and rendering of all templates. Refer to our Template Variables Guide for details. Templates: Provide one or more template to render. Typically, a single template is used to construct a message data. Refer to our Templates Guide for common syntax and extensions. If necessary, templates can also be referenced and injected in user and broker properties. Vendor Documentation Namespace & Shared Access Policies Message User & Broker Properties ... View more