Tealium Learning Center

This article provides a summary of event-level data points made available through EventStore. In this article: How it Works EventStore provides the most efficient way for collecting and exporting event-level data from your site. Here's how it works: The Tealium Collect tag captures the live event feed on your site and feeds the events to EventStore, which allows you to view and download the underlying data. The captured data is then compressed into a flattened JSON file and made available for download from Tealium’s Amazon S3 bucket. Each JSON object in the file may contain one or more rows of name-value pairs associated with the event. If you send your event data (event feeds), to another location, such as your S3 bucket or server, the feeds are not displayed in EventStore. After the S3 bucket reaches a size of 100 MB (uncompressed) or after 1 hour has elapsed, whichever comes first, the data is compressed and prepared for Redshift. The compressed data is then copied and imported into the Redshift database for your account. Data Captured by the Collect Tag The Collect tag captures a mix of predefined data variables and data from the page, as described in the following sections. Ignore legacy values prefixed by " _t " in your data log files. Default Variables Variable Description Visitor ID The unique ID of the visitor. Event ID An alphanumeric identifier unique to the event. Event Time The UNIX/epoch timestamp of the event, based on UTC time zone. User Agent The user-agent header. DOM Variables Variable Description dom_domain Domain of the site. dom_pathname Pathname of the URL. dom_query_string Querystring portion of the URL following the "?" character. dom_url The entire URL of the HTML document. dom_title Title of the HTML document. dom_viewport_width Device screen width. dom_viewport_height Device screen height. Page URL Variables Variable Description pageurl_scheme The Uniform Resource Identifier (URI) protocol, such as "http" or"https". pageurl_domain Domain of the site. pageurl_path Pathname of the URL. pageurl_querystring Querystring portion of the URL following the "?" character. pageurl_query_params_key For each querystring parameter, there is a data point that contains the parameter key and value. pageurl_full_url The URL of the HTML document without querystring parameters. Referrer URL Variables Variable Description referrerurl_scheme The URI protocol of referring URL, such as "http" or"https". referrerurl_domain Domain of the referring URL site. referrerurl_path Pathname of the referring URL. referrerurl_querystring Querystring portion of the referring URL following the "?" character. referrerurl_query_params_key For each querystring parameter, there is a data point that contains the parameter key and value. referrerurl_full_url The entire URL of the referring page. Tags Executed Variable Description   tags_profile_tag-uid_executed The profile and tag that successfully executed. Each successful tag trigger includes its own entry. Environment Detail Variables Variable Description Account ut.account Tealium iQ account. Profile ut.profile Tealium iQ profile. Environment ut.env The publish environment associated with the utag.js file. Tealium Built-in Variables A full list of Tealium built-in variables is provided in the Built-In Data Layer Variables article. Variable Description Event ut.event The name of the event being tracked, such as a view or link. Version ut.version The utag.js version number, followed by the publish timestamp. Domain ut.domain The top-level domain of the currently-loaded web page. tealium_session_number A duplicate of the existing value in cp.utag_main__sn . tealium_session_event_number A new cookie value in cp.utag_main__se that counts the number of utag.link/view/track calls in the current session (visit) Useful for Single Page Apps (SPAs) where there is always 'one page' and many events on that page First-Party Tealium Cookies Variable Description _ses_id A unique identifier for the session. Requires utag.js version 4.27 and later. _st The time at which the visitor session expires if the visitor does nothing more. This is the visitor's "now" time, plus the session timeout time. This timeout period is normally 30 minutes (1800000 milliseconds) unless configured otherwise. The value of utag.cfg.session_timeout , which can be overridden by changing this variable using a JavaScript Extension. Requires utag.js version 4.26 and later. _v_id The ID value unique to the visitor. Requires utag.js version 4.26 and later. _ss A flag value indicating the start of session. Values are 0 or 1. Requires utag.js version 4.26 and later. _pn The page number value. Starts over at 1 with each new session and increments each time utag.js loads. Requires utag.js version 4.28 and later. _sn The session count. Requires utag.js version 4.28 and later. _dc_visit Keeps count of visits. Starts as "1" for the first visit. _dc_event Keeps count of page views. Starts as "1" for the first page view of a visit. _dc_region The AudienceStream region where the visit session resides. Additional Data Variables The tag collects a variety of other data from the page, including: Data points defined in your data layer. The maximum character length for any one value is 255 characters. Webpage elements, such as metadata, cookie parameters, and JavaScript page variables. Performance timing metrics for gathering Real User Monitoring (RUM) data. This data can be used to understand a user's experience. For example, the browser time to DOM interactive state for pages on your site. Peformance Timing Variable Description timing.domain The domain where the timing data was collected. timing.pathname The path name (web page) where the timing data was collected. timing.query_string The query string value in URL where the timing data was collected. timing.timestamp The date/time when the timing data was collected (epoch time of client's web browser). timing.dns t.domainLookupStart timing.connect t.connectStart timing.response t.responseStart timing.dom_loading_to_interactive t.domInteractive - t.domLoading timing.dom_interactive_to_complete t.domComplete minus t.domInteractive timing.load t.loadEventEnd minus t.loadEventStart timing.time_to_first_byte t.responseStart minus t.connectEnd timing.front_end t.loadEventStart minus t.responseEnd timing.fetch_to_response t.responseStart minus t.fetchStart timing.fetch_to_complete t.domComplete minus t.fetchStart timing.fetch_to_interactive t.domInteractive minus t.fetchStart If the value of a data point equals zero (0), no timing information was captured. You can ignore the zero values when reporting or averaging. Calculating Visitor Timezone The timezone for a visitor is not sent in the EventStore data. You can calculate the timezone by viewing the difference between EventTime and _ses_id on the record where _ss is 1 , since that record is the start of the session. If utag.cfg.session_timeout is known, you can calculate the current local time for the user by subtracting utag.cfg.session_timeout from _st , and then calculating the timezone by looking at the difference between the current time and EventTime . This approach can be used for any record. Individual utag.js Versions For detailed information about individual utag versions, see the utag.js Release Notes. Sample JSON Object { "visitorid": "014fb34a718e001ad754191d58ff1c074003a06c00c48", "eventid": "65f61a4b-54ca-4adf-b757-657e1711f6e7", "eventtime": 1441822083000, "useragent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/600.8.9 (KHTML, like Gecko) Version/8.0.8 Safari/600.8.9", "dom_domain": "tealium.com", "dom_pathname": "/products/audiencestream/", "dom_query_string": "", "dom_url": "http://tealium.com/products/audiencestream/", "dom_title": "AudienceStream | Real-time Data Action Engine | Tealium", "dom_viewport_width": "1670", "dom_viewport_height": "1059", "pageurl_scheme": "http", "pageurl_domain": "tealium.com", "pageurl_path": "/products/audiencestream/", "pageurl_querystring": "", "pageurl_full_url": "http://tealium.com/products/audiencestream/", "referrerurl_scheme": "https", "referrerurl_domain": "google.com", "referrerurl_path": "", "referrerurl_querystring": "", "referrerurl_full_url": "https://www.google.com/", "tags_tiq_as_3_executed": true, "tags_tiq_as_1_executed": true, "udo_ut_account": "tealium", "udo_ut_profile": "main", "udo_ut_env": "prod", "udo_ut_event": "view", "udo_ut_version": "ut4.39.201509091709", "udo_ut_domain": "tealium.com", "firstpartycookies_utag_main_ses_id": "1441822044558", "firstpartycookies_utag_main__st": "1441823881730", "firstpartycookies_utag_main_v_id": "014fb34a718e001ad754191d58ff1c074003a06c00c48", "firstpartycookies_utag_main__ss": "0", "firstpartycookies_utag_main__pn": "2", "firstpartycookies_utag_main__sn": "1", "firstpartycookies_utag_main_dc_visit": "1", "firstpartycookies_utag_main_dc_event": "2", "firstpartycookies_utag_main_dc_region": "us-west-1", "firstpartycookies__gat": "1", "firstpartycookies__ga": "GA1.2.2095105468.1441822080", "js_page.is_mobile": "false", "js_page.is_tablet": "false", "device_type": "desktop", "udo_page_name": "AudienceStream | Real-time Data Action Engine | Tealium", "udo_site_name": "Tealium", "udo_site_description": "Tag Management and Audience Segmentation", "udo_page_type": "page", "udo_post_author": "tealium", "udo_post_date": "2014/11/26", } Performance Timing Metrics For additional information about performance timing metrics, see the following: http://calendar.perfplanet.com/2011/a-practical-guide-to-the-navigation-timing-api/ http://engineering.tripadvisor.com/html5-navigation-timing/ ... View more

This article describes how to use Action Frequency Capping and Prioritization features in AudienceStream to control and prioritize action triggers.  In this article How it Works By default, actions in AudienceStream fire as soon as their conditions are met.  Depending on your connector choice, the actions configured fire when a user joins or leaves an audience or when a user is in the audience at the beginning or end of the visit. Action Frequency Capping Allows you to prevent actions from triggering too close together by prioritizing which actions to trigger relative to one another while ensuring that the most important action still triggers. Prioritization AudienceStream separately provides an option to set delays to prevent individual actions from triggering immediately. You can optionally configure delays in combination a cooldown. The highest priority number specified becomes the highest priority. For example, a priority of "2" is higher than a priority of "1”. All non-capped actions trigger independently without delay and are not affected by the cooldown. If two actions in the same cooldown group have the same priority, only one of them will trigger. If you need both actions to trigger, use separate cooldown groups. Cooldown with Frequency Capping When visitors qualify for numerous actions, such as emails, you can control the triggering by restricting the frequency of actions within a specific time period and then decide which actions to trigger and which to ignore. This will avoid spamming. Cooldown only applies when an action is enabled for Frequency Cap and the connector configuration is assigned an action priority number. The action priority number dictates which actions to trigger in the event that several actions in the same cooldown are fulfilled simultaneously. Frequency Cap On When the Frequency Cap is toggled to On, the highest priority action in a Cooldown Group is triggered. No actions in the same Cooldown Group trigger for the rest of the cooldown period and they will not trigger automatically when the cooldown period expires. Frequency Cap Off Action does not qualify for cooldown and, therefore, will trigger as and when the triggering condition/event occurs. Workflow The following steps summarize frequency capping and prioritization the workflow: AudienceStream evaluates the conditions for all actions in a Cooldown Group. If only one action condition is true, AudienceStream instantly triggers that action. If more conditions are true simultaneously, AudienceStream evaluates their action priorities and then triggers only the highest priority action. During the cooldown hours configured for the group, no actions in that group trigger. When frequency capping is in progress, non-capped actions are not affected by the cooldown and trigger independently without being throttled. If an action has a delay set, the delay is respected. The cooldown starts after the delayed action triggers. For example, if the action is set with a two hour delay, it will not trigger until after the delay. If a higher priority action triggers before the delay time configured is met, the cooldown takes effect and suppresses the delayed action. When the cooldown expires, AudienceStream reevaluates the conditions and starts over from Step 2. Adding a New Cooldown Group When you add a new Cooldown Group, the group is available to all frequency capped actions in your profile. Use the following steps to add a new cooldown group: In the sidebar, navigate to AudienceStream. Click the drop-down list in the user menu and select Manage Cooldown. Click + Add Cooldown Group. Click the Color drop-down list and select a color to display for this group. In the Name field, enter a unique name to identify this group. In the Duration drop-down list, enter a custom number (in hours) or select 6, 12, 24, or 48 hours. The number of hours will  determine the wait time between triggering eligible actions. Click Save to confirm. Using the Default Cooldown Group The Default Cooldown Group applies to frequency capped actions when no other cooldown is configured in your profile.  You can edit the color and duration settings for the Default Cooldown Group and apply it to selected frequency capped actions but you cannot edit the name.   Applying a Cooldown Group to a Connector Action This section describes how to apply a Cooldown Group to a Connector action. You may apply a cooldown group to one or more frequency capped actions in the same connector. Use the following steps to apply a Cooldown Group to a connector action: In the sidebar, navigate to AudienceStream > Audience Connectors. Click My Connectors. Click a connector to expand the details and click Edit. Click the Actions tab and use the drop-down list to select the action for which you want to apply Frequency Capping. Click + Create Action. Scroll down to Frequency Cap and click On. Under Action Priority, use the up or down arrow to assign a number as the action priority. Do not set to zero or a negative number. Assign the priorities in increments of 10 instead of consecutive numbers. This makes it easier to insert a new action later without having to update the priority values for other actions. Under Action Cooldown Group, use the drop-down list to select a group. Click Save. Save and Publish your profile. Usage Example This section provides a usage example using a sample scenario. In this scenario, it is assumed that your profile has two Cooldown Groups and one connector with four actions. Action Name Cooldown Group Cooldown Hours Priority Number Additional Delay A Group 1 48 hours 40 — B Group 1 48 hours 30 2 hours C Default 24 hours 1 — D No Cooldown — — — In this scenario, cooldowns are applied to the actions as follows: Cooldown Group 1 If Action A evaluates to true before Action B, only Action A triggers. The 48-hour cooldown starts, during which time neither Action A or B trigger. If Action B evaluates to true before Action A, only Action B triggers after the 2 hours configured as an additional delay. The 48-hour cooldown starts, during which time neither Action A or B trigger. If Actions A and B are both true at the same time, only Action A triggers because it is assigned the highest priority number. The 48-hour cooldown starts, during which time neither Action A or B trigger. Default Cooldown When Action C evaluates to true, it is triggered instantly. The 24-hour cooldown starts, during which time Action C will not trigger again. Action D triggers immediately after its condition is met and is not throttled by any cooldown. ... View more

Rolling Average is the arithmetic mean of numerical values in a Number or a Tally that are all captured as entries in a Timeline. The Timeline's expiration determines which entries can be factored into the final average. In this article: Table of Contents Placeholder Rolling Average With Timeline Expiration The rolling average includes all time-sensitive entries—excluding expired entries—that are in the Timeline. As the timeline progresses, expired entries are discarded and the final rolling average is recalculated with the next set of valid entries. This facet is best understood with the help of a 90-day timeline of order total values. As illustrated in the table below, the order total entry on Jan 1 is included in the arithmetic mean provided it exists in the 90-day timeline. 90-day Timeline Timestamp Entries Order Total (in $) Jan 1 10.00 Feb 15 20.00 Mar 25 30.00 Rolling Average is (10.00 + 20.00 + 30.00) ÷ 3 = 20.00 The same entry is discarded after 90 days and the rolling average is recalculated for the existing entries. Notice how the resulting average changes when an expired entry is excluded from the aggregate. 90-day Timeline Timestamp Entries Order Total (in $) Feb 15 20.00 Mar 25 30.00 Apr 10 40.00 Rolling sum is (20.00 + 30.00 + 40.00) ÷ 3= 30.00 Rolling Average Without Timeline Expiration All entries count towards the rolling average; none of the entries are excluded. The enrichment keeps the average rolling to account for incoming new entries. The 90-day timeline we discussed above would now look something like this: 90-day Timeline Timestamp Entries Order Total (in $) Jan 1 10.00 Feb 15 20.00 Mar 25 30.00 Apr 10 40.00 May 15 50.00 Rolling Sum is (10.00+20.00+30.00+40.00+50.00)÷5 = 30.00     Adding and Configuring the Enrichment Add a Number attribute or a Tally attribute. This attribute will store the resulting average. Click Create Enrichment and select Set Rolling Average Based on Timeline. From the first drop-down, select the Number/Tally attribute that has the values you want to average out. From the next dropd-own, select the timeline where the number/tally is being recorded. Click Finish to confirm, then Save/Publish your profile. Usage Example In this example, you will learn how to record a timeline of purchase events that have occurred in the last 90 days and, at the same time, capture the resulting order total values. Then you will create a new number attribute along with the rolling average enrichment to average out the order totals. STEP 1: Add a new Number Attribute. Purpose: To store the order total values from the receipt page. Title: Order Total Scope: Current Visit Enrichment: Set this Metric to "order_total" WHEN: ANY_PAGE_EVENT Attach or Create Rule: Current URL contains "receipt.html" STEP 2: Add a new Timeline Attribute and set each entry to expiry after 90 days. Purpose: To record every order confirmation event on the receipt page and capture the numerical order total values. Title: 90-day Order Timeline Scope: Visitor Entry: Update Timeline Capture Attribute Data: Order Total WHEN: ANY_PAGE_EVENT Attach or Create Rule Condition: Current URL contains "receipt.html" Entry: Set Expiration of Timeline events Set each event in this Timeline to expire after "90" days STEP 3: Add a new number and create the 'Set Rolling Average Based on Timeline' Enrichment. Purpose: To crunch numbers and store the resulting average. Title: 90-day Order Average Scope: Visitor Enrichment: Set Rolling Average based on Timeline Set this Metric to the Rolling Average of Metric "Order Total" captured in timeline "90-day Order Timeline" Results Go to API sampler in your profile and submit a query to find out how many entries were logged into the Timeline and also to determine the final average. TIP: Locate the title you assigned to the Metric/Tally and the Timeline Attribute. Assuming there are two entries in the 90-day Order Timeline, the API Sampler will display the results like so: Similarly, here's the final average stored in the 90-day Order Average Metric: ... View more

This article describes the set of strings attribute and how to use it. In this article: How It Works Before you begin, familiarize yourself with the following: Using Attributes Using Enrichments The set of strings attribute stores a set of unique text values. Values in a set are only stored once, regardless of the number of times they occur for the visitor or visit. The set of strings attribute is most commonly used for product categories viewed, pages viewed, and products purchased. Examples: Attribute Name Values Product Categories Viewed "Home Improvement", "Electronics", "Apparel", "Kitchen" Browsers Used "Chrome", "Safari" Cart Items "iPad", "Screen Protector", "Headphones" The set of strings attribute is available in the following scopes: Visit and Visitor. Set of Strings Enrichments Add to Set of Strings Add a string value to a set of strings. Adds only unique strings. Attribute Name: product_category Starting Value "Home Improvement", "Electronics", "Kitchen" Enriched With "Apparel", "Electronics" Resulting Value "Home Improvement", "Electronics", "Kitchen", "Apparel" The result ignores the "Electronics" item because it exists already in the set of strings. Store Array as Set of Strings This enrichment is used to save the values from an array of strings attribute into a set of strings attribute. All duplicate elements in the array are ignored in the new set, which permits only unique strings. Attribute Name: Product Categories Viewed Starting Value "Kitchen" Enriched With ["Home Improvement", "Electronics", "Kitchen"] Resulting Value "Home Improvement", "Electronics", "Kitchen" Update Set of Strings By Set of Strings This enrichment appends the values from another set of strings attribute into the set of strings. For example, to track the product categories that a visitor purchases from you might have two set of strings attributes named "Categories Purchased", with one scoped to visit to capture when the purchase occurs and one scoped to visitor to store the master set. Visit: Categories Purchased Visitor: Categories Purchased   "Electronics" "Electronics"   "Kitchen", "Apparel" "Electronics", "Kitchen", "Apparel"   "Kitchen", "Electronics" "Electronics", "Kitchen", "Apparel" While the set of strings scoped to visit is overwritten with new values each time, the enrichment copies those values into the set of strings scoped to visitor where the master list expands, storing each unique value encountered. Attribute Name: Product Category Purchased Starting Value "Electronics" Enriched With "Home Improvement", "Electronics", "Kitchen" Resulting Value "Electronics", "Home Improvement", "Kitchen" Difference Between Two Sets of Strings Create a new set of strings attribute that contains the items from one set of strings that do not appear in another set of strings. For example, to find the categories that a customer browsed, but did not purchase from, use this enrichment to find the difference between "Categories Browsed" and "Categories Purchased". Example: Find values present in: "Categories Browsed" and that are not in: "Categories Purchased" Attribute Name: Browsed Categories Not Purchased Starting Value   Enriched With "Categories Browsed": "Home Improvement", "Kitchen", "Windows" "Categories Purchased": "Home Improvement" Resulting Value "Kitchen", "Windows" Remove Set of Strings Remove a set of strings based on a set of conditions. This is the equivalent of deleting the set. Attribute Name: product_category Starting Value "Home Improvement", "Kitchen", "Windows" Resulting Value   Lowercase Set of Strings Lowercase a set of strings based on a set of conditions. Attribute Name: product_category Starting Value "Home Improvement", "Electronics", "Kitchen" Resulting Value "home improvement", "electronics", "kitchen" Set to Top Tally Items Create a set of strings using the highest valued items from a tally. For example, to track the three most viewed products, create a set of strings to capture the top three entries from a tally attribute that tracks the occurrences of viewed products. Attribute Name: Top 3 Products Viewed Starting Value   Enriched With Top 3 Items in "Viewed Products": {   "AirPods Pro" : 3,   "iPhone 10" : 6,   "iPhone Case" : 10,   "MacBook Pro" : 1,   "iMac" : 2 } Resulting Value "iPhone Case", "iPhone 10", "AirPods Pro" Set to Tally Items Above Target Value Create a set of strings using the items from a tally whose values are above a set threshold. For example, to track products that have been viewed more than 20 times, create a set of strings to capture the entries from a tally attribute that tracks the occurrences of viewed products. Attribute Name: Products Viewed 20+ Times Starting Value   Enriched With Items in "Products Viewed" that are greater than 20: {   "AirPods Pro" : 21,   "iPhone 10" : 35,   "iPhone Case" : 12,   "MacBook Pro" : 1,   "iMac" : 2 } Resulting Value "iPhone 10", "AirPods Pro" Remove Entry from Set of Strings Remove an entry from a set of strings based on a set of conditions. For example, remove the entry "iPhone Case" from a set of strings that tracks a product wishlist because it has been purchased. Attribute Name: Product Wishlist Starting Value "iPhone 10", "AirPods Pro", "iPhone Case" Enriched With Remove purchased_product (value "iPhone Case") Resulting Value "iPhone 10", "AirPods Pro"   ... View more

Tag Specifications and Requirements Specifications Name: Microsoft adCenter Vendor: Microsoft Type: Analytics, Conversion Tracking Required Microsoft adCenter Account Site ID Action ID Domain ID Revenue Tag Configuration in Tealium iQ Adding 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. Configuring the Tag Title (Required): Enter a descriptive title to identify the Tag instance. Tag (Required): From the drop-down list, choose if you want to load the Tag as a JavaScript code or iFrame. Type (Required): Choose the tracking feature you want to enable for the Tag. Analytics: This will allow the Tag to perform Analytics tracking. Conversion: This will allow the Tag to track conversion events. Site ID (Required): Enter the long, alphanumeric value following "flex.atdmt.com/mstag/site/" in the tracking code provided by adCenter. You have the option to configure this field via mapping. Example: d2c3d50f-6f6a-3f2c-a303-6f032aece46c Action ID (Required): Enter the identifier of conversion action you want to track. To set this value dynamically, use the mapping toolbox. Example: actionid=52987 Domain ID (Required): Enter the numeric value assigned to your domain. This value is the same as the account id provided by adCenter. To set this value dynamically, use the mapping toolbox. Example: domainId= 743536 CP: This field is pre-populated with the default value of "5050" assigned to the "cp" parameter in the Conversion Tag. To override this value, use the mapping toolbox. Revenue (Optional): Enter the fixed revenue value in this field. If you prefer to configure it by mapping, leave this field blank. Tag settings #4 through #8, can also be mapped to their appropriate destinations using the Mapping toolbox (see Setting up Mappings). NOTE: Bing Ads has deprecated this Tag and, therefore, recommends replacing it with the new UET Tag. Applying 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 Practices: If you want to implement this Tag for Analytics tracking, load it on all pages of your site; use the default "Load On All Pages" rule. For Conversion tracking, however, set up relevant Rule conditions to load the Tag on the checkout page or other conversion pages of your site. Setting up Mappings Mapping is the simple process of sending data from a data source, in your Data Layer, to the matching destination variable of the vendor Tag. The destination variables for this Tag are available in the Mapping toolbox. Note: We recommend setting up the E-Commerce Extension for this Tag. Be sure to configure the _csubtotal variable so the Extension can automatically send its value to the Revenue variable. Action ID: Map to this destination to send the numeric identifier of the conversion action you want to track. Revenue: Map to this variable to send the revenue value generated by the conversion action. Mapping to Revenue will also override the E-Commerce Extension's _csubtotal value. Non Advertising Cost: Map to this destination to send information about non-advertising expenses, like credit card processing fees. Tax Cost: Map to this destination to send the sales tax information applicable to the transaction. Shipping Cost: Map to this destination to send information about shipment expenses. Site ID: Map to this destination to send the alphanumeric value following the "flex.atdmt.com/mstag/site/" in the tracking pixel. Domain ID: Map to this destination to send the identifier of the domain you want to track. cp: Map to this destination to send the value of the "cp" parameter in the tracking pixel. Vendor Documentation How to manage adCenter campaigns Conversion Tracking with campaign analytics How to set up Mappings How to set up Load Rules How to add a Tag ... View more

This article will guide you in configuring the Splunk tag in Tealium iQ and configuring the Tealium Digital Analytics App within the Splunk interface.  In this article: Table of Contents Placeholder Tag Configuration in Tealium iQ Adding 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. The Splunk tag can be located through the Big Data category in the Marketplace. Set the following fields: Title: The default title is "Splunk". You may enter a descriptive title to identify the tag instance. Server: This field is prepopulated with the location pathname of the Amazon S3 bucket tied to your account and profile. Do not change this server setting unless you want to send the data to a custom server. Require Mapping: This setting allows you to decide what data points you want to send. Select the default setting of No if you intend to send the entire data layer. Select Yes if you want to send only the mapped data points. Applying 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. Do not proceed to Data Mappings if you have disabled mapping for the Tag instance. Instead, click Finish to complete the tag configuration. Mapping Data Sources The following steps are required only if you have set Require Mapping to Yes. In the Tag Settings window, click Next or select the Data Mappings tab. From the Data Sources drop-down, select the data source you want to map. Click the Select Destination button. Because there is no mapping toolkit for this tag you must create custom destination variables to map. Enter a custom variable in the Custom Destination text field. It is recommended to choose short variables to avoid exceeding any browser-imposed character limits on GET requests. Click + Add which will add the custom destination variable.  Click Close to return to the Tag Settings window. Repeat steps 3 to 5 to add more destinations. Then click Finish to save the tag definition or Cancel to exit without adding the tag. Splunk Integration Before you begin the integration process, contact your account manager to request the Amazon Web Services Key ID and Secret key for your profile. How to Install Amazon S3 Add-on (Splunk Connector) Navigate to the Splunk Apps site at http://apps.splunk.com/app/1664/ and download the Tealium Digital Analytics App. An app file (*.tar or *.tgz) required by the connector will be downloaded in the process. You will need to obtain account credentials from your Splunk administrator in order to log in to access the download page.  Launch Splunk and log into your account. Click Apps at the top-left corner of the screen. From the drop-down menu, click Manage Apps. In the next screen, click the Install App From File button. This will open the Upload app screen. Click the Choose File button and select the downloaded app file from your computer to upload it. Add an S3 Input for Splunk Add-on for AWS Please visit the following Splunk article for implementaiton instructions: http://docs.splunk.com/Documentation/AddOns/released/AWS/S3 Setting up Data Inputs for your Splunk Instance Click on Settings at the top-right corner of the Splunk interface. From the drop-down menu, click Data Inputs. Click on Amazon S3. In the next screen, click New to create a new configuration. In the Add new screen, enter your S3 credentials: In the Resource name field, enter the uconnect server pathname (see Configuring the Tag). If the uconnect pathname contains account.name , replace the "." with "/" and change it to uconnect.tealiumiq.com/ account/name . Enter the Key ID and the Server key in their respective fields. Click Save. This completes the Splunk integration.         ... View more

This article describes how to edit and view your user settings to view user permissions, edit your user information, change your account password, and reset your MFA token. In this article: Table of Contents Placeholder Access and View Your User Settings Use the following steps to access and view your user settings: Click your user icon in the upper right of the screen and select  Edit/View User Settings . The User Overview information and profile permissions for your account display. Click Edit User Profile to change or update your  First Name, Last Name, Title, or Email address. Change Password The Change Password screen allows you to change your password according to the password requirements of your account. Use the following steps to change your password: Click your user icon in the upper right of the screen and select  Edit/View User Settings . The User Overview information and profile permissions for your account display. In the right panel, click Change Password.   In the Current password field, enter your current password In the New password field, enter your new password according to the password requirements on the screen. In the Confirm new field, enter your new password again. You can optionally select the Show Password checkbox to display the password as you type. Click Change Password. Click Close to close the window. MFA Settings Use the following steps to reset your MFA token: Click your user icon in the upper right of the screen and select  Edit/View User Settings . The User Overview information and profile permissions for your account display. In the right panel, click MFA Settings. Go to Resetting your MFA token and follow the steps outlined. Reset API Key Use the following steps to reset your API key: Click your user icon in the upper right of the screen and select  Edit/View User Settings . The User Overview information and profile permissions for your account display. In the right panel, click API Key. Go to Managing and Generating API Keys and follow the steps outlined. ... View more

Tag Specifications and Requirements Specifications Name: AdRoll Vendor: AdRoll Type: Retargeting Ads Required Services: AdRoll Account Configurations: Advertiser ID Pixel ID Tag Configuration in Tealium iQ Adding 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.   Configuring the Tag Title(Required): Enter a descriptive title to uniquely identify the Tag instance. Advertiser ID (Optional): Enter the 22-character, alphanumeric value of "adroll_adv_id" specified in the SmartPixel. Example: "R3GMACQF5KBLDNNTUYCEML" Pixel ID (Optional): Enter the 22-character, alphanumeric value of "adroll_pix_id" specified in the SmartPixel. Example: "5SA7B3NDK4G9CVXZPR61031" Note: The SmartPixel can be obtained from the dashboard of your Adroll account. Tip: Place this Tag at the bottom of the list in the Tags tab; Adroll recommends you load this Tag after the webpage has rendered completely.   Applying 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. Note: AdRoll recommends loading the Tag on every page of the site to properly segment visitors. Leave the default 'Load on All Pages' selection as is.   Setting up Mappings Mapping is the simple process of sending data from a data source, in your Data Layer, to the matching destination variable of the vendor Tag. The destination variables for this Tag are available in the Mapping toolkit. For ease of use, the variables are grouped into different categories.   adroll_record_user.myvar: Map to this variable for subsequent calls made by the "adroll_record_user" function with data from the "adroll_record_user" object in mapping after the initial page load. Replace "myvar" with the desired name of your custom record action. adroll_conversion_value_in_dollars: Map to this variable to pass the dollar value of the conversion. adroll_currency: Map to this variable to pass the currency value of the conversion. adroll_segments: Map to this variable to pass the name of the segment you set up in the AdRoll dashboard. adroll_email: Map to this variable to pass the visitor's email. adroll_custom_data.product_id: Map to this variable to send product ID's.  adroll_custom_data.product_group: Map to this variable to send the product's group. adroll_custom_data.product_action: Map to this variable to send the product's action. adroll_custom_data.product_category_id: Map to this variable to send the product's category ID. adroll_adv_id: Map to this variable to send the advertiser's unique ID. adroll_pix_id: Map to this variable to send the SmartPixel's unique ID.   Custom Mapping Adroll allows you to set custom values for your conversions.  Map to the "adroll_custom_data." destination then append the data source's name to the destination variable. Repeat this process for every data source you want to map (example: _corder mapped to adroll_custom_data.ORDER_ID).     Vendor Documentation AdRoll Support: FAQs Activating your Adroll Smartpixel ... View more

Tag Specifications and Requirements Specifications Name: LinkShare Vendor: Rakuten Type: Affiliate Marketing Required Services: LinkShare Network Account Configurations: Merchant ID Tag Configuration in Tealium iQ Adding 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. Configuring the Tag Title (Required): Enter a descriptive title to identify the Tag instance. Merchant ID (Required): Enter the Advertiser's unique ID assigned by LinkShare. Applying 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 of your site, create a new load rule with the relevant conditions. Best Practices: The following best practices come highly recommended for this Tag. Load this Tag on a conversion page (Order Confirmation/Checkout) and the page following a conversion (Receipt/Thank-You). Load the Tag only once per conversion page for optimized performance. Setting up Mappings Mapping is the simple process of sending data from a data source, in your Data Layer, to the matching destination variable of the vendor Tag. The destination variables for this Tag are available in the Mapping toolkit. For ease of use, the variables are grouped into different categories. Note: Be sure to configure the E-commerce Extension for this Tag. As long as you properly add and configure the E-Commerce Extension, you do not have to map anything in the Tag configurations; the E-Commerce Extension will take care of it. However, if you want to override certain E-commerce variables or you are not using the E-Commerce Extension, map to the following destination variables. ord: Map to this variable to send the unique ID of the order/transaction. cur: Map to this variable to send the alphanumeric, three-character currency value. "cur"=USD skulist: Map to this variable to send a list of item SKUs. Each SKU in the list must be unique to the item. "skulist"=sku1|sku2|sku3 qlist: Map a list of item quantities to this variable. The quantities must be listed in the same order as their corresponding SKUs. "qlist"=2|4|8 amtlist: Map a list of item subtotals to this variable. The subtotals must be listed in the same order as their corresponding SKUs and formatted as price*quantity*100. "amtlist"=1000|2000|4000 namelist: Map a list of item names to this variable. The item names must be listed in the same order as their corresponding SKUs. "namelist"=XXX|YYY|ZZZ Vendor Documentation About Rakuten LinkShare Glossary Affiliate Marketing Tracking Technology: Video Tutorial Affiliate Marketing resources (Login required to view articles and videos) Resources How to set up Mappings How to set up Load Rules How to add a Tag ... View more

This article describes how to set up the Kenshoo Conversion tag in your Tealium iQ Tag Management (TiQ) account. In this article: Table of Contents Placeholder Tag Tips Uses E-commerce extension (_corder, _csubtotal, _cpromo, _ccurrency) Order ID, Amount, Promotion Code, and Currency are automatically set. These values can be over-written by creating mappings. Map a value to 'type' to set a dynamic Conversion Type Tag Configuration First, go to Tealium's tag marketplace and add the Kenshoo Conversion tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Kenshoo ID Refers to the subdomain of the URL. Value is 00 for the following example: //00.xg4ken.com/ Profile Token Refers to the long alphanumberic value applied to the cid querystring parameter of the URL. Conversion Type This value details the conversion type, which by default should be set to 'conv'. You can change this to any other relevant conversion type in your site. For example, if you want to track Registrations simply change it to 'reg' or for lead to 'lead'. 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 Conversion Type (type) Order Amount (val) Order ID (orderId) Order Promo Code (promoCode) Order Currency (valueCurrency) Vendor Documentation Kenshoo Guide Series ... View more

This article describes how to restrict which vendors are available in the tag marketplace by enabling and configuring the Tag Marketplace Policy. In this article: Table of Contents Placeholder Prerequisites The Manage Account permission level is required to access this feature. How It Works The tag marketplace contains every vendor integration that Tealium iQ offers. This means that any user with permission to add tags and publish has the ability to add one of these tags to your configuration (and to your site). The tag marketplace has hundreds of tags and is easily searchable and browseable. For example, if you search the tag marketplace for "Google" several offerings will display. The Tag Marketplace Policy allows you to control which vendor tags display in your tag marketplace. You can  use the policy to restrict and safeguard your account so that only a limited selection of preapproved vendor tags can be added to your account. Once a policy is enabled, it automatically applies to all underlying profiles. When enabled, the policy hides all vendors by default. and applies to all underlying profiles. Once you use the Tag Marketplace Policy to select the vendors approved for your site, only those vendors are offered. Limiting the offerings provides an additional layer of security to your account and prevents unwanted tags from being released to your site. The Manage Tag Marketplace Policy dialog uses the following terms and buttons: Enable Tag Marketplace Policy Check this box to activate the Tag Marketplace Policy for your account. By default, this feature is deactivated and all vendor tags are available in the tag marketplace. Hidden Tags When the policy is activated, the tags in this list are not be available in the tag marketplace. Marketplace Tags When the policy is activated, the tags in this list will display in the tag marketplace. Hide All This button moves all tags to the Hidden Tags window, and therefore unavailable in the tag marketplace. Show All This button moves all tags into the Marketplace Tags window and makes all tags available in the tag marketplace. Reset Clicking Reset allows you to revert changes to the Tag Marketplace Policy back to the values present before clicking Save. Save Clicking Save saves the values for your profile. Enable Tags This section describes how to enable only the tags you specify to be available in the tag marketplace and uses Tealium tags as an example. Use the following steps to enable only "Tealium" tags in the policy: Click your user icon in the upper right of the screen and select Manage Tag Marketplace Policy. The Manage Tag Marketplace Policy dialog displays. Click the Enable Tag Marketplace Policy checkbox. Scroll down the list of Hidden Tags and click Show next to all Tealium tags. The Tealium tags selected move to the Marketplace Tags column, indicating that only these tags will appear in the tag marketplace. Click Save. You do not need to Save and Publish after this step, the changes go into effect immediately. With this policy in place, the tag marketplace now only offers the "Tealium" tags and an alert is displayed indicating that the tag marketplace policy is enabled. Try to search for another vendor. There are no return results. Show a Tag Click your user icon in the upper right of the screen and select Manage Tag Marketplace Policy. The Manage Tag Marketplace Policy dialog displays. Click the Enable Tag Marketplace Policy checkbox. From the Hidden Tags column, identify the tag you want to show. Click the Show next to your target tag. The tag is moved to the Marketplace Tags column. Repeat to add more tags. Click Save to confirm. Hide a Tag Click your user icon in the upper right of the screen and select Manage Tag Marketplace Policy. The Manage Tag Marketplace Policy dialog displays. Click the Enable Tag Marketplace Policy checkbox. From the Marketplace Tags column, scroll down to identify the tag you want to hide. Click Hide next to your target tag. The tag is moved back to the Hidden Tags column. Repeat to hide other tags. Click Save to confirm. Show All Tags Click your user icon in the upper right of the screen and select Manage Tag Marketplace Policy. The Manage Tag Marketplace Policy dialog displays. Click the Enable Tag Marketplace Policy checkbox. Click Show All. All tags are moved to the Marketplace Tags column. Click Save to confirm. Hide All Tags Click your user icon in the upper right of the screen and select Manage Tag Marketplace Policy. The Manage Tag Marketplace Policy dialog displays. Click the Enable Tag Marketplace Policy checkbox. Click Hide All. All tags are moved back to the Marketplace Tags column. Click Save to confirm. Reset the Policy Clicking Reset cancels any show/hide actions prior to saving and restore the two columns to their original state prior to saving. ... View more

This article describes how to set up the Clicktale Carmel tag in your Tealium iQ Tag Management account. In this article: Table of Contents Placeholder Tag Tips Override the standard config values using mappings. To pass audiences and badges to Clicktale: Contact your Clicktale representative to enable the receiving of this data. When mapping a badge, enter the name as it should appear in Clicktale. Set Send All Audiences to True to send all audiences to Clicktale in the following format: window.ClicktaleEventHandler(["Tealium Audience: AUDIENCE NAME", ...]); Set Send Replay Link to True to make your Clicktale replay link available as the server-side attribute clicktale_replay_link . Contact your Clicktale representative to enable the generation of the replay link. Server-side attributes will appear in the current account and profile. Use a mapping to override tealium_profile . Tag Configuration First, go to Tealium's tag marketplace and add the Clicktale Carmel tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Title Required. Identifies the tag instance. Clicktale Carmel is the default name. When using multiple tags by the same vendor, assign a unique name Partition The partition where data is sent. Example: www07 Project GUID / PTC ID Clicktale Project GUID Example: 11111111-1111-1111-1111-11111111111 Send Replay Link Select True to make your Clicktale Replay Link available as a server-side attribute. Send All Audiences Select True to send each audience to Clicktale in the format window. Example: ClicktaleEventHandler(["Tealium Audience: AUDIENCE NAME", ...]);. Send Events to ClickTale Select True to send Event Data to Clicktale. Ad Blocker Detection Select True to enable Ad Blocker Detection. Fraud Detection Select True to enable Fraud Detection. Friction Detection Select True to enable Friction Detection. Applying 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. Load this Tag on the page where you want to track the visitor's mouse movements. Tealium recommends that this tag loads after the page has rendered completely. 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 partition String Partition. The partition where data is sent. Map to this variable to dynamically configure the server partition value. project_guid String Project GUID. Map to this variable to set the project guide field. send_replay_link String, Boolean Send Clicktale Replay Link Values are true or false. send_audiences String, Boolean Send all audiences. Values are true or false. tealium_account String Tealium Account. tealium_profile String Tealium Profile. SendEventsToClicktale String Toggle on to Send Events to Clicktale ad_blocker_detection String, Boolean Toggle on to enable Ad Blocker Detection fraud_detection String Toggle on to enable Fraud Detection friction_detection String Toggle on to enable Friction Detection livesignals_url String LiveSignals File URL Ad Block Detection Variable Description AdBlockerEventName String Ad Blocker Event Name AdBlockerFileURL String Ad Blocker File URL AdBlockerTimer Number Ad Blocker Timer Fraud Detection Variable Description ExcessivePasteLowThreshold Number Triggers when thresholds are met that identify abnormal and potentially fraudulent pasting behavior within the same visitor session. Excessive Paste Low Threshold ExcessivePasteMediumThreshold Number Triggers when thresholds are met that identify abnormal and potentially fraudulent pasting behavior within the same visitor session. Excessive Paste Medium Threshold ExcessivePasteHighThreshold Number Triggers when thresholds are met that identify abnormal and potentially fraudulent pasting behavior within the same visitor session. Excessive Paste High Threshold ExcessivePasteEventName String Excessive Paste Event Name ExcessiveReloadLowThreshold Number Triggers when thresholds are met that identify abnormal and potentially fraudulent reload behavior within the same visitor session.  Excessive Reload Low Threshold ExcessiveReloadMediumThreshold Number Triggers when thresholds are met that identify abnormal and potentially fraudulent reload behavior within the same visitor session.  Excessive Reload Medium Threshold ExcessiveReloadHighThreshold Number Triggers when thresholds are met that identify abnormal and potentially fraudulent reload behavior within the same visitor session.   Excessive Reload High Threshold ExcessiveReloadEventName String Excessive Reload Event Name FraudCondition String Fraud Condition Friction Detection Variable Description ConsecutiveClickClickableThreshold Number Consecutive Click Clickable Threshold Identifies when a visitor repeatedly clicks the same (clickable) element without a response from the page. The customer does not click any other element between clicks. This signal indicates a potential issue with the element. ConsecutiveClickNonClickableThreshold Number Consecutive Click Non-clickable Threshold Identifies when a visitor repeatedly clicks the same (un-clickable) element without a response from the page. The customer does not click any other element between clicks. This signal indicates a potential design flaw. ConsecutiveClickEventName String Consecutive Click Event Name ConstantHoverThreshold Number Constant Hover Threshold Identifies when a visitor consistently hovers over the same element without clicking. This signal indicates a visitor’s intent or interest without clicking the element. ConstantHoverEventName String Constant Hover Event Name JsErrorClickThreshold Number JS Error Click Threshold Identifies a click that triggers a JavaScript error. JsErrorClickEventName String JS Error Click Event Name RageClickClickableThreshold Number Rage Click Clickable Threshold RageClickNonClickableThreshold Number Rage Click Non-clickable Threshold RageClickEventName String Rage Click Event Name RepeatedScrollMinPercentThreshold Number Repeated Scroll Minimum Percent Threshold Identifies when a visitor scans the page quickly and scrolls repeatedly from top to bottom. Identifies a potentially poor user experience or a frustrated visitor. RepeatedScrollMaxPercentThreshold Number Repeated Scroll Maximum Percent Threshold Identifies when a visitor scans the page quickly and scrolls repeatedly from top to bottom. Identifies a potentially poor user experience or a frustrated visitor. RepeatedScrollAmountThreshold Number Repeated Scroll Amount Threshold RepeatedScrollEventName String Repeated Scroll Event Name Vendor Documentation How to Generate Clicktale Tracking Code Clicktale Carmel Parameters Tealium Integration Frequently Asked Questions ... View more

The Google Ad Manager Spotlight tag was formerly called the DoubleClick Spotlight tag. The DoubleClick Spotlight tag is deprecated. In this article: Table of Contents Placeholder Tag Specifications and Requirements Specifications Name: Google Ad Manager Spotlight Vendor: Google Type: Conversion Tracking Requirements Services: DFA ( Google Ad Manager  for Advertisers) Account Configurations: Region Code Advertiser ID Spotlight activity  Type of Spotlight activity Web address of the DFA ad server Tag Configuration Adding 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. Configuring the Tag Use the following steps to configure the tag: Title Required. Enter a descriptive title to identify the tag instance. Region Required.  Select the region where the server where the Spotlight activity is located. Example: Americas Advertiser ID Required. This is the ID of the source advertiser that is tracking the Spotlight activity. Enter the value of the "src" key in this field. Example: 1234567 Type Required. Enter the 8-character string of the group/type of Spotlight activity. Example: abcde123 Category Required. Enter the 8-character string assigned to the Spotlight activity being tracked. Example: fghij456 DCNET Optional. If your image pixel contains a dcnet value, you can enter it here. Place this Tag at the top of the list in the Tags tab to ensure that it loads as soon as the page starts loading. Applying 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. As a best practice, set up load rule conditions to strategically load these tags on the pages where you want to track the conversion. Setting up Mappings Mapping is the simple process of sending data from a data source, in your data layer, to the matching destination variable of the vendor tag. The following table describes the standard destination variables available from the Mapping Toolbox. Variable Description qty Map to this variable to indicate the quantity of items sold or the number of transactions for an item. cost Map to this variable to indicate the amount of revenue generated by the transaction. list_id Map to this variable to send the identifier of the boom list (created by the advertiser for retargeting purpose).  U1   through   U10 Map to one or more variables to send custom data. Additional Resources Tealium Documentation How to set up Mappings How to set up Load Rules How to add a Tag Vendor Documentation Conversion Tracking and Spotlight Legacy Image Tags (Spotlight) ... View more

Tag Specifications and Requirements Specifications Name: comScore Vendor: comScore Type: Web Analytics Required Services: comScore Direct Account Configurations: comScore Client ID Tag Configuration in Tealium iQ 1. Adding 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. 2. Configuring the Tag Title (Required): Enter a descriptive title to identify the Tag instance. Account (Required): Enter the client ID provided to you by comScore. Client ID is the numeric value of the c2 parameter and can be obtained from your comScore Direct account. Example: 18273594 Stream Sense Video (Required): Choose whether or not you want to activate comScore's Stream Sense functionality for this Tag. Stream Sense tracks and reports browser interaction with video advertisements. By default, the functionality is set to 'Deactivate'. To activate Stream Sense, select 'Activate' from the drop-down. Tip: Place this Tag at the top of the list in the Tags tab as comScore recommends you load this Tag as soon as the page begins to load. 3. Applying 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: Leave the default 'Load on All Pages' selection as is. Loading this Tag on all pages of your site optimizes the data collection process. 4. Setting up Mappings Mapping is the simple process of sending data from a data source, in your Data Layer, to the matching destination variable of the vendor Tag. The Mapping toolbox for this Tag does not offer any pre-defined destination variables since comScore supports custom (more like 'user-defined') variables. The custom variable you specify will in turn serve as the Tag's destination variable (see example screenshot below). Vendor Documentation About comScore comScore FAQs What is comScore Direct How to set up Mappings How to set up Load Rules How to add a Tag ... View more

When configuring the Advertising.com Dynamic Retargeter Tag (ADR), you select the page type from the drop-down list. What this action does in the background is set the 'pty' variable (something that the ADR Tag recognizes for page type) to a certain value. So, when you select 'Home Page' from the Page Type drop-down list, you are setting 'pty' to 'hp'. You have the option to override or dynamically set the Page Type by mapping the appropriate data source to pty. Prerequisites Before you add the ADR Tag, make certain the E-Commerce Extension is set up and configured. The E-Commerce variables this Tag uses are _cprod, _corder, _csubtotal, and _ccat. Dynamically mapping the Page Type Begin by creating a data source to hold the specific page type value you want to send. Next, use the Tag's mapping toolbox to map the data source to pty. Then, add a Lookup table Extension to set the value of the page type data source you created. Creating a data source Navigate to the Data Layer tab. Add a new data source of the type UDO Variable. Give it a suitable description. Example: adr_pty Mapping to pty Navigate to the Tags tab. Click the Ad.com Dynamic Retargeter Tag. This will expand its configuration view. Click the Edit button in the Mapped Data Sources section. The Data Mapping tab will appear. From the Data Sources drop-down, select the data source you created in Step 2 of Creating a data source. Click the Select Destination button. Since no pre-defined variables are present in the toolbox, you must manually map the data source to pty. Click Apply to select the data source. Enter "pty" in the text field next to your chosen data source. Click Apply to complete the mapping. Adding the Lookup Table Extension Navigate the Extensions Tab and add the Lookup Table Extension from the marketplace. The configuration window will appear. Give the Extension a suitable title. Scope the Extension to 'Ad.com Dynamic Retargeter at AOL'. From the Lookup Value In drop-down, select the data source from which you will lookup the page type value. Example: page_type(js) From the Destination drop-down, select the data source you created in Step 2 of Creating a data source. In the Default Output field, enter "none". This will be assigned to the Destination variable if no match is found in the Lookup Table. Leave the Variable Type and Match Type fields to their default selection of String and Exact, in that order. Set the following lookups: Lookup Match: home Output: hp Lookup Match: landing Output: lp Lookup Match: search Output: sp Lookup Match: category Output: cp Lookup Match: product Output: pp Lookup Match: cart Output: ct Lookup Match: confirmation Output: cfp Then Save and Publish your changes by clicking the Save/Publish button in the top right corner. How to set up Mappings ... View more

Tag Specifications and Requirements Specifications Name: Chartbeat Vendor: Chartbeat Type: Real-time Web Analytics Required Services: Chartbeat Account Configurations: Chartbeat User ID Tag Configuration in Tealium iQ Adding 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. Configuring the Tag Title (Required): Enter a descriptive title to identify the Tag instance. User ID (Required): Enter the numeric user ID provided to you by Chartbeat. This can be found in your Chartbeat account. Example: 1234 Domain (Required): Enter the domain name where you want to implement Chartbeat. Do not include the prefix 'www'. Example: yoursite.com Use Canonical (Optional): Choose whether or not you want Chartbeat to use the Canonical path (the preferred URL) to access a page. By default, the Use Canonical drop-down is set to false, in which case Chartbeat will use the page's actual URL. Select 'true' if you want Chartbeat to use the canonical path you have defined using a link element in your site's HTML. Example: Assume a page can be accessed by two different URLs— http://yoursite.com/products?category=apparel&kids and http://yoursite.com/apparel/kids . But only URL #2 is set as canonical. By enabling the Use Canonical field, Chartbeat can use your preferred URL#2 for tracking purpose. Note: You have the option to override this selection by mapping to the 'path' variable. NOTE: You may use the Data Mapping toolbox to override or dynamically set the Tag settings for #2 through #4.   Applying 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. Note: Leave the default 'Load on All pages' rule as is. Chartbeat, like most analytics Tags, is recommended to load on all pages of the site to ensure accurate data collection. Setting up Mappings Mapping is the simple process of sending data from a data source, in your Data Layer, to the matching destination variable of the vendor Tag. The destination variables for this Tag are available in the Mapping toolkit. (how to map a Data Source to a Tag destination?)     User ID: Map to this destination to send the numeric user ID, one that Chartbeat has provided you. Domain: Map to this destination to send the domain name where Chartbeat is implemented. Use Canonical (canonical): Map to this destination to indicate whether or not the page's url is Canonical. Make sure the value in the data source is either "true" or "false". title: Map to this destination to send the page's current title. path: Map to this variable to send the page's path. sections: Map to this variable to send section information that contains the content you want Chartbeat to track. Multiple sections must be sent as a comma-separated list of values. authors: Map to this variable to send information about the content's author. Multiple authors must be sent as a comma-separated list of values. Vendor Documentation About Chartbeat Publishing for Editorial Chartbeat Implementation Docs Chartbeat Configuration Variables Troubleshooting/FAQs ... View more