-
Expand/CollapseMenu
- TLC Home Home
- Discussions & Ideas Discussions & Ideas
- Product Guides Product Guides
- Knowledge Base Knowledge Base
- Developer Docs Developer Docs
- Education Education
- Blog TLC Blog
- Support Desk Support Desk
Tealium Learning Center
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Home
- :
- About kathleen_jo
10-09-2019
User Recent Badges
4 weeks ago
4 Kudos
This article will guide you through how to use Tealium iQ Tag Management to track between two separate domains.
Table of Contents Placeholder
Why use a First Party Cookie Sync between domains?
You would want to use this method if you have a need to track certain key/value pairs from one domain to another. For example:
You have siteA.com which is your online documentation website. Your online documentation site receives a lot of traffic but has no forms to track query string parameters (utm_campaign, utm_source, utm_medium, cid, etc.) all the way to database/CRM level.
You also have siteB.com which does have forms with hidden form fields that can read query string parameters, like utm_campaign, but there is no easy way to transfer this tracking from siteA.com to siteB.com.
The Tealium First Party Cookie Sync solves for this issue by saving the query string parameters in an iframe cookie that can then be read and used by a Tealium iQ Profile and shared across both siteA.com and siteB.com.
First Party Cookie Sync allows tracking across multiple domains so you can understand your customer's complete journey.
Prerequisites
You must upload a simple iframe HTML file to each of the sites that you want to share data between.
You must create a new profile. Learn more about creating a new profile in Managing Profiles document.
Steps
1) Profile Creation
Create a brand new profile called "cookie-sync-frame" in your account. Read the Managing Profiles document to learn how to create a brand new profile.
Your Account > Profile list should now look like this:
2) The iframe HTML file
Create an HTML file named iframe.html and place this code inside it:
<html>
<head>
<title> iframe Page </title>
</head>
<body>
<script type = "text/javascript" >
var utag_data = {
}
</script>
<script type = "text/javascript" >
( function ( a , b , c , d ){
a = '//tags.tiqcdn.com/utag/ACCOUNT/cookie-sync-frame/prod/uta g.js' ;
b = document ; c = 'script' ; d = b . createElement ( c ); d . src = a ; d . type = 'text/java' + c ; d . async = true ;
a = b . getElementsByTagName ( c )[ 0 ]; a . parentNode . insert Before ( d , a );
})();
</script>
</body>
</html>
Or download the iframe.html attached to this document.
This HTML file must be a stand-alone file. The above code cannot be added to any other file. Also remember to replace ACCOUNT in line 12 with your actual account name.
Upload this stand-alone iframe.html file to both siteA.com and siteB.com.
Remember the URLs where these iframe.html files lives. You will need this information for Step 4.
3) Setting up your Data Layer Variables
Variables that Need to be Created for ALL Profiles
For the purposes of training we'll continue using the Google Analytics variables utm_campaign, utm_source, utm_medium, utm_term, and utm_content as examples. In all 3 profiles, siteA.com, siteB.com and cookie-sync-frame, you will need to create variables in your data layer for utm_campaign, utm_source, utm_medium, cid, etc.
Add the utm Querystring Parameter variables to your data layer. Learn how in this adding data layer variables tutuorial.
Also add the utm variables as First-Party Cookie variables to your data layer. Again, learn how in this data layer lesson.
As a best practice it is recommended that you prepend your First-Party Cookie variables with "utag_main_".
Once complete your data layer should look something like this:
Variable that Needs to be Created ONLY in cookie-sync-frame
In the cookie-sync-frame profile you will need to create one more First-Party Cookie variable called "utag_main_iframes_loaded". We'll utilize this variable later in this tutorial to store the 'master' cookie that will be shared between siteA.com and siteB.com. Your data layer should look something like this when complete.
4) Site Profiles Setup
Setup for siteA.com, siteB.com, etc.
For siteA.com, siteB.com etc. use a JavaScript Code Extension within Tealium iQ and add the following code:
You'll need to update the utag.ut.domains object to specify the top level domain name (applying siteA.com, not www.siteA.com) and the path to the html file that was uploaded.
Utilizing utag.ut.iframeQueryString.push inside the utag.ut.processIFrames function (defined in the JavaScript code below), you can add whatever data points you want to capture from the current domain to sync to the other domains. The code to pull out data points will run on document complete, so you will know that everything has already been set by the tags. For example, the sample code is pulling the Google Analytics and cid querysting parameters from the URL.
//Make sure we have the ut object in utag
utag . ut = utag . ut || {};
//Specify all top level domains and the specific location for the iframe
utag . ut . domains = {
"siteA.com" : "//siteA.com/iframe.html" ,
"siteB.com" : "//siteB.com/iframe.html" ,
"siteC.com" : "//siteC.com/iframe.html"
}
utag . ut . processIFrames = function (){
//Build the querystring params
utag . ut . iframeQueryString = [];
//Capture the UTM Parameters
utag.ut.iframeQueryString.push( "utm_campaign=" + (utag.data[ "cp.utag_main_utm_campaign" ] || ''));
utag.ut.iframeQueryString.push( "utm_source=" + (utag.data[ "cp.utag_main_utm_source" ] || ''));
utag.ut.iframeQueryString.push( "utm_medium=" + (utag.data[ "cp.utag_main_utm_medium" ] || ''));
utag.ut.iframeQueryString.push( "utm_term=" + (utag.data[ "cp.utag_main_utm_term" ] || ''));
utag.ut.iframeQueryString.push( "utm_content=" + (utag.data[ "cp.utag_main_utm_content" ] || ''));
utag.ut.iframeQueryString.push( "cid=" + (utag.data[ "cp.utag_main_cid" ] || ''));
//Need to know how many iframes we create
utag . ut . iframeCreateCount = 0 ;
//Need to know how many iframes loaded
utag . ut . iframeProcessedCount = 0 ;
//Go through each of the keys in the domains object
for ( var d in utag . ut . domains ){
//Ignore the domain if it's the same as the current site
if ( utag . ut . domains . hasOwnProperty ( d ) && d !== utag . data [ "ut.domain" ]){
//Increment the count of iframes being created
utag . ut . iframeCreateCount ++;
//Create the iframe
utag . ut . loader ({ "type" : "iframe" , "src" : utag . ut . domains [ d ] + "?" + utag . ut . iframeQueryString . join ( "&" ), "cb" : utag . ut . processedIFrame , "loc" : "body" });
}
}
}
utag . ut . processedIFrame = function (){
//Increment how many iframes loaded
utag . ut . iframeProcessedCount ++;
//Check to see if we have loaded all iframes needed
if ( utag . ut . iframeCreateCount === utag . ut . iframeProcessedCount ){
//Set a cookie so that we don't need to do this again
utag . loader . SC ( 'utag_main' , { "iframes_loaded" : "true" });
}
}
//Create a window level event listener function
utag . ut . addWindowEvent = function ( evnt , funct ) {
try {
if ( window . attachEvent ) {
return window . attachEvent ( 'on' + evnt , funct );
}
return window . addEventListener ( evnt , funct , false );
} catch ( e ){
try {
console . log ( 'addWindowEvent failed: ' + e );
} catch ( e ){}
}
};
//Only add an event listener if the iframe sync hasn't happened before
if (! utag . data [ "cp.utag_main_iframes_loaded" ]){
//Once doc complete, create the iframes
utag . ut . addWindowEvent ( "load" , utag . ut . processIFram es );
}
Scope the extension to "DOM Ready" and name the extension "First Party Cookie Sync Extension".
You do not need to create this "First Party Cookie Sync Extension" within the cookie-sync-frame profile.
5) Persist Data Extension
For All Profiles
You will now need to use the Persist Data Value Extension for all 6 of your Querystring Parameter variables (utm_campaign, utm_source, utm_medium, utm_term, utm_content, and cid). Learn more about the Persist Data Value Extension. We recommend that you scope the extensions to "All Tags" and execute the extensions after load rules.
6) Setting up utag_main_iframes_loaded in the cookie-sync-frame profile
After all of the data points have been established, we need to set the "utag_main_iframes_loaded" cookie so that when the user visits any other domain configured, the iframe sync does not occur again.
In the "cookie-sync-frame" profile add another Persist Data Extension .
Name it "Set utag_main_iframes_loaded"
Scope it to "All Tags" and makes sure that it executes "After Load Rules"
What you set Persist, Duration, Update, and Condition to depends on your organization's needs.
Store in Cookie should use the "utag_main_iframes_loaded" First-Party Cookie we created earlier.
It is best practice to have this extension load last in the Extensions list.
FAQ
How do I test that my implementation worked?
On siteA.com create a URL that you can test with. Continuing with the theme of Google Analytics querystring parameters, use a URL like the one below: https://siteA.com/?utm_campaign=testA&utm_source=testA&utm_medium_testA&utm_term=testA&utm_content=testA&cid=testA.
In Chrome Developer Tools, open the Application tab, under Storage / Cookies, click https://siteA.com then over the results of utag_main cookie in the right-most section. The utm variables and their values should be captured in that cookie.
Go to https://siteB.com.
Again under Storage / Cookies, click https://siteB.com and hover over the utag_main cookie. You should see the same utm parameters and their values in siteB.com's utag_main cookie.
Alternative Troubleshooting Techniques
Within the Chrome Developer Tools Network tab, verify that the cookie-sync-frame appears in the Network window by opening up one of your profile sites, in Incognito Mode, and looking for the cookie-sync-frame.html file.
Can I use variables other than Google Analytics parameters?
Of course! The utm parameters are used as an example. You can use any key/value pairs desired just as long as you adjust the code in Step 4 and any variables in the data layer.
... View more
4 weeks ago
Below are a few examples of cookies with a custom expiration. The code snippets can be placed within a (non-preloader) Javascript Code extension. In other cases, the Persist Data Values extension is recommended.
Set Session cookie
This code snippet will create a cookie that will be removed at the end of the user's session.
document.cookie = "COOKIE_NAME=" + 'COOKIE_VALUE' + ";path=/;domain=" + utag.cfg.domain + ";expires=";
b['cp.COOKIE_NAME'] = 'COOKIE_VALUE'; // this updates the Tealium data object on the page
Set Visitor cookie (expires after n years)
This code snippet will create a cookie that will expire after n number of years.
document.cookie = "COOKIE_NAME=" + 'COOKIE_VALUE' + ";path=/;domain=" + utag.cfg.domain + ";expires=Thu, 31 Dec [insert Year, example 2034] 00:00:00 GMT";
b['cp.COOKIE_NAME'] = 'COOKIE_VALUE';
Set hours cookie
This code snippet will create a cookie that will expire after a number of hours.
document.cookie = "COOKIE_NAME=" + 'COOKIE_VALUE' + ";path=/;domain=" + utag.cfg.domain + ";expires=" + (function() {
var d = new Date();
d.setTime(d.getTime() + (NUM_HOURS_HERE * 3600000));
return d.toGMTString()
})() + "";
b['cp.COOKIE_NAME'] = 'COOKIE_VALUE';
Set days cookie
This code snippet will create a cookie that will expire after a number of days.
document.cookie = "COOKIE_NAME=" + 'COOKIE_VALUE' + ";path=/;domain=" + utag.cfg.domain + ";expires=" + (function() {
var d = new Date();
d.setTime(d.getTime() + (NUM_DAYS_HERE * 86400000));
return d.toGMTString() })() + "";
b['cp.COOKIE_NAME'] = 'COOKIE_VALUE';
function displayCookies() {
var fname = getCookie("firstname");
if (fname == null ) {
fname = "";
}
if (fname != "") {
fname = "firstname=" + fname;
}
var lname = getCookie("lastname");
if (lname == null ) {
lname = "";
}
if (lname != "") {
lname = "lastname=" + lname;
}
alert(fname + " " + lname);
}
function getCookie(name) {
var nameEQ = name + "=";
//alert(document.cookie);
var ca = document.cookie.split(';');
for (var i = 0; i < ca.length; i++) {
var c = ca[i];
while (c.charAt(0) == ' ')
c = c.substring(1);
if (c.indexOf(nameEQ) != -1)
return c.substring(nameEQ.length, c.length);
}
return null ;
}
... View more
Labels:
10-27-2020
06:58 AM
2 Kudos
Overview
The Bulk Edit tool for iQ Tag Management allows you to toggle the active state or delete multiple variables, load rules, tags or extensions all at once .
Resource URL
Add this tool to the Tealium Tools browser extension using the following URL :
https://solutions.tealium.net/hosted/tealiumTools/bulk_edit/bulk_edit.json
Description
You must be logged into Tealium iQ Tag Management to use the Bulk Edit tool. The tool works for on the following tabs: Data Layer, Load Rules, Tags, and Extensions.
To make a bulk edit:
Use the checkboxes to select multiple items.
Launch the Bulk Edit tool. The following items are displayed:
Current Tab - The tab that you are making bulk edits in.
Items Selected - The number of items selected.
Action - The bulk action to perform:
Toggle - Toggles the On/Off state of the selected items.
Drop - Deletes the selected items.
Selection Type - Allows you to select items in the Current Tab (if not already selected)
Select All - Selects all the items in the Current Tab.
None - Selects none of the items in the Current Tab.
All Active - Selects only the active items in the Current Tab.
All Inactive - Selects only the inactive items in the Current Tab.
Invert Selection - Selects ALL of the items in the Current Tab then inverts the state of all of the items.
Go! - Starts the bulk edit process.
Results
Once the process has run, a results screen will appear in the tool.
On this screen, you will see:
Failed Items - Items in red mean they have failed on the action
Success - A count and a list of the succeeded actions
Failed - A count and a list showing which items failed
FAQ
Why did my item fail to delete? Check to make sure that the item is not in use/linked to something else. For example, a load rule can fail to delete because it is in use by a tag.
Why is the Tealium Bulk Edit tool not working in the Data Layer tab? You must be in list mode in order for the Bulk Edit tool to work in the Data Layer tab.
... View more
10-26-2020
01:58 PM
Resitricted Data is an attribute property that is used to identify Attributes that contain data that should be omitted from the Customer Data Hub services Data Layer Enrichment, EventStore, and EventDB. In general, this would include information that is private or personal, protected by privacy laws, or subject to controlled access. By default, Attributes are not restricted and may flow through to a variety of destinations.
How Restricted Attributes Are Handled
The following services honor the Restricted Data attribute property:
EventStore and EventDB
Data Layer Enrichment
The following services are not affected by Restricted Attributes:
AudienceStream and Visitor Profiles
AudienceStore and AudienceDB
EventStream and AudienceStream Connectors (including Webhooks)
Helpful Links:
https://community.tealiumiq.com/t5/Universal-Data-Hub/Understanding-Restricted-Data/ta-p/17773
... View more
Labels:
09-01-2020
08:53 AM
1 Kudo
This article provides an overview of the Tealium Tools browser extension, available for Google Chrome and Mozilla Firefox.
In this article:
Table of Contents Placeholder
How It Works
The Tealium Tools extension provides a standard set of tools used to assist in managing your Tealium deployment and a powerful framework for creating custom tools or using tools shared by other Tealium users.
Once installed, the Tealium Tools window is organized into the following two tabs:
Home Contains official Tealium built-in tools.
Custom Tools Allows you to manage and run custom tools.
Prerequisites
The Tealium Tools extension is built for the following browsers:
Google Chrome
Mozillla Firefox
Official Tealium Tools
The following is a list of Tealium Tools that are built into the extension:
Tealium iQ A bookmarked link to the iQ Tag Management interface.
TLC (Tealium Learning Community) A bookmarked link to the Tealium Learning Community.
Web Companion A browser tool used to audit your tag configuration, inspect data on your site, and create and test new configurations quickly and easily.
Scan Companion A tool used to scan your site for tags that are not managed through Tealium iQ. Scan Companion is a complementary tool to Site Scan.
AudienceStream Trace Trace provides the necessary tools to put your Universal Data Hub configuration to the test. With Trace, you can observe every detail of a defined workflow, ensure attributes update correctly, rules are dialed in, and actions fire as expected. Trace works in real-time, so you know immediately what works and what needs adjusting.
Optimizely Helper Tealium AudienceStream enables marketers to discover audiences, enrich visitor profiles and stitch together customer interactions across digital touch points. Using both AudienceStream and Optimizely, users can leverage the audiences created in AudienceStream and build targeted experiments in Optimizely.
Verify Test Recorder Test Recorder is a Tealium Tool utility built for recording step-by-step workflows like checkout, newsletter sign-up, product views, etc. You record a test by mimicking page views, clicks, or mouseovers in the order that it takes the visitor to complete the workflow.
Environment Switcher The Environment Switcher is a powerful testing tool that allows you to change the Tealium files (utag.js, utag.sync.js) that are loaded on a page by specifying an environment (Dev, QA, Prod, Custom) and/or an Account/Profile.
For information about available custom tools, see List of Custom Tealium Tools.
Installing
Tealium Tools is installed using each browser's extension marketplace.
Google Chrome
Use the following steps to install the Tealium Tools extension on Google Chrome:
In a new Chrome window, go to Tealium Tools Chrome Extension.
Click + Add to Chrome.
Click Add extension to confirm. Confirm that the button now displays Added to Chrome and that the Tealium icon displays on the upper right of the Chrome toolbar.
Click the Tealium icon in the upper right of the Chrome window to open Tealium Tools and select a tool to use.
Mozilla Firefox
Use the following steps to install the Tealium Tools extension on Mozilla Firefox:
In a new Firefox window, go to Tealium Tools Firefox Add-Ons.
Click + Add to Firefox.
Read the required permissions and click Add to confirm. A confirmation displays that Tealium Tools has been added to Firefox.
From the confirmation message window, click OK.
To use and manage the extension, click the hamburger icon in the upper left of the Firefox window and then click Add-Ons.
In the left navigation window, click Extensions.
Next to the Tealium Tools description, click More. Under Automatic Updates, you can turn automatic updates off or on or keep the default setting.
Click the Tealium icon in the upper right of the Firefox window to open Tealium Tools and select a tool to use.
Managing Custom Tools
The Tealium Tools extension provides a flexible and powerful framework for using, building, and sharing custom tools. Once a custom tool is created, it can be shared and installed by other users. This section provides basic information about adding and removing custom tools.
Adding a Custom Tool
Use the following steps to add a custom tool:
Open Tealium Tools from your browser.
Click the Custom Tools tab.
Click + Custom Tool.
Click the Add Custom Tools tab.
Copy and paste the JSON URL or JSON definition object into the respective fields.
Click Add Custom Tool.
Click Close.
Click Exit. A message displays to confirm that the custom tool was added successfully.
Click Close. The new tool now displays on the Custom Tools tab.
If the tool does not provide its own logo, the initials of the name of the tool displays on the button.
Click the button for the tool to begin to use.
Removing a Custom Tool
Use the following steps to remove a custom tool:
Open Tealium Tools from your browser.
Click the Custom Tools tab.
Click + Custom Tool.
Click the Remove Custom Tools tab. A list of custom tools displays.
From the list, scroll up or down to find the custom tool you want to remove and click Remove.
To remove all custom tools, scroll to the bottom and click Remove All Custom Tools.
Click Close.
Click Exit.
Uninstalling
Google Chrome
Use the following steps to remove the Tealium Tools extension for the Google Chrome browser:
In a Chrome browser window, click More Tools > Extensions.
Navigate to the Tealium Tools extension and click Remove. A confirmation dialog displays.
Click Remove again to confirm.
Mozilla Firefox
Use the following steps to remove the Tealium Tools extension for the Mozilla Firefox browser:
In a Firefox browser window, click the hamburger icon in the upper left of the Firefox window and then click Add-Ons.
In the left navigation window, click Extensions.
Next to the Tealium Tools description, click More.
Click Remove. A message displays that Tealium Tools has been removed.
Additional Information
List of Custom Tealium Tools Detailed information about available custom tools.
Creating Custom Tealium Tools Detailed developer information and migration steps for existing utilities.
... View more
08-07-2018
02:26 PM
Great job @RavingLunatech figure it out! And thank you for posting the solution for all of us to use. Much appreciated!
... View more
07-26-2018
09:56 AM
Hello @cferson and @philb. We just released a fix for this issue. Please test and let us know how we did. Thank you and I look forward to your replies.
... View more
07-24-2018
09:44 AM
Hello @StefanLeever. I have let @iBen and @dannypentier1 know about this request. Someone should be reaching out to you shortly. Thank you!
... View more
07-24-2018
09:37 AM
1 Kudo
Hello @pascalreder. There is also this amazing post by @amarkic.
Tutorial: Designing a Different Consent Preferences Manager Box
Let us know if this helps or not.
Regards,
Kathleen
... View more
07-18-2018
08:59 AM
Hello @michaelgray. The setup is still the same for event tracking. Let us know if How To Guide: Event Tracking with Google Analytics is working for you or not. Thank you and look forward to your reply.
... View more
07-09-2018
03:37 PM
Hello @ji89065p. Have you tried @UnknownJ's example implementation found here:
Example implementation of Snapchat / Snap Pixel
Let us know.
... View more
07-02-2018
09:01 AM
Hello @mitchellt. How's this? LOL
... View more
07-02-2018
07:56 AM
Hi @mark_reddin. Let me work with @TealiumJustin on that document. Hold please...
... View more
06-27-2018
11:06 AM
1 Kudo
How did I miss this @tibor_szentmarj?!?! Great catch and thank you for letting us know.
... View more
06-21-2018
06:55 AM
Hello @william1. This sounds more like an AudienceStream question, so I am moving this post to that board. Thank you.
... View more
06-14-2018
11:03 AM
1 Kudo
Hello @Srinivasan. Thank you so much for trying to assist @ArunthathiSelvi. Much appreciated.
Hello @ArunthathiSelvi. From what I understand, you were emailed earlier this morning with the information that you required. Please let me know if you need anything else. Thank you.
... View more
06-11-2018
07:15 AM
Hello @ArunthathiSelvi. Let's see if @TealiumEdu can assist. Tealium Education, if you have a moment, please, please. Thank you!
... View more
06-06-2018
04:25 PM
Great job figuring it out @bva-developer!
... View more
06-06-2018
07:26 AM
Hello @PatrickHegnauer and @filip_lejon I am trying to get @adrian_browning here to address this post. He is quite the busy man, however, so give me a sec. #ThankYouForYourPatience
... View more
06-06-2018
07:20 AM
1 Kudo
Hello @LeroyPijlman. Thank you for all the great follow up to this post! Much appreciated.
Let me ask @jason_paddock if he can assist you with the gtag.js version of cross domain tracking. Jason, when you have a moment can you assist? Thank you!
... View more
06-04-2018
04:15 PM
Great job figuring that out @Programmer001!
... View more
06-04-2018
08:52 AM
Looking forward to hear how the debugging went @ravi_thati!
... View more
06-01-2018
06:47 AM
Thank you for the update @Krasner. Keep them coming!
... View more
05-30-2018
10:28 AM
Hi @martin_streppel. Thank you for update! Keep them coming.
... View more
05-23-2018
07:04 AM
Hello @TimWaijers. Thank you for the feedback. I will forward it to the appropriate individuals here.
CC: @TealiumJustin
... View more
Public Statistics
| Date Registered | 08-26-2015 03:24 PM |
| Date Last Visited | 10-09-2019 09:39 AM |
| Total Messages Posted | 1,003 |
| Total Kudos Received | 118 |
Kudos given to
Latest Tags
- gdpr compliance
- gdpr data protection
- general data protection…
- data protection
- eu gdpr
- gdpr
- gdpr regulation
- google analytics event …
- google tracking
- event management
- tag manager event track…
- setup events
- analytics tracking
- analytics event trackin…
- analytics events
- universal tracking
- track events
- business analysis
- business requirements g…
- requirements gathering …
- requirements gathering …
- pixel tag
- requirements gathering
- 1x1 pixel
- conversion tracking
- pixel converter
- tracking pixel
- swift programming
- email marketing
-
Products
- Tealium iQ Tag Management
- Tealium EventStream
- Tealium AudienceStream
- Tealium DataAccess
- Tealium for Mobile
-
Company
- Tealium.com
- Blog
- Careers
- Contact Us
- Events
Copyright All Rights Reserved © 2008-2020