Tealium Learning Center

This article describes how to set up the Google Ad Manager 360 Audience Pixel tag in your Tealium iQ Tag Management account. Build first-party audience segments in Google Ad Manager 360 without serving any ads by adding the Audience Pixel tag to your site or mobile app. You can use the pixel tag at no extra cost, without being charged for serving an Ad Manager impression. This tag also allows you to use a publisher provided identifier (PPID) for audience segmentation in place of a Google Marketing Platform cookie or mobile advertising ID. In this article: Tag Tips Use mappings to override or dynamically set the tag configurations. Publisher Provided ID (PPID) should only be added to the URL if a mapped value is populated for it. The PPID value requirements are: Alphanumeric ( [0-9 a-z A-Z] ) or UUID HEX representation ( 8-4-4-4-12 ). (Hyphens are permitted) The following regex can be used to enforce the value: ^([0-9a-zA-Z]{32,150})$|^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$ Tag Configuration Navigate to the Tag Marketplace to add a new tag. Read the Tag Overview article for general instructions on how to add a tag. When adding the tag, configure the following settings: Network Code: The publisher’s Google Ad Manager network identifier. Found under Admin > Global Settings or in the Ad Manager URL. Segment ID: Segment Identifier ( dc_seg ). Load Rules Load the tag on all pages or set conditions for when your tag will load. For more information about load rules, see the Load Rules documentation. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Standard Variable Description Network Code ( network_code ) [String] Segment ID ( segment_id ) [String] Publisher Provided ID ( publisher_provided_id ) [String] ... View more

This article describes how to set up the Crimtan tag in your Tealium iQ Tag Management account. Crimtan is a fully programmatic, data-driven, digital marketing company based in 12 countries around the world. Crimtan turns consumer data into valuable insights and creative display advertising campaigns, helping businesses increase brand awareness, find new customers, and better maintain customer relationships. In this article: Tag Tips Use mapping to dynamically override the standard config values. Tag Configuration Navigate to the Tag Marketplace to add a new tag. Read the Tag Overview article for general instructions on how to add a tag. When adding the tag, configure the following settings: Container ID Silent Mode Load Rules Load the tag on all pages or set conditions for when your tag will load. For more information about load rules, see the Load Rules documentation. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Standard Variable Description Container ID ( containerId ) Silent Mode ( silentMode ) Consent Status ( consentStatus ) ... View more

This article describes how to set up the Yandex.Metrica tag in your Tealium iQ Tag Management account. Yandex.Metrica is a free tool that helps you increase the conversion rate of your site. Metrica lets you monitor the key effectiveness indicators of your website, analyze user behavior, and evaluate the efficiency of your ad campaigns. In this article: Tag Tips Use mapping to override the standard config values dynamically. Tag Configuration Navigate to the Tag Marketplace to add a new tag. Read the Tag Overview article for general instructions on how to add a tag. When adding the tag, configure the following settings: Tag ID: Yandex Tag ID Click Map: Detailed recordings of user activity on the site: mouse movement, scrolling, and clicks Track Links: Setting tracking of outbound links and download links Accurate Track Bounce: Enable the accurate bounce rate, with a non-bounce event registered after 15000 ms (15 s) Webvisor: Webvisor reproduces user actions in video format and lets you know what they do on the site: how they move around the page, how they move the mouse cursor and click through links. Load Rules Load the tag on all pages or set conditions for when your tag will load. For more information about load rules, see the Load Rules documentation. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Standard Variable Description Base Url (base_url) [String] Hit Event Url (url) [String] Tag ID (tagId) [String] Click Map (clickmap) [Boolean] Track Links (trackLinks) [Boolean] Accurate Track Bounce (accurateTrackBounce) [Boolean] Webvisor (webvisor) [Boolean] E-commerce Data Layer (ecommerce) [String/Boolean] E-commerce Variable Description Order Id (order_id) (override _corder) [String/Number] Order Coupon Code (order_coupon_code) (override _cpromo) [String] Order Total (order_total) (override _ctotal) [Number/String] Order Currency (order_currency) (override _ccurrency) [String] Goal ID (goal_id) [Number/String] List of Product IDs (id) (override _csku) [Array] List of Product Names (name) (override _cprodname) [Array] List of Product Brands (brand) (override _cbrand) [Array] List of Product Categories (category) (override _ccat) [Array] List of Product Coupons (coupon) [Array] List of Product Prices (price) (override _cprice) [Array] List of Product Quantities (quantity) (override _cquan) [Array] List of Product Positions (position) [Array] List of Product Variants (variant) [Array] Events To map events, refer to Create an Event Mapping. Variable Description Hit (Send Page View Event) (hit) hit View Product (detail) detail Add Product (add) add Remove Product (remove) remove Purchase (purchase) purchase Event-specific Parameters To map events, refer to Create an Event Mapping. Variable Description Hit (hit) hit View Product (detail) detail Add Product (add) add Remove Product (remove) remove Purchase (purchase) purchase ... View more

This article describes how to set up the Neustar PlatformOne Conversion Tag in your Tealium iQ Tag Management account. Neustar® PlatformOne is an integrated marketing platform that enables advertisers to deliver precision marketing across all marketing activities. Powered by Neustar's Authoritative Identity Engine, PlatformOne provides a single, unbiased and accurate view of customers and prospects to improve conversion rates, optimize spend, and ultimately increase sales. In this article: Tag Tips Use mapping to override the standard config values dynamically. Uses the following E-Commerce variables _corder _ctotal _ccustid _cquan product_quantity This can be mapped as an array (overriding the E-Commerce value, as normal), and will to summed to give a total Or mapped as a number that will be assigned directly Tag Configuration Navigate to the Tag Marketplace to add a new tag. Read the Tag Overview article for general instructions on how to add a tag. When adding the tag, configure the following settings: Tag ID: An integer value (for example, 123456 ) Type ID: An integer value (for example, 123456 ) Load Rules Load the tag on all pages or set conditions for when your tag will load. For more information about load rules, see the Load Rules documentation. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Standard Variable Description Tag ID (tag_id) Type ID (type) E-Commerce Variable Description Order ID (order_id) (Overrides _corder ) Order Total (order_total) (Overrides _ctotal ) Customer ID (customer_id) (Overrides _ccustid ) List of Quantities (product_quantity) (Overrides _cquan ) [Array/Number] Custom Attribute 1 (cust1) [Array/String] Custom Attribute 2 (cust2) [Array/String] ... View more

Adobe Test & Target gives marketers the necessary capabilities to continually make their online content and offers more relevant to their customers -- yielding greater conversion. Tag Specifications and Requirements Specifications Name: Test & Target Vendor: Adobe Type: Personalization Required Services: Adobe Marketing Cloud Account Configurations: Client Code Timeout Global mbox Name (synchronous version) Tag Configuration in Tealium iQ Step 1. Add the Tag Tealium iQ's Tag Marketplace offers a wide variety of tags. Click here to learn how to add a tag to your profile. Tealium supports both asynchronous and synchronous versions of the Test & Target Tag. Each version is a separate tag in the Tag Marketplace. However, we recommend that you use the asynchronous version. If you have concerns about flicker, check out our Flicker-Free Test & Target solution, which allows you load the Test & Target Tag asynchronously and avoid the appearance of flicker. You must add and configure the Test & Target Content Modification extension along with the asynchronous tag. The synchronous version does not use the extension. Step 2. Configure the Tag Asynchronous As a best practice we recommend using the asynchronous version of Test & Target. There are a few differences in the configurations, depending on which version you use. For the asynchronous version, set the following configurations: Title (Required): Enter a descriptive title to identify the tag instance. Client Code (Required): Enter the client ID assigned to you by Adobe. Timeout (Required): Enter the amount of time, in milliseconds, you want the tag to wait for a response from Adobe before assuming the Test & Target server is not responding. If there is no response from the server, the tag call is halted. We recommend setting this to 5000 milliseconds or greater. Visitor Tracking ID (Optional): This field allows you to track visitors across Test and Target and SiteCatalyst. You can find this configuration in the mbox.js file as var imsOrgId = 'XXXXXXXXXXXXXXXXXXXXXXXX@AdobeOrg' You've finished configuring the Test & Target Tag. Synchronous The synchronous version of Test & Target has a slight difference in configurations and requires a change to the Advanced Settings of the tag. If you plan to load this tag synchronously, then you must load the utag.js file synchronously as well. See the Code Center article to see how to acquire the synchronous utag.js code. Title (Required): Enter a descriptive title to identify the tag instance. Client Code (Required): Enter the client ID assigned to you by Adobe. Global mbox Name (Required): Enter the name of the globally hidden mbox. Adobe typically uses global here. The tag automatically calls mboxCreate to create the mbox. Visitor Tracking ID (Optional): This field allows you to track visitors across Test and Target and SiteCatalyst. You can find this configuration in the mbox.js file as var imsOrgId = 'XXXXXXXXXXXXXXXXXXXXXXXX@AdobeOrg' Advanced Settings (Required): Change the following Advanced Settings: Set Wait Flag to 'No'. Set Synchronous Load to 'Yes'. Any further configuration of the test content is handled through Test & Target's user interface. Step 3. Apply Load Rules Load Rules determine when and where to load an instance of this tag. The Load on All Pages rule is the default Load Rule. To load this tag on a specific page, create a new load rule with the relevant conditions. Best Practice: We recommend that you load this tag on all pages by leaving the default Load on All Pages selected. For the asynchronous version, you can control the conditions under which your tests load through the Test & Target Extension. Step 4. Set up Mappings Mapping is the simple process of sending data from a data source, in your Data Layer, to the matching destination variable of the vendor tag. For the asynchronous version of Test & Target, mappings are handled through the Test & Target Content Modification extension in the Static Params field. Mapping is not supported for the synchronous version of Test & Target. ... View more

This article describes how to set up the ClickSend connector. In this article: Connector Actions Action Name AudienceStream EventStream Create a New Contact ✓ ✓ Update a Specific Contact ✓ ✓ Delete a Specific Contact ✓ ✓ Send an SMS ✓ ✓ Send a Transactional Email ✓ ✓ 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: Username Username is your account username, password is your account password. These are the same credentials that you use to login to the dashboard. For more information, read: ClickSend's authentication documentation. Password Username is your account username, password is your account password. These are the same credentials that you use to login to the dashboard. For more information, read: ClickSend's authentication documentation. Click Done when you are finished configuring the connector. Action Settings — Parameters and Options Click Continue to configure the connector actions. Enter in a name for the action and then select the action type from the drop-down menu. The following section describes how to set up parameters and options for each action. Action — Create a New Contact Parameters Parameter Description List ID The contact list ID where your contact is associated. For more information on this endpoint, read: ClickSend's create a new contact documentation. Phone Number Contact phone number in E.164 format. Note that the fields phone_number , fax_number , address_line_1 , and email are all optional. However, at least one of them must be specified, otherwise the API call will fail. For more information, read: ClickSend's create a new contact documentation. First Name First name of the contact. Last Name Last name of the contact. Fax Number Contact fax number. Note that the fields phone_number , fax_number , address_line_1 , and email are all optional. However, at least one of them must be specified, otherwise the API call will fail. For more information, read: ClickSend's create a new contact documentation. Organization Name Your organization name. Email Contact email. Note that the fields phone_number , fax_number , address_line_1 , and email are all optional. However, at least one of them must be specified, otherwise the API call will fail. For more information, read: ClickSend's create a new contact documentation. Address Line 1 Contact address line 1. Note that the fields phone_number , fax_number , address_line_1 , and email are all optional. However, at least one of them must be specified, otherwise the API call will fail. For more information, read: ClickSend's create a new contact documentation. Address Line 2 Contact address line 2. Address City Contact city. Address State Contact state. Address Postal Code Contact postal code. Address Country Contact two-letter country code defined in ISO 3166. Custom Attributes Any custom attributes you wish to include. Action — Update a Specific Contact Parameters Parameter Description List ID Contact list ID you want to access. For more information on this endpoint, read: ClickSend's update a contact documentation. Contact ID Contact ID you want to access. Phone Number Contact phone number in E.164 format. First Name First name of the contact. Last Name Last name of the contact. Fax Number Contact fax number. Organization Name Your organization name. Email Contact email. Address Line 1 Contact address line 1. Address Line 2 Contact address line 2. Address City Contact city. Address State Contact state. Address Postal Code Contact postal code. Address Country Contact two-letter country code defined in ISO 3166 format. Custom Attributes Any custom attributes you wish to include. Action — Delete a Specific Contact Parameters Parameter Description List ID Your contact list ID you want to access. For more information on this endpoint, read: ClickSend's delete a contact documentation. Contact ID Your contact ID you want to access. Action — Send an SMS Parameters Parameter Description To Recipient number in E.164 format or local format. For more information, read: ClickSend's send an SMS documentation. Body Your message. Source Your method of sending. For example, wordpress , php , c# . From Your sender ID. For more information, read: SendGrid's sender ID or number documentation. Schedule Your scheduled time as a Unix timestamp. Leave blank for immediate delivery. Custom String Your reference. Will be passed back with all replies and delivery reports. Country Recipient country. From Email An email address where the reply should be emailed to. If omitted, the reply will be emailed back to the user who sent the outgoing SMS. Action — Send a Transactional Email Parameters Parameter Description Email The recipient's email address. Name (to) The recipient's name. Email Address ID The sender's email address ID. Name (from) The sender's name. Subject The subject of the email. Body The content of the email. ... View more

This article describes how to set up the PulsePoint HCP365 Pixel tag in your Tealium iQ Tag Management account. HCP365, the first self-serve product under the Signal platform, uncovers who, how, and when your HCP audience organically engages with branded digital touch points at the NPI-level. The HCP365 Pixel will send page-level information into your PulsePoint system. In this article: Tag Tips Use mappings to override Standard parameters. Tag Configuration Navigate to the Tag Marketplace to add a new tag. Read the Tag Overview article for general instructions on how to add a tag. When adding the tag, configure the following settings: PulsePoint Container Pixel: PulsePoint container pixel that is unique to each client Token: PulsePoint internal identifier for a brand (for example, Merck advertiser has multiple brands so multiple tokens) Load Rules Load the tag on all pages or set conditions for when your tag will load. For more information about load rules, see the Load Rules documentation. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Standard Variable Description PulsePoint container pixel ( p ) [String] Token ( token ) [String] Base Url ( base_url ) [String] CCPA Opt-Out ( us_privacy ) (Required) [String] URL of the page the tag was fired ( url ) (Required) [String] Referrer of the page ( rr ) (Required) [String] Additional parameters for passing additional information to the pixel ( param1 ) [String] Additional parameters for passing additional information to the pixel ( param2 ) [String] Additional parameters for passing additional information to the pixel ( param3 ) [String] Additional parameters for passing additional information to the pixel ( param4 ) [String] Additional parameters for passing additional information to the pixel ( param5 ) [String] Form details if tag is fired on form submission ( frmtext ) [String] Link text of the link being clicked or document name of the document being downloaded ( clktext ) [String] ... View more

This article describes how to set up the UserWay tag in your Tealium iQ Tag Management account. UserWay creates advanced website accessibility solutions that help ensure ADA compliance without refactoring your website's existing code. With UserWay's RaaS™ and Tealium users can effortlessly increase compliance with WCAG 2.1, ADA, ATAG 2.0, EN 301-549, and Section 508 regulations as required by US & international governmental & regulatory bodies. In this article: Tag Tips Use mappings to override or dynamically set the tag configurations. Tag Configuration Navigate to the Tag Marketplace to add a new tag. Read the Tag Overview article for general instructions on how to add a tag. When adding the tag, configure the following setting: Data-account: Single-text field Load Rules Load the tag on all pages or set conditions for when your tag will load. For more information about load rules, see the Load Rules documentation. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Common Variable Description Get UserWay API version. (getVersion) Show UserWay accessibility menu icon. (iconVisibilityOn) Hide UserWay accessibility menu icon. (iconVisibilityOff) Toggle UserWay accessibility icon's visibility. (iconVisibilityToggle) Widget methods Variable Description Open or close widget menu. (widgetToggle) Open widget menu. (widgetOpen) Close widget menu. (widgetClose) Reset all widget features. (resetAll) Keyboard navigation Variable Description Enable or disable keyboard navigation. (keyboardNavToggle) Enable keyboard navigation. (keyboardNavEnable) Disable keyboard navigation. (keyboardNavDisable) Big Cursor Variable Description Enable or disable big cursor. (bigCursorToggle) Enable big cursor. (bigCursorEnable) Disable big cursor. (bigCursorDisable) Reading Guide Variable Description Enable or disable reading guide. (readingGuideToggle) Enable reading guide. (readingGuideEnable) Disable reading guide. (readingGuideDisable) Contrast feature Variable Description Enable or disable contrast feature. (contrastToggle) Enable contrast feature, integer value from 1 to 4 or empty. (contrastEnable) Disable contrast feature. (contrastDisable) Big text Variable Description Enable or disable big text feature. (bigTextToggle) Enable big text feature, integer value from 1 to 4 or empty. (bigTextEnable) Disable big text feature (bigTextDisable) Highlight feature Variable Description Enable or disable highlight feature. (highlightToggle) Enable highlight feature. (highlightEnable) Disable highlight feature. (highlightDisable) Legible fonts Variable Description Enable or disable legible fonts feature. (legibleFontsToggle) Enable legible fonts feature. (legibleFontsEnable) Disable legible fonts feature. (legibleFontsDisable) Text spacing Variable Description Enable or disable text spacing feature. (textSpacingToggle) Enable text spacing feature, integer value from 1 to 3 or empty. (textSpacingEnable) Disable text spacing feature. (textSpacingDisable) ReadPage Variable Description Enable, disable or change reading speed of the Read Page feature. (readPageToggle) Enable read page feature. (readPageEnable) Disable read page feature. (readPageDisable) PageStructure Variable Description Enable page structure view with predefined headers tab. (pageStructureHeaders) Enable page structure view with predefined landmarks tab. (pageStructureLandmarks) Enable page structure view with predefined links tab. (pageStructureLinks) Disable page structure function. (pageStructureDisable) Tooltips Variable Description Enable or disable tooltips feature. (tooltipsToggle) Enable tooltips feature. (tooltipsEnable) Disable tooltips feature. (tooltipsDisable) Stop Animations Variable Description Enable or disable stop animations feature. (stopAnimationToggle) Enable stop animations feature. (stopAnimationEnable) Disable stop animations feature. (stopAnimationDisable) Quick Accessibility Menu Variable Description Opens quick accessibility menu (openQuickAccessibilityMenu) Widget Settings Variable Description Updates widget language dynamically. No page refresh required. (changeWidgetLanguage) ... View more

This article describes how to use a visitor function to retrieve probabalistic identity data from the Acxiom identity provider and save it in the visitor profile. In this article: Retrieving visitor data and storing it in a visitor profile We recommend using a visitor function to capture the data from Acxiom. For more information on visitor functions, see Event and Visitor Functions. The visitor function does the following: Requests the additional data from Acxiom. Sends an event containing the additional data and tealium_visitor_id to Tealium Collect. The EventStream attributes and visitor attributes are enriched by the event sent from the function. The following figure illustrates the process of retrieving data from the identity provider and saving it in the visitor profile: Prerequisites EventSteam and Functions. The Tealium Collect API as a Data Source. Create visitor attributes to store the additional information. For more information on creating attributes, see Using Attributes. Create an event spec titled acxiom_function_event . This will contain the desired attributes, which will be used to enrich the visitor attributes. For more information on creating attributes, see Using Attributes. Add an enrichment to enrich the visitor attributes with the value of the event attributes. For more information on adding an enrichment, see Using Enrichments. The function works best when the Acxiom Real Tag tag is installed. This identifier will increase the confidence rating for the visitor. Creating a function to process the event To create the function: Navigate to the Functions interface. Click Add Function. Enter a name for the function. Enter appropriate notes to describe the function for later reference. Select the Processed Event trigger. Select the desired event feed for the trigger. Click Continue. Enter the sample code below into the Code box. Customize the code as necessary for your configuration. Save the function. You can test the function with the Test feature and a tool such as Postman API Workbench. For more information on creating a function, see Managing Functions. Example function code The following test example function will attempt to match a visitor profile based off of the attributes you send to it: Attribute Description acxiom_function_event Event Spec name realId Acxiom rTag address User’s address phone User’s phone number email User’s email address fullName User’s full name The function will return any additional user data for profile enrichment. This code is currently in beta. // In an event scoped function, the following modules are available for use: event, auth import { event, store, tealium } from "tealium"; (async () => {         // These endpoints will be specific to each customers setup with Acxiom as they will refer to the customers provisioned private environment.     const access_url="https://mydomain.com/metrics/access_token"     const query_url="https://mydomain.com/metrics"     const query_name="demo_dsapi_match"     // Uncomment this to find out exactly what is available to use in your event object     console.log('Data available:\n', JSON.stringify(event, null, 2));     const data = {};     data.tealium_account = event?.data?.udo?.tealium_account;     data.tealium_profile = event?.data?.udo?.tealium_profile;     data.visitor_id = event?.data?.udo?.visitor_id;     data.trace_id = event?.data?.firstparty_tealium_cookies?.trace_id;     data.acxiom_real_id = event?.data?.udo?.acxiom_real_id || "";     data.customer_email = event?.data?.udo?.customer_email;     data.customer_first_name = event?.data?.udo?.customer_first_name;     data.customer_last_name = event?.data?.udo?.customer_last_name;     data.customer_full_name = `${data.customer_first_name} ${data.customer_last_name}`     // Check if acxiom_real_id is available     // if (typeof data.acxiom_real_id === "undefined") {     //     console.error("acxiom_entity_id is unavailable.");     //     return;     // }     // Pull in refresh token from global variables     const refresh_token = store.get("acxiom_refresh_token")     console.log("refresh_token: ", refresh_token)     // Generate access token     const access_token_request = await fetch(access_url, {         method: "POST",         headers: {             "Content-Type": "application/json",             "Authorization": `Bearer ${refresh_token}`         },         body: `{"grant_type":"refresh_token","refresh_token":"${refresh_token}"}`     })     .catch((error) => {         console.error('Error:', error);     });     const access_token_response = await access_token_request.json();     // console.log("access_token_response:", JSON.stringify(access_token_response));     const access_token = access_token_response.jwt_token;     // console.log("access_token: ", access_token)     // Fetch query_execution_id from Acxiom PAIL with acxiom_real_id     const response = await fetch(`${query_url}/named_queries/${query_name}/execute`, {         method: "POST",         redirect: "follow",         headers: {             "Content-Type": "application/json",             "Authorization": `Bearer ${access_token}`         },         body: `{             "realID": "${data?.acxiom_real_id}",             "address": "${data?.customer_address}",             "phone": "${data?.customer_phone}",             "email": "${data?.customer_email}",             "fullName": "${data?.customer_full_name}"         }`     })     .then(res => {         console.log("Res: ", JSON.stringify(res))         return res     })     // .then(response => console.log("Response: ", JSON.stringify(response)))     .catch(error => console.error('Error: ', error.message));     const body = await response.json();     const query_execution_id = body.query_execution_id         // console.log("Status: " + response.status);     console.log("Body: " + JSON.stringify(body, null, 2));     // Check if Acxiom response data is available     if (!response.ok) {         console.error("Acxiom response data is unavailable.");         return;     }     // Fetch data from Acxiom PAIL with query_execution_id     const payload = await fetch(`${query_url}/query_executions/${query_execution_id}`, {         method: "GET",         headers: {             "Content-Type": "application/json",             "Authorization": `Bearer ${access_token}`         }     })     .then(res => {         console.log("Res: ", JSON.stringify(res))         return res     })     // .then(response => response.json())     // .then(response => console.log("Response: ", JSON.stringify(response)))     .catch(err => console.error(err));     const user_data = await payload.json();     console.log("user_data: ", JSON.stringify(user_data))     let data_object = {};     for (let i=0; i < user_data.column_info.length; i++) {         data_object[user_data.column_info[i].name] = user_data.data[0][i]     }     // data_object = JSON.stringify(data_object)     let newEvent = {};     newEvent = { ...data_object }     newEvent.tealium_event = "acxiom_function_event";     newEvent.visitor_id = data.visitor_id;     newEvent.tealium_trace_id = data?.tealium_trace_id;     newEvent.customer_email = data_object?.email;         console.log("newEvent: " + JSON.stringify(newEvent, null, 2));     // Send data received from Acxiom to Tealium     tealium         .sendCollectEvent(newEvent, data.tealium_account, data.tealium_profile)         .then(response => {             console.log('Status code: ', response.status);             return response;         })         .then(data => console.log('Result: ', JSON.stringify(data, null, 2)))         .catch(error => console.error('Error: ', error.message)); })(); Additional information About Functions Managing Functions Writing Functions Data Transformation Functions Event and Visitor Functions Adding an Authentication to a Function Functions Example Code ... View more

This article explains how the identity providers in Tealium’s Identity Partner Ecosystem work in the Tealium platform and how to use them. Tealium relies on deterministic information sources to use PII to stitch visitor data together into a visitor profile for a single customer view. However, you can use identity providers of first-party and third-party data, which often rely on probabilistic methods of identity resolution, to create high-quality insights about each visitor, prospect and customer. These probabilistic insights can be combined with data collected and profiles enriched by Tealium to enhance relationship data and provide personalized experiences to customers. What do Identity Providers do? Tealium’s Identity Partners provide the following services: Collect first party and third party data into a single customer database. This can be used as a CRM itself, or used to enhance a CRM that a business owns. Collect, clean, and normalize first party data in an ongoing process to ensure the quality of their service. Integrate with UID2.0, the open source ID framework that will be replacing third-party cookies. For example, The Trade Desk offers UID 2.0, which allows the advertiser to share PII, and they send back a short-term anonymous identifier for ad targeting. Some data providers also provide AdTech and publisher-related features. These direct integrations with publisher platforms can support ad targeting, and others allow analysis of ad campaigns in privacy-compliant environments. Tealium provides access to a large number of identity partner integrations across the platform: iQ Tag Management, EventStream, Data Source, AudienceStream, and Functions. Because it can be a lot of work pulling information from each of these sources and combining it into a clear vision of your visitor and customer profile, Tealium is here to make the process of integrating identity provider data from multiple sources smoother and easier. Deterministic vs Probabilistic It is important to understand the difference between deterministic matching and probabailistic data models: Deterministic matching uses first-party data to link device-level data to the appropriate user profiles. Probabilistic models use predictive algorithms to link user data to an individual based on a confidence level. The deterministic method uses PII (email, UID2.0, etc.) to identify the user. Tealium employs the deterministic model with Visitor Stitching. Integrations with probabilistic identity programs typically require the use of Tealium’s functions to process returned data along with the confidence score. How it works Auth0 and CIAM Auth0 uses the Customer Identity Access Management (CIAM) model: When the user logs in to Auth0, their identity is confirmed by the Auth0 authorization server. Tealium appears as an Auth0 action, which can be used through drag and drop integration. The Auth0 Data Source appears under the new Identity category in Tealium. UID 2.0 The Trade Desk and other vendors use UID 2.0, which uses PII for deterministic identification. You will need to configure an enrichment and function code to assign a UID 2.0 to a visitor: For more information, see Using Tealium Functions to Generate a UID2.0 Token.  UID 2.0 cannot be used in the EU due to privacy restrictions. Acxiom and Merkle As identity and data management solution providers, Acxiom and Merkle perform the following roles: Provide customer data strategies, and additional optional services. Require access to Functions and Tealium iQ Tag Management. Cleanse and store first and third party data for businesses, which can group profiles into households, gather demographics, track NCOA (National Change of Address), and more. Identify visitors via probabalistic methods to "stitch deterministically, enrich probabalistically." How you can use Identity Providers You can use an identity provider to immediately share PII such as phone numbers and email addresses with Tealium to enrich customer profiles. This allows you to turn anonymous visitors into known visitors or customers. Because data providers constantly clean and normalize their data, you can use this information to help clean your own data. As third party cookies are deprecated, anonymous retargeting will no longer be possible. So sharing one or more pieces of PII with AdTech ID partners allows identification and targeting of that individual across publishers and domains. Many customers have already hired third-party identity providers to improve their visitor profiles. The Tealium Identity Marketplace can help simplify the process of subscribing to, importing, and incorporating this data. Identity Tags, Connectors, and Data Sources The Identity category in each of the Tags, Connectors, and Data Sources interfaces lists all of the available identifier resources for that part of the platform. Identity and Data Management Solutions Partner Integration Type Summary Documentation Link Acxiom Tag First-party tag implemented across brand’s owned and paid media. Provides a unified and consistent identity across owned and paid media. Allows for linkages to be built by both deterministic and probabilistic signals. Operates as a fully first-party solution, meaning running off of the client’s own domain and with no data sharing with other entities. Able to resolve identities even in the absence (or non-acceptance) of cookies Acxiom Real Identity rTag Setup Guide Auth0 Data Source An Action within the Auth0 integration market that sends user data from Auth0 upon Login Tealium Integrations at Auth0 Merkle Tag Merkury uses an organization’s first-party CRM data and valuable interactions such as logins, outbound email campaigns and media reach to create and grow a universe of person-based IDs. Tealium IQ’s data mapping feature allows you to control which data points are shared with Merkury. Merkle Merkury Tag Setup Guide Advertising Identity Services Partner Integration Type Summary Documentation Link Criteo Tag Cookie Matching associates a cookie that identifies a Tealium visitor to the cookie that identifies the user for Criteo.  Criteo Cookie Matching Service Tag Setup Guide Connector Audience Match is a flexible customer targeting solution. Criteo Audience Match Connector Setup Guide Epsilon Tag Returns a list of partner pixel URLs that, when called by the browser, synchronize IDs with exchanges. This allows users can to be identified and messaged after they leave your site. Epsilon Partner Sync Web Service Tag Setup Guide Tapad Tag This allows Tapad and you to jointly identify devices in order to take action on these devices. Note: Fires once per Tealium visitor session. Sends the tapad_id server-side attribute to Tealium. TAPAD Cookie Matching Service Tag Setup Guide The Trade Desk (TDD) Tag The Trade Desk Universal Pixel enables marketers to gain more visibility into user data, and analyze reporting at a more granular level. Trade Desk Universal Pixel Setup Guide for Tealium iQ Connector The Trade Desk Connector can be used for posting enriched Visitor Profiles and Audiences to TDD for more personalized advertising campaigns. The Trade Desk Cookie Matching Service Tag Setup Guide (used with UID2.0 Function) Function UID2.0 is an open source identifier that replaces 3rd-party cookies. The Trade Desk Connector Setup Guide (used with UID2.0 Function) Identity provider privacy restrictions: Identity Partners have limitations on where they can operate due to legislation such as the GDPR. Each partner will have different capabilities (for example, Merkle is Global, while the TDD UID2.0 cannot be used within the EU). Acxiom - GDPR Auth0 - Auth0 General Data Protection Regulation Compliance Criteo - GDPR: What You Need to Know | Criteo Epsilon - GDPR: Steps towards compliance Merkle - Data Protection Statement Tapad - Privacy Notice - Global TDD - UnifiedID2 How to implement an identity provider To implement identity providers For The Trade Desk and UID 2.0, see Using Tealium Functions to Generate a UID2.0 Token.  For Acxiom, see Using Tealium Functions for Acxiom Identity Resolution. We will add more function examples soon. ... View more

This article describes how to set up the Rockerbox tag in your Tealium iQ Tag Management account. Rockerbox is the leading attribution provider for digital companies. Rockerbox provides one source of truth across all of your marketing, enabling companies to quickly uncover the effectiveness of all of their marketing. In this article: Tag Tips Use mappings to: Override standard config values and set custom parameters Trigger standard and custom events Supports the following E-Commerce extension values: Order Id ( _corder ) Revenue ( _ctotal ) Coupon ( _cpromo ) Products ( _cprod ) Tag Configuration Navigate to the Tag Marketplace to add a new tag. Read the Tag Overview article for general instructions on how to add a tag. When adding the tag, configure the following settings: Client Auth: Client Auth ID Allow automatic page view: Load Rules Load the tag on all pages or set conditions for when your tag will load. For more information about load rules, see the Load Rules documentation. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Standard Variable Description Base Url ( base_url ) [String] Client Auth ( client_auth ) [String] Automatic Page View ( automatic_pageview ) [Boolean] Disable Push State ( disablePushState ) [Boolean] E-commerce Variable Description External Id (external_id) [String/Number] Order Id ( order_id ) (override _corder) [String/Number] Revenue ( revenue ) (override _ctotal) [String/Number] Coupon ( coupon ) (override _cpromo) [String] Products ( products ) (override _cprod) [Array] Email ( email ) [String] Address Variable Description Country ( rb_country ) [String] State ( rb_state ) [String] City ( rb_city ) [String] Address 1 ( rb_address_1 ) [String] Address 2 ( rb_address_2 ) [String] Zip Code ( rb_zip_code ) [String] Events To map events, refer to Create an Event Mapping. Variable Description Page View (view) view Purchase ( conv.purchase ) conv.purchase Add To Cart ( conv.add_to_cart ) conv.add_to_cart Initiate Checkout ( conv.initiate_checkout ) conv.initiate_checkout Create Account ( conv.create_account ) conv.create_account Email Signup ( conv.email_signup ) conv.email_signup Enrollment ( conv.enrollment ) conv.enrollment Purchase Subscription ( conv.purchase.subscription ) conv.purchase.subscription Purchase One Time ( conv.purchase.one_time ) conv.purchase.one_time Custom custom Event-specific Parameters To map events, refer to Create an Event Mapping. Variable Description Page View ( view ) view Purchase ( conv.purchase ) conv.purchase Add To Cart ( conv.add_to_cart ) conv.add_to_cart Initiate Checkout ( conv.initiate_checkout ) conv.initiate_checkout Create Account ( conv.create_account ) conv.create_account Email Signup ( conv.email_signup ) conv.email_signup Enrollment ( conv.enrollment ) conv.enrollment Purchase Subscription ( conv.purchase.subscription ) conv.purchase.subscription Purchase One Time ( conv.purchase.one_time ) conv.purchase.one_time Custom custom ... View more

Learn about the new features and fixes released in August 2022. Client-Side Tags New/Cool Stuff New marketplace tag: Dotmetrics. New marketplace tag: Twitter Pixel tag. Fixes Updated Copy Tag feature to correctly transfer tag template modifications. Updated platform to terminate session on password reset or change. Server-Side Connectors New/Cool Stuff New marketplace connector: Yahoo Conversions. New marketplace connector: Yahoo DataX New server-side data source: Google Ads Leads. Fixes Updated Twitter Custom Audiences to fix the expires_at and effective_at parameters to use ISO 8601 format. Deprecations Deprecated the Google Ads Enhanced Conversions connector, renamed it to Google Ads Enhanced Conversions - Legacy. ... View more

This article describes how to set up the Twitter Pixel tag in your Tealium iQ Tag Management account. The Twitter Pixel helps you measure your return on investment by tracking the actions users take after viewing or engaging with your ads on Twitter. Twitter's conversion tracking lets you attribute conversions beyond last link clicked, to include actions driven by all types of ad engagements, such as link clicks, retweets, likes, and impressions. In this article: Tag Tips Use mappings to: Set up event triggers. Map event-specific parameters to Event Code IDs. Dynamically override standard config values. Dynamically override E-Commerce extension values. Supports the following E-Commerce extension parameters: Order ID Order Total Currency List of Product IDs List of Names List of Categories List of Quantities Tag Configuration Navigate to the Tag Marketplace to add a new tag. Read the Tag Overview article for general instructions on how to add a tag. When adding the tag, configure the following settings: Pixel ID: Also referred to as your Twitter Pixel ID. You can find it in your Twitter Pixel code snippet: pid in the following example: twq('config','pid'); Load Rules Load the tag on all pages or set conditions for when your tag will load. For more information about load rules, see the Load Rules documentation. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Standard Parameters Variable Description Twitter Pixel ID ( pixel_code ) [String] Email Address ( email_address ) [String] Phone Number ( phone_number ) [String] External ID ( external_id ) [String] Text that was searched for on your website ( search_string ) [String] A string description for additional info ( description ) [String] Twitter click ID that can be included with any request ( twclid ) [String] E-Commerce Variable Description Order Total ( order_total ) (Overrides _ctotal ) [String] Currency ( order_currency ) (Overrides _ccurrency ) [String] Order ID ( order_id ) (Overrides _corder ) [String] List of Categories ( product_category ) (Overrides _ccat) [Array] List of SKUs ( product_skus ) (Overrides _csku ) [Array] List of Names ( product_names ) (Overrides _cprodname ) [Array] List of Prices ( product_unit_price ) (Overrides _cprice ) [Array] List of Quantities ( product_quantity ) (Overrides _cquan ) [Array] ID associated with a group of product variants ( content_group_id ) [String] Event-specific Parameters To map events, refer to Create an Event Mapping. Variable Description Twitter Pixel ID ( pixel_code ) pixel_code Email Address ( email_address ) email_address Phone Number ( phone_number ) phone_number External ID ( external_id ) external_id Text that was searched for on your website ( search_string ) search_string A string description for additional info ( description ) description Twitter click ID that can be included with any request ( twclid ) twclid Order Total ( order_total ) (Overrides _ctotal ) order_total Currency ( order_currency ) (Overrides _ccurrency ) order_currency Order ID ( order_id ) (Overrides _corder ) order_id List of Categories ( product_category ) (Overrides _ccat ) product_category List of SKUs ( product_skus ) (Overrides _csku ) product_skus List of Names ( product_names ) (Overrides _cprodname ) product_names List of Prices ( product_unit_price ) (Overrides _cprice ) product_unit_price List of Quantities ( product_quantity ) (Overrides _cquan ) product_quantity ID associated with a group of product variants ( content_group_id ) content_group_id Custom Parameter custom_parameter ... View more

This article describes how to set up the DMD - AIMXR tag in your Tealium iQ Tag Management account. DMD, an IQVIA Business, is a healthcare identity company dedicated to connecting marketers to key healthcare audiences for impactful engagement. Their Audience Identity Manager Extended Reach (AIMXR) provides identity resolution for Healthcare Professionals (HCPs). This tag will load DMD’s AIMXR library and will scan for a DMD tagged device. Upon identification, AIM.ondetect() will execute whatever is located within the function. In this article: Tag Configuration Navigate to the Tag Marketplace to add a new tag. Read the Tag Overview article for general instructions on how to add a tag. When adding the tag, configure the following settings: API KEY: For merchants, this is the production client id. For partners, this is the partner client id. Trigger Event On Detect: Trigger a utag.link() callback event upon the confirmation of a AIMXR Tagged Identity (request AIMXR Signal Data to be returned) Load Rules Load the tag on all pages or set conditions for when your tag will load. For more information about load rules, see the Load Rules documentation. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Standard Variable Description API Key (string) (apiKey) Trigger Event On Detect (boolean) (triggerEvent) ... View more

This article describes how to set up the Criteo Cookie Matching Service tag in your Tealium iQ Tag Management account. Criteo Cookie Matching Service enables a buyer to associate the cookie that identifies a Tealium visitor, and the cookie that identifies the user for Criteo. In this article: Tag Tips If left blank, Tealium Account and Profile will be automatically populated. Sends the following server-side attribute back to Tealium: criteo_user_id For more information about cookie matching in EventStream, see: Understanding Persistent Cookie Matching in EventStream. Tag Configuration Navigate to the Tag Marketplace to add a new tag. Read the Tag Overview article for general instructions on how to add a tag. When adding the tag, configure the following settings: Tealium Account: (Optional) Your Tealium account. Tealium Profile: (Optional) Your Tealium profile. Days between syncs: (Optional) How often to recheck the ID. This value defaults to 7 days. Data Source Key: (Optional) The data source key from your server-side configuration. Use /event endpoint: Send data to the /event endpoint. Load Rules Load the tag on all pages or set conditions for when your tag will load. For more information about load rules, see the Load Rules documentation. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Standard Variable Description Tealium Account ( tealium_account ) [String] Tealium Profile ( tealium_profile ) [String] Days between syncs ( days_between_syncs ) [Number] Data Source Key ( tealium_datasource ) [String] Use /event endpoint ( use_event_endpoint ) [Boolean] ... View more

This article describes how to set up the CJ Affiliate Mobile Application Tag in your Tealium iQ Tag Management account. CJ Affiliate is the leading global affiliate marketing network, specializing in pay-for-performance programs that drive results for businesses around the world. The purpose of the CJ Affiliate Mobile Application Tag is to inform CJ of user activity across clients' Mobile Applications, allowing for tracking of installations and In App Events. In this article: Tag Tips Use mappings to: Dynamically override config data. Dynamically override the E-Commerce extension values. Send additional data values. Trigger events. Tag Configuration Navigate to the Tag Marketplace to add a new tag. Read the Tag Overview article for general instructions on how to add a tag. When adding the tag, configure the following settings: Client ID (CID): This value is set as each client's CJ Enterprise ID, a static value provided by CJ. Type: This is a static value provided by CJ. Each Action will have a unique TYPE value. Sale Tag Type: Standard: CID , OID , TYPE and CURRENCY are sent. Advanced: Sends additional values ITEM , AMT , QTY , DCNT . Load Rules Load the tag on all pages or set conditions for when your tag will load. For more information about load rules, see the Load Rules documentation. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Standard Variable Description User Agent (UA) (required) [String] The User Agent. CJ Client ID (CID) (required) [Number] Each client's CJ Enterprise ID, a static value provided by CJ. CJ Action ID (TYPE) (required) [Number] Each Action will have a unique TYPE value, a static value provided by CJ. Order Number/Unique ID (OID) (required) [Alphanumeric] A unique order or invoice identifier, used to reconcile orders in the client's system with CJ to validate each sale or lead. This value is truncated after the 96th character. May only contain alphanumeric characters, or underscores. Does not include PII, such as a full or partial email address. Method (METHOD) [String] Time Of Action (EVENTTIME) [Alphanumeric] The URL-encoded time of the event in any of the following formats: ISO 8601 standard yyyy-mm-ddThh24:mm:ss+/-hh:mm year, month, date, time, offset from UTC YYYY-MM-DDTHH:MM:SSS.SSSZ CJEVENT Value From URL (CJEVENT) (required) [Alphanumeric] A unique CJ-generated token passed to your site that stores referring publisher data for cookieless attribution. Subtotal Associated With Action (AMOUNT) (required) [Number] The subtotal of the purchase, not including shipping or tax. Currency Code (CURRENCY) (required) [ISO Currency Code] A three-letter code that identifies the currency used for the order's amount value. If not specified, will default to the Advertiser functional currency in the CJ interface. Vendor Name (VENDOR) (required) [Alphanumeric] The name of the vendor sending the postback to CJ. Discount (DISCOUNT) (required) [Number] A discount value applied to the entire order. Coupon (COUPON) [String] A coupon, voucher, or discount code used at the time of purchase. SKU (SKU) (Overrides _cprod ) [Array] The identifier of each item in the order. This value must be less or equal to 100 characters. There is a maximum of 100 sets of item-based values in each order. Only alphanumeric strings, dashes, and underscores are allowed. Items Amount (AMT) (Overrides _cprice ) [Array] The price of each item in the order. Quantity (QTY) (Overrides _cquan ) [Array] The quantity of each item in the order. Any decimals in the value are ignored, so 1.0 will be interpreted as 10 . Items Discount (DCNT) (Overrides _cpdisc ) [Array] The discount value that is applied to each individual item in the order. Additional parameters Variable Description Brand ( brand ) [Alphanumeric] Brand of items purchased. If multiple brands were purchased, one will be selected. Brand Id ( brandId ) [Alphanumeric] Identifier of the brand of items purchased. If multiple brands were purchased, one will be selected. Category ( category ) [Alphanumeric] Category of items purchased. If multiple categories were purchased, one will be selected. Customer Status ( customerStatus ) [Alphanumeric] Customer's status based on past purchases (for example: new , lapsed , return , etc.). Delivery ( delivery ) [Alphanumeric] Method of delivery (for example: in_store_pick_up , digital , express , etc.). Loyalty Earned ( loyaltyEarned ) [Alphanumeric] Loyalty points earned on the transaction. Loyalty First Time Signup ( loyaltyFirstTimeSignup ) [Alphanumeric] Whether this order coincided with the customer joining the loyalty program. Loyalty Level ( loyaltyLevel ) [Alphanumeric] The customer's level in the loyalty program. Loyalty Redeemed ( loyaltyRedeemed ) [Alphanumeric] Loyalty points used during the transaction. Loyalty Status ( loyaltyStatus ) [Alphanumeric] Whether the customer is a loyalty member. Marketing Channel ( marketingChannel ) [Alphanumeric] Any additional advertiser-defined marketing channels assigned to this transaction. Events To map events, refer to Create an Event Mapping. Variable Description Purchase ( purchase ) purchase Conversion ( conversion ) conversion Custom custom ... View more

You trust us with your real-time data, so anything that slows things down for you, we want to speed back up. We’re happy to announce significant performance improvements to the Attributes experience in Tealium EventStream and Tealium AudienceStream. What Changed? If your account profile contains a large number of attributes in EventStream and AudienceStream, you may have experienced significant performance lag from all the data loading up at once on the attributes screens. The more attributes, the longer the wait for the list to appear. What's New We’ve changed the attribute details to now appear in a dedicated slideout. This reduces the amount of data the attributes screen needs to load, speeding things up for you and letting you get right back to delighting your customers with great experiences. We have not made any changes to the adding or editing of attributes, those are still the same. Reply to this post to provide feedback To send feedback, simply reply to this post with your questions or comments. ... View more

This article describes how to set up the PayPal Shopping Analytics tag in your Tealium iQ Tag Management account. The SDK collects analytical data from visitors to your website. This data is used by PayPal to provide you an option to re-target visitors who drop off. In this article: Tag Tips Use mappings to: - Dynamically override config data - Dynamically override the E-Commerce extension values - Event trigger Tag Configuration Navigate to the Tag Marketplace to add a new tag. Read the Tag Overview article for general instructions on how to add a tag. When adding the tag, configure the following settings: Client ID: For merchants, this is the production client ID. For partners, this is the partner client ID. Load Rules Load the tag on all pages or set conditions for when your tag will load. For more information about load rules, see the Load Rules documentation. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Settings Variable Description Screen Name (client_id) (Required) [String] User Id (user_id) [String] First Time Visit (first_time_visit) [Boolean] Page View Variable Description Page Type (page_type) (Required) [String] Page Name (page_name) [String] Page Path (page_path) [String] Page Category Name (page_category_name) [String] Page Category Id (page_category_id) [String] Deal Id (deal_id) [String] Deal Name (deal_name) [String] Deal Value (deal_value) [String] Search Results Count (search_results_count) [String] Product View Variable Description Product Id (product_id)  (required) [String] (Overrides _cprod) Product Name (product_name)  [String] (Overrides _cprodname) Product Url (product_url) [String] Product Price (product_price)  [String] (Overrides _cprice) Product Brand (product_brand)  [String] (Overrides _cbrand) Product Category Name (product_category_name) [String] (Overrides _ccat) Product Category Id (product_category_id) [String]  Product Discount (product_discount)  [String] (Overrides _cpdisc) Events Variable Description Page View (page_view) page_view Product View (product_view) product_view ... View more

This article describes how to set up the Merkle Merkury tag in your Tealium iQ Tag Management account. Merkury, Merkle’s identity resolution platform, helps organizations master cookieless identity through control and transparency. Powered by people-based data across 1,000+ attributes, Merkury integrates with Tealium to increase site visitor identification rates, inform cross-channel targeting, personalization, measurement, and more. Using our wizard-driven integration, organizations can create load rules to determine when and where to trigger Merkury’s JavaScript tag. Tealium IQ’s data mapping feature allows you to control which data points are shared with Merkury. In this article: Tag Tips Adobe MediaSDK requires the Adobe Experience Cloud ID Service as well as AppMeasurement for JS to be loaded first, preferably bundled. This tag is fired via utag.track('video', data); which should be implemented in your video event handlers. Tag Configuration Navigate to the Tag Marketplace to add a new tag. Read the Tag Overview article for general instructions on how to add a tag. When adding the tag, configure the following settings: CID: CID is a client-specific numeric account number generated from Merkury Team. Domain: Domain is the client website's domain (for example, merkleinc.com ). Send Merkury Identity Event: Whether to generate the  merkury_identity event, which contains the following information: event merkury_email_sha256 merkury_hmid merkury_confidence_score Load Rules Load the tag on all pages or set conditions for when your tag will load. For more information about load rules, see the Load Rules documentation. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Standard Variable Description CID (sv_cid) DOMAIN (sv_origin) Client ID (uID) Email Address (em) MD5 Email Hash (eme) Client Email ID (emID) ... View more

Learn about the new features and fixes released in April 2022. Tealium iQ Tag Management Fixed an issue with duplication of items in the Admin menu when switching profiles or versions. Updated the profile switcher to list entries in alphabetical order. Client-Side Tags New marketplace tag: Epsilon Partner Sync Web Service. New marketplace tag: Rokt. Fixed an issue with the Google Analytics Tag failing when it checks configuration attributes, but tries to use non-existent attributes. Fixed an issue with the Google Analytics 4 tag where the event_callback parameter fails to map properly. Fixed an issue with the Tealium Collect Tag that caused a 400 error when switching from the default endpoint to the HTTP API endpoint while changing to a non-default (Global) region. Tealium EventStream and Tealium AudienceStream Fixed an issue in the assigned actions tab where deactivated connectors and actions were improperly appearing as active. Fixed an issue in the data sources interface to properly obscure passwords and other credentials. Fixed an issue in the event feed interface with invalid dates. Fixed an issue with attribute enrichments to ensure that only users with permissions to use IP addresses can include Client IP in rules. Updated the connectors interface to improve scrolling, collapsed views, and expanded views. Updated the event feed interface to allow duplication of event feeds. Updated the manage rules tool with a new search box. Updated the visitor lookup tool with a new keyword search box. Updated the visitor lookup tool to include a JSON viewer.  Tealium Predict ML Released significant improvements in the workflows to create, train, and deploy models. (Learn more) Server-Side Connectors New/Cool Stuff New marketplace connector: Amazon Advertising DSP. New marketplace connector: Doceree. New marketplace connector: Epsilon Event API. Fixes Updated the Google Ads API connector to version 10. (Learn more) Updated the TikTok connector to include Access Token, App ID and Secret in its configuration. (Learn more) Fixed an issue with the Firebase Cloud Messaging connector where a 200 HTTP response that contains error messages would fail to parse properly. ... View more

This article describes how to set up the Epsilon Partner Sync Web Service Tag tag in your Tealium iQ Tag Management account. Epsilon is the leader in outcome-based marketing with a rich, 50-year heritage in helping marketers anticipate, activate, and prove measurable business outcomes. In this article: Tag Configuration First, go to the tag marketplace and add the Epsilon Partner Sync Web Service Tag tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Advertiser Identifier: dtm_cid Secondary Advertiser Identifier: dtm_cmagic Page Visit Form ID: dtm_fid Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Tag Configuration Variable Description Advertiser Identifier (dtm_cid) [String] Secondary Advertiser Identifier (dtm_cmagic) [String] Page Visit Form ID (dtm_fid) [String] User ID (dtm_cookie_id) [String] dtm_token_s [String] dtmc_tcf_string [String] ... View more

This article describes how to set up the Doceree connector. Doceree is a global network of physician-only platforms for programmatic marketing of targeted ads for physicians. The Doceree Connector allows users to manage Doceree audiences and users. In this article: Connector Actions Action Name AudienceStream EventStream Add User NPI ✓ ✗ Remove User NPI ✓ ✗ 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: Username Required: Username for your Doceree account. Password Required: Password for your Doceree account. Click Done when you are finished configuring the connector. Action Settings — Parameters and Options Click Continue to configure the connector actions. Enter in a name for the action and then select the action type from the drop-down menu. The following section describes how to set up parameters and options for each action. Action — Add User NPI Batch Limits This action uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following thresholds is met: Max number of requests: 1000 Max time since oldest request: 10 minutes Max size of requests: 1 MB Parameters Parameter Description Account The Doceree account associated with this audience. Audience ID The audience that you want to add the user to. NPI The unique identifier (NPI) for the user. Action — Remove User NPI Parameters Parameter Description Account The Doceree account associated with this audience. Audience ID The audience that you want to remove the user from. NPI The unique identifier (NPI) for the user. ... View more

This article describes how to set up the Rokt tag in your Tealium iQ Tag Management account. Immediately add profit with third-party offers from well-known advertisers on your confirmation page through Rokt Ecommerce. You can also optimize campaign performance for Rokt Ads by integrating conversion attribution through Tealium. For more information about Rokt's suite of SDKs and APIs, please read the Rokt Integration Guides. In this article: Tag Tips Use mapping to override the standard config values and trigger events. Tag Configuration First, go to the tag marketplace and add the Rokt tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Rokt Account ID: Your Rokt account ID. Two-step Email: Send email address only on positive engagement. Use Sandbox: Send events to sandbox account for testing. Load Rules Load Rules determine when and where to load an instance of the Rokt tag on your site. Create a Load Rule to load the Rokt tag on your conversion page. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Standard Variable Description Email (email) First Name (firstname) Last Name (lastname) Mobile Number (mobile) Zip or Postal Code (zipcode) Country (country) Language (language) Use Sandbox (sandbox) E-Commerce Variable Attribute Description Confirmation Number (confirmationref) This variable overrides the _corder variable. Amount (amount) This variable overrides the _ctotal variable. Currency (currency) This variable overrides the _ccurrency variable. Payment Type (paymenttype)   ccbin (ccbin)   List of Item Prices (price) [Array] This array overrides the_cprice variable. List of Item Quantites  (quantity) [Array] This array overrides the_cquan variable List of Item Major Categories  (majorcat) [Array] This array overrides the_ccat variable List of Item Major Category IDs (majorcatid) [Array] List of Item Minor Categories  (minorcat) [Array] This array overrides the _ccat2 variable List of Item Minor Category IDs  (minorcatid) [Array] List of Product Names  (productname) [Array] This array overrides the_cprodname variable. List of Item SKUs (sku) [Array] This array overrides the_csku variable. ... View more

This article describes how to set up the Schema App tag in your Tealium iQ Tag Management account. Schema App is an organic search catalyst, designed to help digital marketers increase organic search performance, productivity and profitably by quickly and easily integrating schema markup across their web portfolio. Schema App is the world's leading platform for adopting and maintaining Schema Markup at scale without writing, copying, or pasting code. Just enter the information from your page, click save, and you are done. Stay on the forefront of organic search with Schema App. In this article: Tag Tips Account ID and API Key can be found in the application under the menu Integrations > JavaScript page. Tag Configuration First, go to the tag marketplace and add the Schema App tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Account ID: Your Schema App Account ID API Key: Your Schema App API Key Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Standard Variable Description Account ID (account_id) API Key (api_key) Base URL/API Endpoint (base_url) ... View more