Tealium Learning Center

This article describes how to set up the MNTN (formerly Steelhouse)Smarter Pixel tag in your Tealium iQ Tag Management account. In this article: Tag Tips Use mapping to dynamically override the Account ID or to pass data into the "additional" parameter. Conversion tag fires when the Order ID is set. Supports these E-Commerce extension parameters: Order ID ( _corder ) Sub Total ( _csubtotal ) List of Product IDs ( _cprod ) List of Quantities ( _cquan ) List of Prices ( _cprice ) Tag Configuration First, go to the tag marketplace and add the MNTN Smarter Pixel tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Account ID Example: 12345 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 acct Account ID Additional Variables Variable Description adv.track.myvar Additional Tracking Variable adv.conv.myvar Account Conversion Variable E-Commerce Variable Description order_id Order ID Overrides _corder . order_subtotal Subtotal Overrides _csubtotal . product_id Array List of Product IDs. Overrides _cprod . product_quantity Array List of Quantities. Overrides _cquan . product_unit_price Array List of Prices. Overrides _cprice ... View more

This article describes how to set up the LinkedIn Insight Tag tag in your Tealium iQ Tag Management account. In this article: Tag Tips Override standard configs via mapping. You may enter a comma-separated list of Partner IDs in the Partner ID field. Uses the following E-Commerce variables: Order ID (_corder) Order Total (_ctotal) Order Currency (_ccurrency) Customer ID (_ccustid) Tag Configuration First, go to the tag marketplace and add the LinkedIn Insight Tag tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Partner ID: Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Standard Variable Description Partner ID (partner_id) Custom Channel (linkedin.custom_channel_id) Custom Group ID (linkedin.custom_group_id) Custom User ID (linkedin.custom_user_id) Zoom Info ID (linkedin.zoom_info_id) Title (linkedin.title) Domain (linkedin.domain) Company (linkedin.company) Gender (linkedin.gender) Location (linkedin.location) Education (linkedin.education) Email SHA256 (linkedin.email_sha256) Email SHA512 (linkedin.email_sha512) Raw Data (linkedin.raw_data) Raw Data Overwrite (linkedin.raw_data_overwrite) Encrypted Data (linkedin.encrypted_data) Partner Data (linkedin.partner_data) Sic Code (linkedin.sic_codes) Employee Range (linkedin.employee_range) Default Keywords (linkedin.default_keywords) Async Target (linkedin.async_target) Use Iframe (linkedin.use_iframe) Use Callback (linkedin.use_callback) Test URL (linkedin.test_url) E-Commerce Variable Description Order ID (order_id) (Overrides _corder) Order Total (order_total) (Overrides _ctotal) Currency (order_currency) (Overrides _ccurrency) Promo Code (order_coupon_code) (Overrides _cpromo) Customer ID (customer_id) (Overrides _ccustid) ... View more

This article describes how to set up the Adobe Experience Platform Web SDK (BETA) tag in your Tealium iQ Tag Management account. In this article: Tag Tips Use mappings to override standard config values and set custom parameters. If you are configuring multiple instances, you must provide a unique Config ID and Org ID for each instance. Provide multiple values in a comma-separated list. Tag Configuration First, go to the tag marketplace and add the Adobe Experience Platform Web SDK (BETA) tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Instance Name The namespace for your SDK. The default value is alloy. Config ID Your Adobe-assigned configuration ID. This ID links the SDK to the appropriate accounts and configuration. Org ID Your Adobe-assigned Experience Cloud organization ID. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Standard Variable Description clickCollectionEnabled Boolean Click Collection Enabled context Array Context cookieDestinationsEnabled Boolean Cookie Destinations Enabled debugEnabled Boolean Debug Enabled decisionScopes Array Decision Scopes defaultConsent String Default Consent downloadLinkQualifier String Download Link Qualifier edgeConfigId String Config ID edgeDomain String Edge Domain event_type String Event Type errorsEnabled Boolean Errors Enabled idMigrationEnabled Array ID Migration Enabled instanceName String Instance Name onBeforeEventSend Function onBeforeEventSend function orgId String Org ID prehidingStyle String Prehiding Style renderDecisions Boolean Render Decisions thirdPartyCookiesEnabled Boolean Third Party Cookies Enabled urlDestinationsEnabled Boolean URL Destinations Enabled custom.## Custom Data commandCallback Function commandCallback Function E-Commerce Variable Description purchaseID Order ID Overrides _corder . priceTotal Order Total Overrides _ctotal . currencyCode Currency Overrides _ccurrency . product.name Array List of Names Overrides _cprodname . product.SKU Array List of SKUs Overrides _csku . product.quantity Array List of Quantities Overrides _cquan . product.priceTotal Array List of Prices Overrides _cprice . payment.transactionID Array Payment Transaction ID payment.paymentAmount Array Payment Amount payment.paymentType Array Payment Type payment.currencyCode Array Payment Currency Code Commands/Events Variable Description advertising.clicks Clicks advertising.completes Completes advertising.conversions Conversions advertising.federated Federated advertising.firstQuartiles First Quartiles advertising.impressions Impressions advertising.midpoints Midpoints advertising.starts Starts advertising.thirdQuartiles Third Quartiles advertising.timePlayed Time Played commerce.checkouts Checkouts commerce.productListAdds Product List Adds commerce.productListOpens Product List Opens commerce.productListRemovals Product List Removals commerce.productListReopens Product List Reopens commerce.productListViews Product List Views commerce.productViews Product Views commerce.purchases Purchases commerce.saveForLaters Save For Laters delivery.feedback Feedback web.webinteraction.linkClicks Link Clicks web.webpagedetails.pageView s Page Views identityMap Identity Map custom Custom identityMap Parameters Variable Description id_namespace Array, String ID Namespace id Array, String ID authenticatedState Array, String Authenticated State primary Array, String Primary ... View more

Learn about the new features and fixes released in August 2021. Tags New/Cool Stuff New marketplace tag: Adobe Experience Platform Web SDK (Beta). (Learn more) Updated the AT Internet SmartTag tag to add a configuration option to add the ability to reset page context if needed. (Learn more) Updated the Braze Web SDK tag to support version 3.3. (Learn more) Updated the Base URL for the Braze Web SDK tag. (Learn more) Updated the Google Analytics (gtag.js) tag to use the set command for dimensions and metrics scoped to "All Page Hits". (Learn more) Updated the Google Analytics 4 (GA4) tag to add event-specific parameters for default page view. (Learn more) Updated the LinkedIn Insight tag to add support for multiple partner IDs. (Learn more) Updated the Steelhouse Smarter Pixel tag to the new brand name MNTN Smarter Pixel. (Learn more) Updated the Tealium Collect tag to add a conditional check to stop tag execution for update_consent_cookie events from Tealium SDKs. (Learn more) Fixes Corrected a syntax error in the Adobe AppMeasurement for JS tag for Version 2.22.0. (Learn more) Updated auto_initialize mapping with correct logic for the Adjust Mobile Remote Command Tag. (Learn more) Added the internal search plug-in to the AT Internet SmartTag tag to support the variables in the Internal Search category. (Learn more) Corrected an issue with the Tealium Collect tag with single page applications that use the tc_string . (Learn more) Updated the Google Analytics 4 (GA4) tag to include support for up to five (5) previously missing item categories. (Learn more) Updated the Google Analytics 4 (GA4) tag to correct the Page View flag condition as it is not used. (Learn more) Updated the Google Analytics 4 (GA4) tag to add missing product_variant e-commerce option. (Learn more) Connectors New/Cool Stuff New marketplace connector: Qualtrics XM Directory (Learn more) Updated the Braze connector to support an EU endpoint. (Learn more) The Google Ads Enhanced Conversions connector is now generally available (GA) in the connector marketplace and available to all customers. (Learn more) Updated the Facebook Marketing API version for the Facebook App Events, Facebook Audiences, Facebook Messenger, Facebook Conversions, and Facebook Offline Conversions connectors from v10.0 to v11.0. (Learn More) Updated the Facebook Audiences connector to add a checkbox to the Create Custom Audience modal. (Learn More) Updated the Facebook Audiences connector to support value-based lookalikes that can be used by Facebook to determine which users in an audience carry the most value, in a quantifiable way. (Learn More) Updated the Facebook Conversions connector to require a User Agent, Action Source and Event Source URL if a web event takes place. (Learn More) Added the Test Event Code data mapping event to the Facebook Conversions connector to support the Facebook Test Events tool. (Learn More) An IP Address is no longer a required User Agent field when using the Facebook Conversions connector. (Learn more) Updated the Facebook Conversions connector to contain a Pixel_ID that can be used to override the value provided in the Configuration setup. (Learn More) Updated the Snapchat Conversions connector to add Tealium as integration parameter. (Learn more) Updated the Snapchat Conversions connector to ignore empty or null hashed values. (Learn more) The Zoho CRM connector has been deprecated and replaced with V2. (Learn more) Fixes Updated the Lookalike field for the Facebook Audiences connector to correctly require a number type attribute type instead of a string attribute. (Learn More) Corrected issue with the Zoho CRM connector where values displayed twice in the Duplicate Check Fields drop-down list. (Learn more) iQ Tag Management New/Cool Stuff Added profile logo validation restrictions for the type of URL that can be linked in the profile logo URL. Customer Data Hub New/Cool Stuff Updated the Predict model strength training details to place higher importance on the Recall score instead of the F1 score. (Learn more) Updated the deployed model sparkline graph in Predict to show live performance metrics. (Learn more) Updated the Functions feature to support the JavaScript flatten object method. (Learn more) Fixes Corrected issue in the Functions feature that caused a type error when using the Fetch POST method without the body parameter. Updated the supported version of jQuery from 3.4.1 to 3.6.0 to resolve a potential security vulnerability and corrected issues that could be caused by the jQuery upgrade. Resolved an issue in the server-side date picker in the user interface that was introduced with the jQuery support upgrade to v3.6.0. Installations Mobile Android Added lifecycle variables to now include all events for Kotlin, not just lifecycle events. Added configuration options to override the profile used for consent logging for Kotlin. Updated TealiumConfig class for Kotlin to accept a customVisitorId . Updated TealiumConfig class for ReactNative to accept a customVisitorId . Updated Kotlin ConsentLogging to send as a Dispatch rather than directly to EventStream. Corrected issue with the Xamarin SDK when parsing of Array of Strings through a dictionary. iOS Corrected issue with Swift where ATT status did not refresh as expected without restarting the application. Corrected  TealiumASIdentifierManager class issue in Swift where ATT status did not update as expected. Corrected issue in Ruby that caused Collect requests to direct to http instead of https . Updated Cordova to support V2. Updated Xamarin to support v1.0.3. ... View more

This article describes how to set up the Mailgun connector. In this article: Connector Actions Action Name AudienceStream EventStream Send Email ✓ ✓ Add Member to List ✓ ✗ Update Member in 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: Password Your API key is the password. Click the Security tab under the Account section of the control panel to manage your API key. For more information on authentication, visit: Mailgun API Reference: Authentication. 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 - Send Email Parameters Parameter Description My Domain The domain of your Mailgun account. For more information, see: Mailgun API Reference: Base URL. From Email address of the sender. For more information on this endpoint, see: Mailgun API Reference: Messaging > Sending. To Email address of the recipient. Example: bob@host.com or Bob <bob@host.com> . Subject Message subject. Text Body of the message. Additional Parameters Additional optional parameters. For more information on these fields, see: Mailgun API Reference: Messaging > Sending. Action - Add Member to List Parameters Parameter Description List Address Address of your list. Example: LIST@YOUR_DOMAIN_NAME.COM For more information on this endpoint, see: Mailgun API Reference: Mailing Lists. Member Address Valid email address of the member being added. Name Optional member name. Subscribed Values are Yes or No. The default value is Yes. Yes to add as subscribed. No to add as unsubscribed. Upsert Values are Yes or No. The default value is No. Yes to update member if present. No to raise error in case of a duplicate member. Additional Parameters Optional additional parameters. Example: gender, age. Action - Update Member in List Parameters Parameter Description List Address Address of your list. Example: LIST@YOUR_DOMAIN_NAME.COM For more information on this endpoint, see see: Mailgun API Reference: Mailing Lists. Member Address Valid email address of member. Name Optional member name. Subscribed Values are Yes or No. Yes for subscribed. No for unsubscribed. Additional Parameters Optional additional parameters. Example: gender, age. ... View more

Learn about the new features and fixes released in July 2021. Tags New/Cool Stuff Added the adobe_org_id mapping field to the Adobe Analytics AppMeasurement for JS tag to better support custom value mappings. (Learn more) Updated the Adobe Target tag to support Version 2.5.0. (Learn more) Added section default value for the CIM gemiusPrism tag. (Learn more) Updated the Floodlight ( gtag.js ) to add the ability to send multiple requests to the same activities and groups using an array or csv file. (Learn more) Added campaign parameter support for the Google Analytics (GA4) tag. (Learn more) Updated the Google Analytics 4 (GA4) tag to allow custom event mapping. (Learn more) Introduced the beta version of the Google Consent Mode tag used to integrate with Tealium Consent Manager. (Learn more) Updated the Lytics tag to support Lytics Version 3 Javascript tag. (Learn more) Added new eCommerce mapping variables and support for utag.sync.js version to the Oracle CX tag to support Oracle Infinity Analytics. (Learn more) Added new parameters for the Oracle CX tag. (Learn more) Fixes Updated the Google Analytics (GA4) tag to correctly update base_url for renamed data layer objects. Corrected issue with the Adobe Analytics AppMeasurement for JS tag where custom value mappings did not work for adobe_org_id , combineLinkVar , linkTrackVars / Events , and linkType / Name . Corrected mapping issues with the Adjust Mobile Remote Command tag. Connectors New/Cool Stuff Added the Send Profile Event to the beta (experiment) version of the Adobe Campaign Standard connector. (Learn more) Added Transactional API Endpoint event to the beta (experiment) version of the Adobe Campaign Standard connector. (Learn more) Updated the Google Ads Conversions connector to include batch support. (Learn more) Added support for Version 8 of the Google Ads API used with the Google Ads Conversions Connector to v8. (Learn more) Fixes Updated the Responsys Marketing Cloud connector to correctly display Merge Profile Extension Recipients action errors. iQ Tag Management Fixes Corrected an issue where deactivating or deleting a load rule could potentially disable Consent Manager, including instances where the rule was not linked to Consent Manager. Customer Data Hub New/Cool Stuff Introduced the Tealium Functions feature for EventStream API Hub and AudienceStream CDP to provide a quick and intuitive way to customize Tealium for your business needs with just a few lines of JavaScript code. (Learn more) Updated the Visitor Deletion Tool (Early Access Program) feature to change results file link handling response from the server. (Learn more) Fixes Corrected issue where users were unable to select string type event attributes when enriching an AudienceStream attribute using the Set Date enrichment option. Corrected the following Visitor Delete Tool (Early Access Program) issues: Added text missing from File Service column in Jobs Listing. Corrected blank slide-out panel that appeared after enabling or disabling a job. Corrected issue where required messaging did not display when attempting to save with the File Prefix field left empty on the Job Edit screen. Corrected display issues experienced when expanding the information accordion view. Installations Mobile Android Added untilRestart volatile data support for Kotlin. Corrected Kotlin issue that caused the Location module to crash on startup when the device was offline. Corrected issue where launch events were not immediately sent for the Android Lifecycle launch when using ReactNative for Kotlin 2.x. iOS Corrected issue in Swift to ensure that shouldMigratePersistentData defaults to false instead of true. Corrected issue with Swift that caused persistent data to be deleted during operating system upgrades. Removed UIWebView cookie migration code for Swift. Corrected CoreTelephony log issue for Swift. Added the WKWebView processPool fix to the ObjC library. ... View more

This article describes how to set up the Lytics tag in your Tealium iQ Tag Management account. In this article: Tag Tips Use mapping to override the standard config values. Tag Configuration First, go to the tag marketplace and add the Lytics tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Collection ID: Your Lytics supplied Collection ID (cid/account id) Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Standard Variable Description cid Collection ID ... View more

This article describes how to set up the Oracle CX Tag tag in your Tealium iQ Tag Management account. In this article: Tag Tips Supports these E-Commerce extension parameters: Order ID ( _corder ) List of Product IDs ( _cprod ) List of Product SKUs ( _csku ) List of Product Quantities ( _cquan ) Order Total ( _ctotal ) Sub Total ( _csubtotal ) Shipping Amount ( _cship ) Tax Amount ( _ctax ) Currency ( _ccurrency ) Promo Code ( _cpromo ) List of Names ( _cprodname ) List of Brands ( _cbrand ) List of Categories ( _ccat ) List of Categories 2 ( _ccat2 ) List of Prices ( _cprice ) List of Discounts ( _cpdisc ) Tag Configuration First, go to the tag marketplace and add the Oracle CX Tag tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Account ID Your Oracle Infinity Account ID. Tag ID Your Oracle Infinity Tag ID. Context Optional The context for your Oracle Infinity Tag. Example: analytics:dev 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_guid Account ID tag_id Tag ID context Context Click Tracking Configuration Variable Description successCallback Success Callback Function failCallback Fail Callback Function mutation Mutation Function wt.dl Event ID Commerce Variable Description wt.tx_i Invoice Number wt.tx_id Invoice Date wt.tx_it Invoice Time wt.mc_id Campaign ID wt.mc_ev Campaign Event wt.conv Conversion Nam wt.pn_sku Product SKU wt.pn_id Product Identifier wt.pn_fa Product Family wt.pn_gr Product Group wt.pn_sc Product Subgroup wt.pn_ma Product Manufacturer wt.pn_su Product Supplier wt.product_coupon Coupon Code wt.product_name Product Names wt.pn_gr Product Group wt.pn_sc Product Sub Group wt.product_price Product Price wt.product_discount Product Unit Discount wt.cart_total Cart Total wt.cart_subtotal Cart Subtotal wt.cart_shipping Cart Shipping wt.cart_tax Cart Tax wt.currency Currency wt.si_cs Conversion Step wt.si_n Scenario Name wt.si_p Scenario Step Name wt.si_x Scenario Step Number wt.tx_cartid Cart ID Overrides _corder . wt.tx_s Transaction Subtotal wt.tx_u Units wt.tx_e Transaction Event Type Transaction Event Type Variable Description a Cart Addition p Purchase r Cart Removal v Product View Custom Custom Content Variable Description wt.cg_n Content Group Name wt.cg_s Content Subgroup Name wt.ti Page Title page-uri Page URI wt.es Page URL domain Domain wt.oss On-site Search Phrase wt.oss_r On-site Search Success Mobile Web and App Variable Description wt.a_ac App Ad Click wt.a_ai App Ad Impression wt.a_an App Ad Name wt.a_pub App Publisher wt.ct Connection Type wt.g_co Country of Origin wt.dm Device Model wt.ets Event Timestamp wt.gc Geolocation Coordinates wt.sys Mobile App Event Type wt.a_nm Mobile App Name wt.av Mobile App Version wt.a_dc Mobile Carrier wt.sdk_v Mobile SDK Build Traffic Sources Variable Description referrer Referrer referrer-domain Referring Domain referrer-path Referring URI ... View more

This article describes how to set up the Reddit Pixel tag in your Tealium iQ Tag Management account. In this article: Tag Tips Use mapping to override the standard configuration values and trigger events. Purchase event fires when Order ID is set. Tag Configuration First, go to the tag marketplace and add the Reddit Pixel tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Account ID Your Reddit Account ID. Send Page Visit By default, Page Visit events are automatically recorded each page on your site. If you do not want the snippet to send a Page Visit event to the Reddit Pixel, set the this option to false. 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 String Account ID send_page_visit Boolean Send Page Visit Events Variable Description PageVisit Page Visit Enter the value of the mapped variable needed to trigger the selected event. ViewContent View Content Enter the value of the mapped variable needed to trigger the selected event. Search Search Enter the value of the mapped variable needed to trigger the selected event. AddToCart Add to cart Enter the value of the mapped variable needed to trigger the selected event. AddToWishlist Add to Wish List Enter the value of the mapped variable needed to trigger the selected event. Purchase Purchase Enter the value of the mapped variable needed to trigger the selected event. Lead Lead Enter the value of the mapped variable needed to trigger the selected event. SignUp SignUp Enter the value of the mapped variable needed to trigger the selected event. ... View more

Learn about the new features and fixes released in June 2021. Tags New/Cool Stuff New marketplace tag: Quantcast Cookie Matching Service (Learn more) Updated the Google Ads Conversion Tracking and Remarketing (gtag.js) tag to include custom events and added mapping properties to specific events. (Learn more) Updated the CIM gemiusPrism tag to include section mapping. (Learn more) Updated the PerimeterX Bot Defender tag branding and expanded vendor description. (Learn more) Updated the Yahoo Dot (Verizon) tag to support multiple Pixel IDs. (Learn more) Fixes Updated the Adlucent tag to remove TAX and SHIPPING from mapping and descriptions. (Learn more) The previously unavailable Kayak tag is now updated and available in the tags marketplace. (Learn more) Updated the Adobe Analytics tag to set s.cookieDomainPeriods to ensure that the correct cookie domain for plugins is received. (Learn more) Updated the Commission Junction (CJ) Global tag to include static variables pointOfSale=web and trackingSource=Tealium for all queries. (Learn more) Updated the Criteo OneTag to correctly set the setCustomerId field. (Learn more) Corrected issue with the Bing tag where event label was not populated and corrected the variable reference for mapping event_label . (Learn more) Corrected issues with custom even mapping for the Google Analytics 4 (GA4) tag. (Learn more) Corrected regex issues with the Google Analytics 4 (GA4) tag where the view_item_list event only returned a single item. (Learn more) Connectors New/Cool Stuff New marketplace connector: Snapchat Conversions (Learn more) New marketplace connector: Kayak Conversion Tracking (Learn more) New marketplace connector: Oracle Infinity Analytics (Learn more) Updated the Twitter Ads connector API version from Version 8 to Version 9 and updated the name of the connector from Twitter Tailored Audiences to Twitter Custom Audiences. (Learn more) Updated the Facebook Conversions connector parameters to include validation to the client IP address and client user agent. (Learn more) Updated the Tealium approval email address for the Snapchat Audience Match connector. (Learn more) Fixes Fixed an issue with the Webhook connector when using the Print Attribute Names setting that caused visitor ID attributes to be printed as their IDs instead of as their names. iQ Tag Management New/Cool Stuff Added a new extension scope for use with the JavaScript Code or Advanced JavaScript Code extensions named utag Sync that associates an extension to the utag.sync.js file. (Learn more) When using the Usercentrics extension to import new Data Processing Services, changed and removed services are now highlighted in the interface before the changes are introduced. (Learn more) Fixes Corrected an issue causing an unnecessary error message to display when switching profiles. Updated the user interface to correct an issue where overly long version names prevented the Save/Publish button from displaying properly. Corrected an issue where concurrent users with proper permissions were to not be able to merge versions in some cases. Updated the Edit Tag Template screen to not display the template drop-down list when viewing directly from the tag view. Customer Data Hub Fixes Disabled the Load Profile button in the profile switcher modal in cases where the Profiles field is blank. Corrected the scope selection drop-down list displayed in the AudienceStream Add Attribute screen. Installations Mobile Android Fixed an issue with the Location module for Kotlin that caused the module to crash on startup when the device was offline. Corrected React Native issue with Kotlin 2.x where launch events were not immediately sent when the application launched, but in the next lifecycle event. iOS Removed the UIWebView cookie migration code and the cookie migration listener. Corrected issue with Swift that caused persistent data (app cache) to be deleted after an OS upgrade. Corrected a CoreTelephony log issue with Swift. Updated iOS deep linking and QR Trace to support SceneDelegate by using the UISceneWillConnectNotification to initiate the "swizzle" proxy. Added the WKWebView processPool fix to the Objective C library. ... View more

This article describes how to set up the Adlucent tag in your Tealium iQ Tag Management account. In this article: Tag Tips Use the E-Commerce extension to set the following parameters: Order ID Customer ID List of SKUs List of Quantities List of Prices List of Categories Use mapping to: Dynamically override the standard config values Dynamically override the E-Commerce extension values Set a value for Customer Type Tag Configuration First, go to the tag marketplace and add the Adlucent tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Retailer ID: Your Adlucent retailer ID. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Standard Variable Description Retailer ID (retailer) Customer ID (customerID) Customer Type (customerType) Order ID (orderKey) List of SKUs (sku) [Array] List of Quantities (qty) [Array] List of Prices (price) [Array] List of Categories (category) [Array] ... View more

This article describes how to set up the Yahoo Dot tag in your Tealium iQ Tag Management account. In this article: Tag Tips Use mapping to: Dynamically override the standard config values Dynamically override the E-Commerce extension values Set values for these Standard custom event parameters: Event Category ( ec ) Event Action ( ea ) Event Label ( el ) Event Value ( ev ) Goal Value ( gv ) If you are using the e-commerce extension, Goal Value ( gv ) will automatically be populated with the E-Commerce extension value for Order Subtotal. Map a value directly to Goal Value to override the E-Commerce extension value. Tag Configuration First, go to the tag marketplace and add the Yahoo Dot tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Project ID The projectId value from your Yahoo Dot code snippet. Pixel ID The pixelId value from your Yahoo Dot code snippet. You may enter multiple Pixel IDs in a comma-separated list. 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: Yahoo Dot Variable Description Project ID (projectId) Pixel ID (pixelId) [String or Array] User Email (userEmail) User Hashed Email (userHashedEmail) Custom Event Parameters Variable Description Event Category (ec) [String or Array] Event Action (ea) [String or Array] Event Label (el) [String or Array] Event Value (ev) [String or Array] Goal Value (gv) (Overrides E-Commerce Order Subtotal) [Number] Timestamp (timestamp) Advertiser ID (advertiser_id) E-Commerce Variable Description Sub Total (order_subtotal) (Overrides _csubtotal) List of Product IDs (product_id) (Overrides _cprod) [Array] ... View more

This article describes how to set up the PerimeterX Bot Defender tag in your Tealium iQ Tag Management account. In this article: Tag Tips Use mapping to dynamically override standard config values. Tag Configuration First, go to the tag marketplace and add the PerimeterX Bot Defender tag (Learn more about how to add a tag). After adding the tag, configure the following settings: AppID: Your Unique Application Identifier 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 appId AppID _pxParam1 Custom Param 1 _pxParam2 Custom Param 2 _pxParam3 Custom Param 3 _pxParam4 Custom Param 4 ... View more

This article describes how to set up the CIM gemiusPrism tag in your Tealium iQ Tag Management account. In this article: Tag Tips lan language of the page must be in all capitals. Pre-defined values are NL/FR/EN/GE/LU//OTHER key free keyword to describe the content of the site subs subsection of the web site, not official CIM section free free field Example: Use to to add content type Each parameter name and parameter value can be together up to 50 characters long, including the equal sign (=). The total number of characters in parameter names and their values may be up to 200. The vertical bar (|) and the equal sign (=) symbols are not allowed in parameters. The slash (/) character can be used as a separator between levels of the structure and therefore cannot be used in the name of one node of the tree Letters with accent marks (á, ą, â, ă, ä, etc.) are not allowed and must be changed to Latin letters The following characters are not allowed in the values of parameters 'lan' and 'key' { } [ ] ()" ' ~ ` ! @ # $ % ^ & * ? ; , : / | = Tag Configuration First, go to the tag marketplace and add the CIM gemiusPrism tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Identifier Supplied by CIM gemiusPrism Language The language of the page. Example: NL. You can dynamically override this value via mapping. 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 identifier Account Identifier lanuage Language key Keyword subs Subsection free Free field section Section ... View more

This article describes how to set up the KAYAK tag in your Tealium iQ Tag Management account. In this article: Tag Tips Use event mappings to configure when confirmation and cancellation pixels are fired. The Commission Currency value will default to the e-commerce Currency value if one is not provided. Tag Configuration First, go to the tag marketplace and add the KAYAK tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Partner Code Supplied by KAYAK, this is the internal KAYAK code. Click ID Query Parameter Name Name of the query parameter that will be used to pass the click id in the tracking url. 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 Configurations Variable Description Partner Code (partner_code) Booked On Date (bookedon) Kayak Commission Amount (kayakcommission) Commission Currency (commissioncurrency) Booking Type (bookingtype) Kayak Commission Percentage (commissionpercentage) Custom Field 1 (tag1) Custom Field 2 (tag2) E-Commerce Variable Description Order ID/Booking ID (order_id) (Overrides _corder) Order Total (order_total) (Overrides _ctotal) Currency (order_currency) (Overrides _ccurrency) Hotel Variable Description Booking Check In Date (checkin) Booking Check Out Date (checkout) Booked Property ID (hid) Number of Travelers (travelers) Number of Rooms (rooms) Flight Variable Description Itinerary Description (itin) Origin Airport Code (origin) Destination Airport Code (destination) Fare Class (fareClass) Cabin Type (cabinType) Car Variable Description Pick Up Date (pickup) Drop Off Date (dropoff) Pick Up Location ID (pickupid) Drop Off Location ID (dropoffid) Car Agency ID (agency) Events Variable Description Confirmation Confirmation Cancellation Cancellation ... View more

Learn about the new features and fixes released in May 2021. Tags New/Cool Stuff Updated the Contentsquare UX Analytics tag to add currency support for e-commerce transactions. (Learn more) Updated the Adobe Target tag to add support for Adobe Target version 2.4.1. (Learn more) Fixes Updated the AT Internet SmartTag template to remove incorrect default configuration placeholders. Connectors New/Cool Stuff New marketplace connector: Impact Page Loads (Learn more) New marketplace connector: Quantcast Audiences (Learn more) Updated the Amplitude connector by adding built-in logic to skip empty values. (Learn more) Updated Facebook Conversions and Offline Conversions connectors to improve ID validation and ensure mapped data is a valid number and not a string. Fixes Updated the Salesforce and Salesforce Standard Objects connectors to correctly produce unique keys for each customer and avoid key collisions. Updated the Amazon EventBridge connector to include missing session token and corrected an error that occurred when an event source was configured manually. Corrected an issue causing inaccurate error reporting related to email hashing for the Google Enhanced Conversions connector. iQ Tag Management New/Cool Stuff The Site Scan service is now deprecated and no longer available from Tealium Tools. Increased the size of the code editor window for the JavaScipt Code (Basic) extension and added full screen pop-out capabilities. Fixes Corrected an issue where the code contents of inherited JavaScript extensions did not display in child profiles. Corrected an issue in the Consent Manager user interface where users were not able to scroll to select the consent language. Corrected an issue where an incorrect version of the cmShowpreferences template displayed in the Template Status Checker. Customer Data Hub Fixes Corrected issue so that using regex inside of rules no longer converts to invalid regex, which previously caused the profile to not save. Installations Mobile Remote Commands Corrected issue with the Android Firebase Remote Command implementation to correctly report events when either no event or firebase_event_params exists. Android (Kotlin) Corrected issue with Kotlin HTTP that caused requests to not send if no response listener is passed. React Native Updated the Braze Remote Command tag to correct issue with ReactNative importing the com.tealium.remotecommands:braze:1.0.0 artifact. iOS Swift Corrected issue where the decline_consent event did not correctly send for .gdpr (config.consentPolicy = .gdpr) . (Learn more) Updated Firebase to correctly map custom parameters for events. Corrected consent policy issue where the key policy was inadvertently changed to consent_policy , thus invalidating the event specifications for consent. ... View more

We have expanded and simplified how you manage code in the utag.sync.js file. A new extension scope named utag Sync associates an extension to the utag.sync.js file. The utag Sync scope is available for the JavaScript Code or Advanced JavaScript Code extensions. What's New Previously, the utag.sync.js file could only be updated by editing the tag template. This method was inflexible, prone to error, and limited to users with the permission to manage templates. The new scope allows you to manage the contents of the utag.sync.js file with all the conveniences of extensions. How It Works Use the utag Sync scope to publish code from a JavaScript Code extension into utag.sync.js instead of editing the tag template. Add a JavaScript Code or Advanced JavaScript Code extension and set the scope to utag Sync. When the profile is published, the placeholder ##UTSYNC## in utag.sync.js is replaced by the code from the scoped extensions. Benefits Convenience of Extensions Enjoy the convenience of extensions while managing utag.sync.js . Enable or disable the code in utag.sync.js by turning on or off the associated extensions and easily publish utag.sync.js to different environments using publish locations. Support for Inheritance and Libraries Create and manage shared utag Sync extensions with libraries, which will be inherited to child profiles. This allows you to easily manage common sync code across profiles. Support for Publishing Approval and Environment Lock 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. GitHub Integration Increase efficiency and code quality by using the GitHub integration with the Advanced JavaScript Code extension to publish code from an external repository into the utag.sync.js file. How do I enable the feature? To enable this feature, toggle on the Generate utag.sync.js File option in your Publish Configuration settings, as follows: 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. Additional Information Using the utag.sync.js Script Advanced JavaScript Code Extension Extensions JavaScript Code Extension (Basic) Load Order Manager Order of Operations ... View more

Learn about the new features and fixes released in April 2021. Tags New/Cool Stuff New marketplace tag: Adjust Mobile Remote Command (Learn more) Updated the Google Analytics (gtag.js) tag to include the send_to parameter on page_view events. (Learn more) Updated the Rakuten Marketing from "Rakuten Marketing" to "Rakuten Advertising", added the nonCentCurrencies parameter, and updated endpoint configurations. (Learn more) Connectors New/Cool Stuff Updated Adobe Analytics Connector to support event serialization. (Learn more) Improved error deserialization for Google Ads Conversion connector to handle 429 HTTP responses. (Learn more) Deprecated current Criteo Audience Match connector and introduced new Criteo connector. (Learn more) Fixes Updated logic in Google Floodlight connector to correctly account for partially successful API responses. iQ Tag Management Fixes Corrected an issue causing tags to display incorrect history data. Corrected an issue causing the inability to scroll load rules. Corrected an issue with extensions using the Preloader scope that resulted in utag.js failure. Corrected issue causing DOM Ready extensions to not display properly in Load Order Manager. Customer Data Hub Fixes Corrected issue in AudienceStream > Audience Discovery where users could not access the Audiences drop-down list. Installations Mobile Remote Commands Applied HTTP remote command updates to format the request body based on the content-type header. Android (Java) Updated the Android SDK to allow suppression of remote_api events. Android (Kotlin) Updated the Kotlin SDK to allow for custom consent policies. Updated the device collector for Kotlin to include device_language . Added os_name to Kotlin for consistency with Swift. Added module_names , enabled_modules , and enabled_modules_versions to Kotlin events to improve the debugging experience. Added the tealium_profile override setting to the CollectDispatcher for Kotlin. Updated the Kotlin CollectDispatcher to correctly encode the receipt of collections and non-standard characters in EventStream. Updated Kotlin to correctly include REQUEST_UUID for each track in the event request payload. Corrected the Kotlin library_version key to be the tealium_library_version key. Flutter Updated the Tealium for Flutter API with the ability to use the Swift library. Updated the Tealium for Flutter API with the ability to use the Kotlin library. React Native Added a Remote Command adapter to enable any remote command to be added to the React Native plug-in. Added "on-ready" callback support for Tealium initialization using React Native. iOS Swift Updated the Swift SDK to allow for custom consent policies. Updated the Swift crash reporter module to correctly include crash_count for the total number of crashes. To successfully set and sync cookies, added the ability to allow a process pool for multiple webviews to be set up each time WKWebview is instantiated. ... View more

Learn about the new features and fixes released in March 2021. Tags New/Cool Stuff The Google Analytics 4 (GA4) tag was moved out of beta. (Learn more) New marketplace tag: Amobee Cookie Matching Service (Learn more) Updated the Firebase Mobile Remote Command tag to the latest SDK, including eCommerce function updates. (Learn more) The legacy version of the Facebook pixel tag is now deprecated and no longer available from the tag marketplace. (Learn more) Updated the Google Analytics (gtag.js ) tag to add support for List Name as an array type. (Learn more) Fixes Updated tag tips for the Google DoubleClick and AdWords Cookie Matching service tag to accurately reflect the name of the google_gid cookie value variable sent to AudienceStream. (Learn more) Updated the Adobe Analytics AppMeasurement for JS tag to correctly map linkTrackVars and linkTrackEvents. (Learn more) Updated the Google Analytics (gtag.js) tag to remove unsupported mapping for   config.linker.domains and config.linker.accept_incoming . (Learn more) Connectors New/Cool Stuff The Google Ads Enhanced Conversions connector is now available as a beta experiment. (Learn more) The Xandr Real Time Segments (Tealium-Provided Credentials) connector is now available as a beta experiment. (Learn more) Updated the Google Ads Customer Match connector to allow multiple mappings for the UserIdentifier parameter. (Learn more) Updated the Criteo connector to support a mapping for IP address. (Learn more) The Impact Radius connector was renamed to Impact Conversions. (Learn more) Updated the End-User License Agreement (EULA) for all Google Customer Match connectors. Fixes Updated the Criteo connector to validate that the audienceId parameter is entered as a number. (Learn more) Updated the Adobe Campaign Classic Batch connector to correctly flag error identifiers. (Learn more) The beta experiment version of the Xandr Real Time Segments (Customer-Provided Credentials) connector is no longer available. Corrected issue in connector workflow causing text the inability to edit selected text. iQ Tag Management Fixes Updated the Template Status Checker to correctly look for the new version of the mobile.html template and corrected the ability to open the template. Updated the Template Status Checker to include Consent Manager templates in the summary view and total template count. Corrected issue causing merge to not display the extensions, variables, and load rules as having changed when included in the merge but not specifically changed. Corrected an issue in Web Companion for private client environments where the title for tags and extensions incorrectly displays as "No Title". Corrected a UTF-8 display issue preventing Web Companion from loading properly. Corrected an issue causing extensions with the Run Once option not to display in a filtered list. Corrected a display issue that occurred on user account screens when enabling MFA for an account. Corrected an issue in the code editor that caused syntax errors to display when editing templates with placeholder code. Customer Data Hub New/Cool Stuff New data source: Adobe Experience Platform Launch. (Learn more) The HTTP API - Flattened data source was renamed to HTTP API - Advanced. (Learn more) Added Trimou template functions substring , substringAfter , substringAfterLast , substingBefore , substringBeforeLast , substringBetween . (Learn more) Installations Web Updated the Universal Tag (utag.js) to support secure cookies using a JavaSciript preloader extension. (Learn more) Mobile Updated NativeScript to support consent expiration (Learn more). Updated the media tracking modules for the Swift and Kotlin libraries to support background playback. Android Updated to support autotracking of push notifications for Kotlin. Updated for Kotlin to move _http  command activity to a background thread. Corrected issue with ReactNative for Android for the NoSuchKeyExpection on versions v.062 and below. Corrected issue to correctly start offline tracking when the mobile application is started offline. Swift Updated to match Kotlin functionality to use tealium_event_type=view and tealium_event_type=event instead of call_type=view . Updated the ConsentPolicy protocol to public to support the creation of custom consent policies. Corrected issue to automatically reset lifecycle crash key on the launch event. Corrected issue with crash reporter module using Carthage. ... View more

This article describes how to set up the Amobee Cookie Matching Service tag in your Tealium iQ Tag Management account. In this article: Tag Tips Sends the following server-side attribute back to Tealium:   amobee_id If left blank, the Tealium account and profile names are automatically populated. Tag Configuration First, go to the tag marketplace and add the Amobee Cookie Matching Service tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Amobee Token (Your Amobee Token) Tealium Account: Tealium Profile 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 amobee_token Amobee token Your Amobee token, as provided by Amobee. tealium_account Tealium account name tealium_profile Tealium profile name ... View more

This article describes how to use the HTTP API - Advanced data source to create an HTTP endpoint to collect real-time event data with support for flattening complex objects. In this article: Table of Contents Placeholder How It Works A Webhook API sends outgoing requests to an endpoint that you specify. These requests inform Tealium EventStream and AudienceStream about customer activity from your external systems. When you add a webhook data source, a unique endpoint is generated. This endpoint is used to configure a webhook in your external system. Once configured, you can create subscriptions based on topics and receive related push notifications to automate use cases, stay informed, and increase productivity. The HTTP API - Advanced data source is a generic data source that can conditionally parse incoming request bodies. This data source offers an HTTP endpoint to collect real-time event data with support for flattening complex objects. The endpoint is flexible and can be implemented as a tracking pixel in a web page or as a JSON API in your custom application. This data source is similar to the HTTP API data source, but with additional support for complex objects. Events sent using HTTP POST with a complex JSON object will be flattened as follows: Event keys are created by lowercasing and connecting key paths to a prefix. For example, a value of true located at alpha.beta displays as "alpha_beta":true . Numbers, Booleans, and strings inside of an array are preserved. Objects and arrays inside of an array are stringified. Use this data source type when you need to send data in real time and do not have the ability to modify the request to meet format requirements for the standard Tealium Collect endpoint. Requirements Tealium EventStream or Tealium AudienceStream Supported Parameters The following default parameters are supported in each request: Parameter Description tealium_event Optional The name of the event. tealium_trace_id Optional For use with Trace. tealium_visitor_id Optional* For use with AudienceStream If batched events are being used and there is no tealium_visitor_id present in the event, all events in the same batch generate the same tealium_visitor_id . This implies that the events will be tied together in the same visitor profile, regardless of visitor stitching. Setup The following sections provide guidance on how to add the HTTP API - Advanced data source and create a webhook. Add the Data Source The HTTP API - Advanced data source supports both the GET and POST methods using the following endpoint: https://collect.tealiumiq.com/integration/event/ACCOUNT/PROFILE/DATA_SOURCE_KEY Add the HTTP API - Advanced data source before proceeding, then copy the generated endpoint for use in an external system. Related: How to Add a Data Source Examples The following sections provide examples of input code and the resulting (flattened) output for complex objects. Complex Object Before Flattening { "boolean": true, "number": 12.34, "string": "value", "array_of_strings": ["first", "second"], "array_of_arrays": [ [1, 2], [3, 4] ], "array_of_objects": [{ "ordinal": "first" }, { "ordinal": "second" }], "object": { "child_boolean": true, "child_number": 12.34, "child_string": "value", "child_array_of_strings": ["first", "second"], "child_array_of_arrays": [ [1, 2], [3, 4] ], "child_object": { "gchild_boolean": true, "gchild_number": 12.34, "gchild_string": "value", "gchild_array_of_strings": ["first", "second"], "gchild_array_of_arrays": [ [1, 2], [3, 4] ] } } } After Flattening { "boolean": true, "number": 12.34, "string": "value", "array_of_strings": ["first", "second"], "array_of_arrays": ["[1,2]", "[3,4]"], "array_of_objects": ["{\"ordinal\":\"first\"}", "{\"ordinal\":\"second\"}"], "object_child_boolean": true, "object_child_number": 12.34, "object_child_string": "value", "object_child_array_of_strings": ["first", "second"], "object_child_array_of_arrays": ["[1,2]", "[3,4]"], "object_child_object_gchild_boolean": true, "object_child_object_gchild_number": 12.34, "object_child_object_gchild_string": "value", "object_child_object_gchild_array_of_strings": ["first", "second"], "object_child_object_gchild_array_of_arrays": ["[1,2]", "[3,4]"] } JSON Object Before Flattening A JSON object is treated as a single event by default. { "events": [ { "id": "1", "name": "Event A" }, { "id": "2", "name": "Event B" }, { "id": "3", "name": "Event C" } ] } After Flattening Unless the parser is overwritten by custom logic used to parse out batched events, the JSON object is transformed into a single event with stringified JSON array values. { "events": [ "{\"id\":\"1\",\"name\":\"Event A\"}", "{\"id\":\"2\",\"name\":\"Event B\"}", "{\"id\":\"3\",\"name\":\"Event C\"}" ] } ... View more

This article describes how to manage server-side users and permission roles for the Tealium Customer Data Hub. This article covers the following topics: How It Works Server-side user permissions provide control over the degree of access users have for each profile by creating a separation of access between the Tealium client-side interface and the server-side interface. From the server-side Manage Users screen, you can do the following: Grant Access to New Users New users are added to accounts in Tealium iQ Tag Management. After new users are added, the new users display in the server-side user permissions list where server-side access can be granted, by profile. To add new users to an account, you must have the Manager Users permission. To assign roles on the server-side, you you must have the Manage Account permission. Specify Access Account administrators can grant access to users only for the areas that they intend to work on as well as grant Save and Publish permissions for client-side products for a profile that do not carry over to server-side products for that profile. Set Permissions for Future Profiles For active profiles, you can set the permissions for future profiles, which allows user admins to define a profile-level permission role for users of new profiles created for an account. Add and Edit Bulk Users You can add and edit users in bulk (up to 25 users at a time) and search user profiles and filter users by permission type. Admin Users Admins of the server-side interface are the only users that have the ability to change the permissions of server-side users. None of the server-side permission roles grant this ability. To be an admin on the server-side, you must have the Manage Account permission in the client-side interface. Only the Manage Users permission on the client-side grants the ability to add users to the account. To learn more about managing user permission in Tealium iQ Tag Management, see Managing User Permissions in iQ Tag Management. Server-Side Permission Roles Server-side access is controlled using predefined permission roles. For each profile in the account, users are assigned a permission role to determine their access level. The following table describes the four available server-side permission roles: PERMISSION ROLE DESCRIPTION No Access (default) This is the default role for all users other than account administrators. The No Access permission role does not grant any access to the server-side profile. If the user attempts to access the server-side, their profile is blocked and an "Access Denied" message displays. Reader The Reader permission grants read-only access to the server-side profile. A user in this role can browse the profile configuration, but Save/Publish is disabled. Users with this role cannot save any changes. Editor The Editor permission grants edit and save access to the server-side profile. With this role, you can save but not publish. Users with this role can also access and edit settings from the Profile Admin > Settings menu. Publisher (Admin default) This is the default role for account administrators. The Publisher permission grants the same access as the Editor role, with the addition of the ability to save and publish the profile. Profile access between the server-side and client-side product is mutually exclusive. For example, you can grant Save and Publish permissions for client-side products without impacting server-side product permissions for a given profile. In addition, if you remove or change user access to a profile on the client-side, it is not removed or changed on the server-side. Add a Server-Side Only User To give a user access to server-side, you must first add them in the client-side interface. In the client-side interface you must have the Manage Users permission to add users to your account and the Manage Account permission to manage permissions in the server-side interface. To add a user with only permission to a server-side profile, follow these steps: In the client-side interface, add the user, but do not select any client-side permissions. The user must verify their email address before you can continue, at which point the user has read-only access to the client-side interface and appears in the Manage Users list in the server-side interface. In the server-side interface, go to Manage Users and assign permission roles to grant the user access to a server-side profile, then click Next. Save your changes. Return to the client-side interface. On the User Menu, select Manage Users. In the   User Manager   dialog, select the user you want to remove. Click More and select   Remove User. In the   Remove User   dialog, confirm the user to be removed, then click   Remove User. The user no longer has access to the client-side profile, but retains access to the server-side profile. Edit Server-Side User Permissions To edit server-side user permissions, you must have the Manage Account permission, which is assigned from the client-side interface. Use the following steps to view and edit server-side permissions for a user: Log into the server-side area of the Customer Data Hub. In the user admin menu, select Manage Users. A list of all server-side users displays, including the user's name, email address, and a timestamp for the last login. Click a user to display the permission details. To grant access to a profile, select a Permission Role. Repeat Step 3 through Step 5 for each user you want to edit. If no changes are needed, click X to close the user details and return to the user list. You will be prompted to confirm your intention to disregard changes if you have made adjustments. Click Save to keep your changes or Cancel to discard the changes. Your changes are saved without the need to publish. Set Permissions for Future Profiles Use the following steps to set permissions for future profiles, which allows user admins to define a profile-level permission role for users of new profiles created for an account. Log into the server-side area of the Customer Data Hub. On the user admin menu, select Manage Users. In the Set permissions for future profiles list, select a role to be assigned to users of new profiles created for an account. Click Save to keep your changes or Cancel to discard the changes. Your changes are saved without the need to publish. Edit User Permission Roles in Bulk Use the following steps to edit the permission role for multiple users: On the user admin menu, select Manage Users. Select each user for which you want to change the permission role. Click Bulk Actions and select the permission to assign to the selected users. Click Apply, then click Save. You do not need to publish for your changes to persist. Frequently Asked Questions (FAQ) If a user is removed from the client-side profile, is the user also removed from the server-side profile? No. When a user exists in both client-side and server-side, removing the user from one does not impact the other. Can I grant a user access to a server-side profile without allowing access to a client-side profile? Yes. If a user already exists in the account and has been granted permission to a profile on the server-side, go to iQ Tag Management > Manage Users and remove that user from the client-side interface. For more information, see Add a Server-Side Only User. How does the "All current and future profiles" option impact server-side permissions? There is no impact to server-side users. All server-side users have the default permission role of No Access to all new server-side profiles. What happens if a user has access to only one profile on the server-side and no profile access on the client-side? If the user selects server-side at the login screen, they are automatically loaded into the account/profile accordingly. If the user attempts to log in to the client-side, a modal displays with a denied access message. Can a server-side admin change their own permissions for server-side profiles? Yes. A server-side admin user (granted by the Manage Account permission) can change permissions for all server-side users, including their own. Can a server-side admin update manage permissions for all server-side profiles? Yes. A server-side admin user's access is granted by the Manage Account permission, which is an account-level permission. Users with this permission level have access to the Manage Users screen in the server-side interface where they can manage user permissions for all profiles. How do the new server-side permissions affect the Omnichannel File Status API? Access control to the Omichannel File Status API will change upon final release of the server-side permissions feature. In addition to the standard requirement of needing an API key to authenticate with the API, users must have read access to the relevant Customer Data Hub account. Users using the v1 API only need read access to the Customer Data Hub account. Can a server-side admin add new users to an account? No. The Manage Account permission does not grant access to add new users or delete users from an account. While they can remove access to profiles, only users who have the Manage Users permission assigned in the iQ Tag Management workflow can invite a new user to an account or completely delete a user from an account. Does this feature change the way user management access is granted or controlled within TiQ? No. The Manage Users permission in iQ Tag Management remains the permission that grants a user access to add or remove users from a business account. Users with only the Manage Users permission do not have access to manage permissions on the server-side. Additional Resources Managing User Permissions in iQ Tag Management ... View more

Learn about the new features and fixes released in February 2021. Tags New/Cool Stuff Updated The Trade Desk Cookie Matching Service template to trigger only once per session by default. (Learn more) The Cookie Reports tag is now rebranded to Digital Control Room. (Learn more) Updated the createContexts function for the Snowplow tag to allow arrays of variables to be passed and support sending multiple contexts. (Learn more) Updated the Fullstory tag to support page events for the FS.setVars API. (Learn more) Updated mobile timestamp handling for the Adobe AppMeasurement tag, Versions 1.6.3 and later. (Learn more) Updated the Adobe Target tag to support Version 2.4. (Learn more) Updated the Adobe Experience Cloud ID Service API to support Version 5.2. (Learn more) Connectors New/Cool Stuff Added batching support for the Sailthru connector. (Learn more) Added new, required parameters for the Facebook Conversions connector. (Learn more) Upgraded the Twitter Ads API from from Version 7 to Version 8. Fixes Corrected issue in Facebook Conversions that caused the "Action Source" key in Event Data mapping to display in the wrong area. iQ Tag Management New/Cool Stuff New marketplace extension: Usercentrics CMP, V1. (Learn more) New marketplace extension: Usercentrics CMP, V2. (Learn more) Reintroduced the original JavaScript extension as the JavaScript Code Extension (Basic), which is now available in addition to the Advanced JavaScript extension. (Learn more) Fixes Corrected a cosmetic issue to ensure that single items do not scroll on a page when performing a Load Order Manager bulk move. Corrected an issue where child profiles were able to inherit an "add-once" extension from a parent library, which resulted in multiple extensions in the child profile. Corrected an issue where changing JavaScript Extension scopes from Tag Scoped to DOM Ready created a duplicate of the extension. Corrected an issue that occurred when importing variable bundles that created an additional e-commerce extension for the first time and did not map variables by default as expected. Corrected an issue in Consent Manager (Preferences) that caused omitted tags to fire twice for events with a UIDs array that occurred before a consent decision when the omitted tags were included in the UIDs array. Customer Data Hub Fixes Corrected an issue in the display of server-side versioning that caused the graph to not display property. Corrected issue causing the Data Source tab to not load if the profile contains a deprecated data source. Corrected issue causing problems when filtering Live Events using TraceId . Corrected the visit expiration estimate calculation for visitor profiles. Installations New/Cool Stuff Mobile Android Updated React Native to support the latest Kotlin libraries. Corrected issue causing offline tracking to not be dispatched when an application is started offline. Added public API method to reset and regenerate the Tealium Visitor ID. iOS Applied various enhancements to improve the user experience when working with the Tealium and Adobe visitor services. Swift Updated the Airship remote command integration to support JSON configuration files for Swift 2.0. Updated React Native to support the latest Kotlin libraries. Added NativeScript integration support for mobile SDKs. NativeScript Released Tealium for NativeScript, a set of cross-platform classes that interface with the native Tealium iOS SDKs. (Learn more) ... View more

This article describes how to set up the Digital Control Room (formerly Cookie Reports) tag in your Tealium iQ Tag Management account. In this article: Requirements The unique 8-digit code and language code for your site, supplied by Digital Control Room. Tag Tips Use mapping to override standard configuration values dynamically. Tag Configuration First, go to the tag marketplace and add the Digital Control Room (formerly Cookie Reports) tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Policy Code: //policy.cookiereports.com/XXXXXXXX_panel-en-gb.js Language Code: //policy.cookiereports.com/XXXXXXXX_panel-XX-XX.js 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 policy_code Policy Code language_code Language Code ... View more

The Tealium Usercentrics extension is used to enable third party CMP support. The extension simplifies the integration between Tag Management and Consent Management by allowing you to map data processing services to specific tags. Implementing this extension ensures the enforcement of end-user privacy preferences (consent) and that only consented services have the ability to transmit data to third parties. The implementation additionally ensures that only mapped tags can actively run on the website, which reduces the privacy risk exposure when changes are introduced. In this article: Table of Contents Placeholder How it Works The Tealium iQ Tag Management Usercentrics extension is used to ensure that your CMP policy is enforced at the source level, thus blocking or firing tags according to the user's consent preferences. Simple bookmarklet functionality is used to import the Data Processing Services JSON object text to a bookmark in your browser, which is then used to create a mapping table. To use, add the extension, enter the required information, and then use the mapping table to map consent preferences to your tags. Using this method significantly reduces implementation time and provides an extra layer of protection by preventing tags from firing until they are mapped to a CMP service. To prevent privacy risk exposure in instances where a tag is added without being mapped to a Usercentrics data processing service, only mapped tags fire once the extension is active. Prerequisites Knowledge of your Usercentrics Implementation You must have knowledge of the current or planned version of your Usercentrics implementation. To obtain all of the Data Processing Services in your Consent Management Platform (CMP), follow the instructions outlined in the Usercentrics Direct Implementation Guide. Use a Test Environment for your First Implementation Tealium recommends using a testing environment for your first implementation in order to fully access the CMP to create the mapping table within the extension. Using a testing environment ensures that no end-user data is processed prior to applying the extension in your development environment. Once you have completed the mapping of all data processing services to their corresponding tags, you can release it to production and Tealium iQ Tag Management will handle the enforcement of end-user privacy preferences (consent). Requirements Tealium Universal Tag (utag.js), Version 4.48. (Learn more) The Usercentrics CMP must load before Tealium iQ Tag Management. For this reason, you must do one of the following: Implement the Usercentrics Script (tag) directly within the HTML code of your website. - OR - Go to the Implement the Usercentrics Tag section below and follow the instructions to implement the tag within Tealium iQ Tag Management. Create a Data Processing Service for Tealium iQ Tag Management in your Usercentrics CMP setup. To learn more, see the Usercentrics documentation, Assign a data attribute. Know the name of your Data Processing Service before you begin, as it is required in the configuration steps. Implement the Usercentrics Tag Use the following steps to implement the Usercentrics tag within Tealium iQ Tag Management using the JavaScript Code extension: Go to Tealium iQ Tag Management > Extensions > Add Extension and select the JavaScript Code extension to add the script for Usercentrics V1 or Usercentrics V2. Add the JavaScript Code extension. If you have not previously used the JavaScript Code extension and need to learn how, see JavaScript Code Extension. Name the extension Usercentrics Tag, and set the scope to Pre Loader. Use the script from one of the following examples to create the extension: Usercentrics V1 Script: Supports Usercentrics CMP v1. (function(a, b, c, d) { b = document; c = 'script'; d = b.createElement(c); d.src="XXXXXXXXXXX"; // URL for Usercentrics CMP Version 1 Script. d.type = 'text/java' + c; d.async = true; d.id = 'XXXXXXXXX'; // Usercentrics Settings-ID a = b.getElementsByTagName(c)[0]; a.parentNode.insertBefore(d, a); } )(); Usercentrics V2 Script: Supports Usercentrics CMP V2 Browser SDK (TCF v2.0) (function(a, b, c, d) { b = document; c = 'script'; d = b.createElement(c); d.src="XXXXXXXXXXX"; // URL for Usercentrics CMP Version 2 Script. d.type = 'text/java' + c; d.async = true; d.id = 'usercentrics-cmp'; d.setAttribute('data-settings-id', "XXXXXXXXXXX"); // Usercentrics Settings-ID a = b.getElementsByTagName(c)[0]; a.parentNode.insertBefore(d, a); } )(); Save and publish the JavaScript Code extension to your environment. Create a Tealium Data Processing Service in your Usercentrics CMP You must create a Tealium Data Processing Service in your Usercentrics account to ensure that user consent preferences are enforced and third parties can only process data if allowed to do so. Use the following steps to create a Data Processing Service for Tealium iQ Tag Management in your Usercentrics CMP account: Go to your Usercentrics account . Select the most recent Data Processing template for Tealium iQ Tag Management. Mark the template as Required to ensure that it cannot be opted out. If you customized the Tealium iQ Tag Management service name, it will not be automatically detected by the CMP extension. In the Configuration section of this document, you will manually add the custom service name using the Service Name input field. Configure the Extension The steps in this section describe how to add the extension, install the bookmarklet, copy the data processing services, import the data processing services, map your tags to your data processing services, and apply conditions to define which domains can execute the extension. Add the Extension Use the following steps to add the Usercentrics extension: Go to iQ Tag Management > Extensions > Add Extension and click the Privacy tab. Select one of the Usercentrics extensions: Usercentrics V1 or Usercentrics V2. Select the version that corresponds with the version currently in use by your organization. In the Title field, enter a meaningful title to be used for this extension. Note that the Scope field cannot be modified. Enter the Settings-ID (Optional) Under Usercentrics Settings ID, in the Settings ID field, you can manually add your Usercentrics Settings_ID . This step may not be needed as the Usercentrics Settings-ID is automatically added to the extension while importing the data processing services. Under the Tealium iQ Service Name, in the Service Name field, enter the exact name that was given to the Tealium Data Processing Service within Usercentrics. Continue to the next section to install and use the Service Mapper bookmarklet. Install the Service Mapper Bookmarklet Use the following steps to install the bookmarklet: Click the Bookmarklet button. The Usercentrics Service Mapper Bookmarklet dialog displays. Click the Usercentrics Service Mapper link and drag and drop the bookmarklet onto the bookmark bar for your browser. The bookmarklet now displays in your browser bar. Click Close to dismiss the Usercentrics Service Mapper Bookmarklet window. Create a Mapping Table Use the following steps to copy and import your data processing services to create a mapping table: Open another browser tab and navigate to the Usercentrics test environment where your CMP is implemented and click the Usercentrics Service Mapper bookmarklet to launch. A pop-up window displays the text for your Data Processing Services JSON object. Copy the entire text from this window. Navigate back to the Usercentrics configuration dialog in iQ Tag Management and click the Import button. The Import Services dialog displays. Paste the copied JSON text into the window, as shown in the following example. Click Create Mapping Table. Your Usercentrics Settings ID and Tealium iQ Service Name are now automatically populated and the Service Mappings to your data processing services display in a mapping table. The mapping table must be updated each time a new tag is introduced or when your Data Processing Services with the Usercentrics configuration is changes, as described in the Update the Mapping Table section of this document. Map Data Processing Services to Tags Use the following steps to map your data processing services to tags: For each item in the mapping table, click the To UID field and use the prepopulated list to select the appropriate tag UID. You can map more than one tag to a data processing service. The bookmarklet automatically adds a list item for Tealium iQ Tag Management and Usercentrics in the mapping table. Use the trash can icon to delete the Tealium iQ Tag Management and Usercentrics services, as they are not used for consent enforcement. (Optional) Click Add Service to manually add additional services and map them accordingly. When complete, consent is immediately enforced without the necessity of a page reload, which guarantees that end-user privacy preferences are enforced before any data processing takes place. Save and Publish your changes. Update the Mapping Table The mapping table must be updated when a new tag is introduced or when your Data Processing Services within the Usercentrics setup changes. Use the bookmarklet functionality as described in the configuration steps and repeat the process to update. The Import function identifies Data Processing Services that already exist, including any that have been recently added and those that were previously deleted, as follows: If the Data Processing Service already exists, mapping is not impacted. If the Data Processing Service was deleted, it also deletes the mapping entry. If the Data Processing Service is newly introduced, a new line item is added to the mapping table and you must map at least one corresponding tag. Troubleshooting To view typical events, log messages, and error messages that may require attention, enable console logging. Use the following steps to enable console logging: Go to JavaScript (Web) Debugging and follow the steps to add the debugging cookie. After the debugging cookie is set, use the "/SENDING|\*\*\*\*/" filter to display only relevant entries. FAQ Can this extension be used in mobile installations? No. Mobile installations, such as iOS and Android, do not support the Tealium iQ Tag Management Usercentrics extension. Additional Information Usercentrics Direct Implementation Guide Usercentrics CMP, Version 1 Usercentrics Web CMP, Version 2 Tealium: Master List of Extensions Become a Tealium Techology Partner ... View more