-
Expand/CollapseMenu
- TLC Home Home
- Discussions Discussions
- Documentation Documentation
- Knowledge Base Knowledge Base
- Education Education
- Blog 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.
- About fiann_ohagan
07-17-2017
User Recent Badges
12-20-2016
03:15 PM
3 Kudos
@ahrasch we actually have found a limit on the number of files, although hopefully you won't hit against it.
There is no limit imposed by Tealium, but there is a limit of 300,000 files per Tealium profile because they all go into a single folder on the CDN server. The CDN imposes a limit of 300k files in a single folder.
If you hit close to this limit, then you will need to find a way to combine the data down into a smaller number of files.
... View more
10-30-2015
01:05 AM
1 Kudo
Hi @steve_bowsher this code is implemented in a JavaScript Code extension, rather than in the template of a custom tag.
Within any JavaScript extension, you have access to the "b object" which is a reference to the data object (utag_data) for the event that has been passed.
So you can reference any data field like this:
{ scope:'page', name:'section', value:b.page_name, mobile:true }
Note that it's not in quotes, because you want the value of b.page_name (or whatever data layer value you choose) rather than the literal string "b.page_name".
I hope that helps. I can do this for you, or you can give a go and see how it works out.
Fiann
... View more
09-24-2015
11:30 AM
1 Kudo
Question
Can I use an array variable in a Load Rule with a condition such as CONTAINS?
Answer
Short answer: Yes.
Long answer: The JavaScript code generated by Load Rule conditions uses the toString() method which will convert an array to a comma-delimited string. A Load Rule that uses the CONTAINS condition, for example, will convert the variable to a string using toString() , then use indexOf() to find the desired value within the variable.
> product_name = ["Nexus One", "Samsung Razor", "Apple iPhone"]
["Nexus One", "Samsung Razor", "Apple iPhone"]
> product_name.toString()
"Nexus One,Samsung Razor,Apple iPhone"
> product_name.toString().indexOf("Apple")
24
... View more
Labels:
08-21-2015
04:12 AM
If you want to fire more than one Adwords tag on the same page, then the lookup table won't work.
If you have two values you want to look up (e.g. a conversion id and an account value) then there is a solution but it's a bit of a hack. You can put both values in the output field of the lookup table with a separator like this: 123|xyz.
Then you can use a second extension, either a Set Data Value extension or JavaScript code equivalent, to split on the | separator and populate two separate values.
It's a bit more complicated but it can still be easier than managing a large number of separate tag instances, so we sometimes do this for Floodlight tags where you need to have a different type and category for each instance.
... View more
08-20-2015
01:56 AM
Hi Colin,
The best way to do this is to use a Lookup Table extension. https://community.tealiumiq.com/t5/Tealium-iQ/Lookup-Table-Extension/ta-p/13708 For an Adwords remarketing tag, you generally have one field which you want to map to the tag, which is the conversion label. So here are the steps you want to take:
Create a new Adwords tag and set the load rule to All Pages.
Create a new Data Source called adwords_conv_label and map this to the conversion label on the Adwords tag.
Create a Lookup Table extension. Set the scope to your Adwords tag. The input can be whatever you want but it will usually be the url pathname or possibly a page category variable from your data layer. The output is the adwords_conv_label variable. If you have a few to fill in, it may be easier to set up the data in an Excel spreadsheet and then upload it to Tealium as a CSV file.
Finally, create a second extension of type JavaScript Code, and again set the scope to the Adwords tag. Make sure that it comes after the lookup table in the list of extensions (you can drag-and-drop to reorder them). This will make sure that the tag doesn't fire if there is no entry in the lookup table that matches the current page. Put this code in the extension: if (b.adwords_conv_label === "") { return false; } The return false tells Tealium not to fire this tag.
I hope that gets you started, but if you need some assistance setting this up then reach out to your Account Manager and they'll be able to help out.
... View more
06-10-2015
07:44 AM
Scenario: You have some HTML that looks like this, which triggers a download when you click the link: <a href="#" id="download-button">
<img src="book.png" id="book-image">
<script language="JavaScript">
if (window.picturefill) {window.picturefill();}
</script>
Download user guide
</a>
You want to record the text inside the <a> link tag in your web analytics reports. Typically it's ok to use something like this, either in a JavaScript Code extension, or using a jQuery onHandler extension: // Capture clicks on the button and fire a link event
// Set page_name using jQuery.text()
jQuery("#download-button").on("click", function (event) {
var link = jQuery(this);
utag.link({
interaction_event : "download",
page_name : link.text()
});
}); This code creates a "link" event with two fields in the data object: an event and a name for the button that was clicked, which should be the visible text on the link. You can't use jQuery.text() Unfortunately the method jQuery(node).text() doesn't just give you the text of the link. It also catches the content of the <script> block. So the page_name comes out as: "if (window.picturefill) {window.picturefill();} Download user guide" You can't use innerText One possibility is to use the browser's innerText property in Internet Explorer and Chrome. However this is not supported in Firefox, so you need to use a fallback method: // Set page_name using textContent or innerText
jQuery("#download-button").on("click", function (event) {
var link = jQuery(this);
utag.link({
interaction_event : "download",
page_name : link.textContent || link.innerText
});
}); And in Firefox, the textContent property also includes the content of the <script> node so that it gives the same content as above. This solution works in IE but not in Firefox. Solution: use jQuery to strip scripts So here is the cross-browser answer. Use jQuery to strip out the scripts, and then collect the text content from the inside. // Full solution using jQuery to remove scripts
jQuery("#home-button").on("click", function (event) {
var link = jQuery(this);
// clone the node, strip out scripts and get text
var name = link.clone().find("script,noscript,style").remove().end().text();
// remove whitespace and new lines
name = name.replace(/\s+/g, " ");
// remove any whitespace at the start and end
name = jQuery.trim(name);
utag.link({
interaction_event : "download",
page_name : name
});
}); And now, the page_name contains just the visible text as expected. "Download user guide" Conclusion It's not common to put a script inline inside a HTML element that you would like to collect. But if you do run into this situation, I hope this solution helps you.
... View more
06-02-2015
01:47 AM
Hi Ronaldo, for this case you will need to use a JavaScript encoding rather than an html entity encoding.
My colleague Craig Rouse has been using this tool which works very effectively: http://rishida.net/tools/conversion/ - use the JavaScript Escapes tool at the bottom of the page.
For example it will convert the string in your code from "Dt Publicação" to "Dt Publica\u00E7\u00E3o" which is the Unicode encoding for the string, and this should give the correct data in your reports.
Hopefully this will not be necessary in the future when we fully support UTF-8 in extensions.
... View more
04-08-2015
05:55 AM
1 Kudo
It's possible to do this, but only using some custom JavaScript code. There are 2 steps, and we can put both of them in a single JavaScript Code extension. 1) Fire the single tag. You can do this using the syntax utag.view({ ..data.. }, [ tag UID ]); There is some more information here How to trigger exclusively one tag You could use a setTimeout or an event listener on the onLoad event to fire the utag.view(); 2) Suppress the normal firing. If you put "return false;" in a JavaScript Code extension, then the tag that it is scoped to will not execute.
... View more
03-19-2015
10:21 AM
Hi Alessandro, the best practice way to do this will be to turn on the "Clear Vars" setting on the SiteCatalyst tag and then re-set all the data when you call utag.view(). Otherwise you are going to have unpredictable data being sent.
Alternatively you can just set s.events="" directly, or tealium_s.events="" if you have a custom 's' object name.
... View more
03-04-2015
04:53 PM
Real time performance monitoring tools provide the capabilities needed for detailed performance and advanced error analysis and the ability to correlate the results directly to business metrics, such as conversions, page views, and revenue.
This article covers the following topics:
Table of Contents Placeholder
How it Works
You can easily add, implement, and manage the Akamai mPulse JavaScript tag through Tealium iQ. You can then create load rules to determine when and where to trigger this vendor and use the mapping feature to control which data points are shared with Akamai.
Tag Configuration
Use the following steps to add and configure the tag:
In Tealium iQ, click the Tags tab.
Click + Add Tag.
Enter Akamai in the search field.
Next to Akamai mPulse, click + Add.
In the Vendor Configuration field, enter the API key supplied by Akamai. This key is the unique identifier for your data.
Expand Advanced Settings. These settings are not required for most tags, but are needed for Akamai.
Set the Wait Flag to No. This means that the tag will be triggered as soon as the Tealium utag.js library file loads.
Set the Synchronous Load Type to No.
If set to Yes, the tag will not fire.
Load Rules
Use the following steps to apply load rules:
Click Next to advance to the Load Rules tab.
From Load Rules, click the Load on All Pages checkbox. This step is required to enable the tag to be bundled when configuring the Publish settings in the following steps.
Click Finish.
Click Save in the upper right corner but do not publish.
Configure and Publish Settings to Optimize Performance
Use the following steps to configure and publish settings that will optimize tag performance:
Click Save/Publish in the upper right corner. The Save/Publish dialog displays.
In the upper right corner of the Save/Publish dialog, click Configure Publish Settings. The Publish Configurations dialog displays.
There are many Publish Settings options described on the Tealium support site. For Akamai mPulse, you can activate the following two (2) optional settings for Akamai to improve tag performance.
From the Publish Configurations dialog, click the General Publishing tab.
Scroll down to Performance Optimization and set the following to ON.
Bundle Tags Loaded on All Pages Setting this option to On ensures that any tags that load on the All Pages load rule are included inline in your utag.js file instead of in a separate, numbered file. Although your utag.js file will be larger, it will remove one (1) http request (server call) as the page loads.
Minify Tag Templates Setting this option to On applies "minification" to the generated JavaScript, which removes unnecessary whitespace so that the file size downloaded is smaller.
Click Apply to close the Publish Settings dialog. You are now back at the Save / Publish dialog.
Publishing and Testing
As a final step, publish and test your new tag as follows:
From the Save/Publish dialog, click Save As.
Using Save As saves your change as a new version, which enables you to roll back your changes if needed.
Once the updated utag.js hits the CDN, you can see Akamai firing in the browser.
You can test that the tag is performing as expected by using a tag monitor, such as Ghostery, or you can view tag activity using your browser network monitoring tool. You will know that the tag is firing correctly if you see the following request firing:
Look for the request at http://c.go-mpulse.net/boomerang. The key displayed will match the API key you entered when you configured the Akamai mPulse tag.
... View more
02-27-2015
08:52 AM
Calling utag.view() will fire any tags with load rules that match the data you pass in. This will include any tags with the All Pages load rule.
If you only want to fire SiteCatalyst and you don't want other tags to fire, you can still call s.t() directly, rather than calling utag.view(). Depending on how your profile is set up you might have a different name for the 's' object. You can see this on the SiteCatalyst tag, in the config panel on the left hand side, called "S-Object Name".
If it's blank, then you should call s.() and if it has a different name then call that name, e.g. tealium_s.t()
... View more
02-26-2015
06:31 AM
That should be all you need. If it's not triggering SiteCatalyst, then you should put in a request to your account manager to get some help debugging it because it sounds like there is an issue specific to your pages.
... View more
02-26-2015
05:02 AM
Steve, you can call utag.view() to trigger a page view event, this will trigger s.t() on the SiteCatalyst tag. There is some documentation here: https://community.tealiumiq.com/t5/utag/utag-link-and-utag-view/ta-p/11888 In general, if you are updating the global utag_data object with new data, then you will want to call utag.view(utag_data) which will send the data object to the event. Alternatively, if you don't want to persist everything from the previous page view, then create a new data object for the event and call it like this utag.view({ data : "value" }).
... View more
12-30-2014
12:44 AM
Another possible solution is to add a Javascript Code extension in your Tealium configuration to fire a custom event.
There are two possible scopes that you could use:
* Preloader scope: this runs as soon as the utag.js file loads, but before the utag object is fully initialised.
* DOM Ready: this runs after the utag object is initialised, and before the tags all fire. At this point the utag object will exist and the utag_data object will be populated. Unlike the All Tags scope, it only runs once, it does not get executed each time a view event fires.
I would suggest experimenting with firing the Angular callback / event from code in the DOM Ready scope. Please let us know how you get on, if it works well then it could be a good candidate for a new standard feature!
... View more
11-21-2014
07:31 AM
You can map a single data layer variable to two outputs in the same tag. It will appear once in the list, but with 2 output mapping lines.
In the destination chooser, the point-and-click interface does not allow you to make multiple selections from the list. However, you can just type directly in the text box with a comma between the entries.
... View more
10-21-2014
02:31 AM
Hi Alessandro, yes you can do that.
The IE8-compatibility build at https://raw.githubusercontent.com/lodash/lodash/2.4.1/dist/lodash.compat.min.js is about 30Kb so that's not excessive.
As you say, you can just copy and paste the whole thing into a preloader extension.
... View more
10-20-2014
07:06 AM
This is easy to do in Tealium. You just need to create 2 instances of the Google Analytics tag. Apart from the account id, where you enter your UA-1234-1 account number, there are two other important settings. First, make sure that in the "script source" setting, you choose Google (external). This prevents you loading the whole library twice. Secondly, give each of the trackers a distinct name. For example if you have an account for the site and a roll-up account to collect data from multiple sites, you could call them "global" and "local". The two trackers will now collect the same page view data. If you want to collect different event data, there are two ways that you can achieve this, but they both involve using a custom JavaScript code extension. One method is to create an extension scoped to the tag instance which checks for relevant events and returns false if it's not going to record the data. You can insert your own condition here:
// a is event type, "link" is an event
// b is the data object
if (a === "link" && b.local_event === false) {
return false; // do not collect this event
}
The other alternative is to create the events explicitly in GA style:
jQuery("button#add-to-basket").on("click", function () {
ga("local.send", "event", "add-to-cart", "clicked");
});
In the second example, the prefix before the send is the name of the tracker.
... View more
09-15-2014
09:05 AM
If you are using a JS Code extension, there is a variable called 'a' which contains the event type. It has the value of either "view" or "link" matching to utag.view() and utag.link() calls.
You can suppress the extension from firing by adding this at the top of the extension:
{code:js}
// only fire on view events
if (a !== "view") {
return;
}
{code}
... View more
09-11-2014
07:25 AM
Hi Jan, you can always check which CDN is currently serving your files by using this URL: https://tags.tiqcdn.com/monitor.html However, this will be different for users in a different location and may change from minute to minute. We recommend using a third party monitoring service to check the response times so that you have an independent confirmation. Keynote, Compuware (Gomez) and Watchmouse are three well known services. They request the files from their servers and report the response times and you can configure them to alert you if it exceeds a threshold. We have our own monitoring in place, but if you do spot any slow response times then please contact your account manager who can help to investigate the problem.
... View more
08-27-2014
02:01 AM
"Is populated" checks whether the variable is equal to an empty string. "Is defined" checks whether the variable is undefined or null.
In general, to get the effect you would expect, you have to always combine both conditions with an AND rule, so that your load rule says the variable "is defined" AND "is populated".
... View more
07-31-2014
09:29 AM
1 Kudo
Hi Luca, you can use mapping to send data to Test&Target in the same way as any other tag. There is no mapping toolbox because unlike SiteCatalyst for example there are no defined variables that you should use. So you can just choose the variable from the list and then type the parameter name into the text box. For ecommerce data, you don't need to map anything. If you have the Ecommerce Extension set up, then we automatically create a conversion mbox with this code: mboxDefine('orderConfirmPage','orderConfirmPage', 'productPurchasedId='+b._cprod.join(','), 'orderId='+b._corder, 'orderTotal='+b._ctotal); So this passes the order id, order total and the product ids from the basket to T&T automatically. The requirement is that the order ID is specified in the page, this is the trigger that the Ecommerce Extension uses to recognise a confirmation page. If you need more information about the ecommerce extension please refer to E-Commerce Extension
... View more
07-30-2014
07:29 AM
Hi Alessandro, we now have an alternative solution: a new configuration setting in the utag.js. Please see this article by my colleague Roshan. https://community.tealiumiq.com/t5/Tealium-iQ/How-to-evaluate-load-rules-AFTER-extensions/ta-p/13745
... View more
07-28-2014
09:11 AM
Sharon we have a few pieces that might help with this.
In particular if you are capturing the data later from the a object in the HTML then we have a diff tool that will compare the props and eVars set in the page with what is sent to SiteCatalyst. If that sounds useful I can send you the code for it.
I am very interested in setting up automated tests for the implementations that I set up so please let me know a bit more detail on some example test cases and I will be happy to help you set it up.
Fiann
... View more
07-21-2014
07:58 AM
Hi Jeremy, a quick tip for testing - it's always worth looking at the timestamp which is contained in the first line of the utag.js file, in the format "//tealium universal tag - utag.loader ut4.0.201407151556" where the last part is year-month-day and then the time in GMT time zone.
You will see this timestamp change when the update files hit the CDN.
... View more
06-16-2014
03:29 AM
Hi Sebastian, the mapping toolbox is not implemented for Piwik tags because sending custom data is not a matter of just adding query string parameters to a pixel url.
Instead they have a similar format to Google Analytics, where you append data to a JavaScript array object and this is picked up by the analytics tool. You can do this in a JS Code extension.
Here is an example from the documentation at http://developer.piwik.org/api-reference/tracking-javascript
_paq.push([ 'setCustomVariable','1','VisitorType','Member' ]);
If you have a data layer variable called visitor_type, you could put this code in a JS Code extension and you would send the variable to Custom Variable 1:
_paq.push([ 'setCustomVariable','1','VisitorType', b.visitor_type ]);
In a JS Code extension, "b" is a reference to the data object, so b.visitor_type is your visitor_type variable.
Does that help solve your problem? If you have a lot of mappings to add, then we could put in a request for the mapping code to be implemented in the tag to support this.
... View more
Public Statistics
| Date Registered | 09-01-2015 05:04 PM |
| Date Last Visited | 07-17-2017 02:27 AM |
| Total Messages Posted | 57 |
| Total Kudos Received | 6 |
Kudos from
Latest Tags
No tags yet
-
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-2023