-
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 mike_anderson
10-12-2020
User Recent Badges
10-16-2015
12:01 PM
Brian, Josh is spot on with his post. I would utilize resource locks to keep your data layer protected, or I guess "locked". This allows anyone to use the items for rules, mapping, etc but only allows the users with the specific lock permissions to edit the data layer items. If you think it's needed, we could add an additional level of permissions around creating data layer elements, load rules, etc. But candidly we wanted to have a simpler, more flexible security model utilizing labels and locks rather than having dozens of permission checkboxes. We could also potentially add action type filters to the "Versions" tab that allowed operators to look for tag additions/removals, template updates, data layer items, etc. This would at least allow you to audit your team and their activity at a more granular level.
... View more
10-14-2015
01:22 PM
Here are a couple articles around the different data source types Data Source Types
and the Data Layer Tab within TealiumiQ Data Layer Tab In short, we do automatically grab all the variables and values from the query string. Our method outperforms the getQueryParam call as that call reads the entire URL, looks for the token starting point, looks for the token end point and takes the substring value and returns it. Each time you call getQueryParam this happens, and as you'd imagine this function just benefits the Adobe Analytics tag and no others. We parse the URL once, tokenize the values and make them available to each tag. To utilize these, simply go to the "Data Layer Tab" in TealiumiQ, add a "Data Source", enter the query param key into the "Source" field, and select "Querystring Parameter" from the "Type" dropdown. The Tealium tag will now look for that query string parameter, store it and make it available. This value can now be use to influence "Load Rules", can be "Mapped" to any of your tag vendors and can be used in "Extensions".
... View more
08-03-2015
10:55 AM
Create a data layer element of "UDO Variable" type and name it something like "subdomain". Then using Extensions, create an Advanced -> JavaScript Code extension.
Scope the extension to either one tag, or to all if you want this data point globally available.
Paste this preferred code below into the extension editor. (Making sure whatever you name the UDO variable is the same as line 2: UDO Variable "myname" -> b.myname)
Extension version scoped to global or a tag vendor for tracking the subdomain in your tag vendors:
var arr = location.hostname.split('.');
b.subdomain = arr[0];
If you want to be able to use this subdomain value to be used within load rules, then you'll need to scope this extension to "Pre Loader" and instead of "b" you'll just add the value directly on to utag_data.
Extension version scoped to pre-loader for tracking the subdomain in your tag vendors and usable within load rules (This assumes your page level data object is named utag_data):
var arr = location.hostname.split('.');
utag_data.subdomain = arr[0];
... View more
07-20-2015
10:14 PM
Honestly, I think it's easier to do because we show you how to put the proper hooks in place. Normally you would tag a Universal Data Object for each page on the site. For Angular you're doing the same thing but you define a UDO with each callback. If you can make that process part of the application, this becomes really easy. We can walk you through best practices of what to do so you don't have to revisit the code after the initial implementation.
... View more
07-20-2015
10:10 PM
Yes we do. Reach out to your account manager and they can get you setup with our Angular plugin.
... View more
07-10-2015
10:24 AM
tags.tiqcdn.com should be enough for tags. There are some tags (like Google Analytics) where you can choose to have the JS file Tealium hosted or vendor hosted. You'll want to choose Tealium hosted, or you'll need to add firewall filters for the various vendor domains.
If they need access to the Admin Console, you'll need access to
my.tealiumiq.com
community.tealiumiq.com
tags.tiqcdn.com
... View more
07-27-2014
10:55 PM
The easiest way to get custom javascript in is to create an extension for this. In the Extensions tab, you can add an Extension. This will bring up our Extension Marketplace. On the Advanced tab, you'll see an extension named "JavaScript Code". Adding this tag will give you a script editor window to paste your JavaScript code.
What you need to decide is when you want this code to run. For all pages, you can select "All Pages" as the scope. If you want to delay when this code runs until the DOM is ready, you can select "Dom Ready" as the scope, and if you want this code to run before any of the Tealium code runs, you should select "Pre Loader" as the scope.
All Pages is likely fine for the scope based on my guess.
Giving the added extension a recognizable title, you can publish the deployment out, go to your website, launch WebCompanion and see if the extension fired successfully. If you don't have WebCompanion installed, click on your email address at the top right of the TealiumIQ interface, click the WebCompanion menu item and follow the steps to install it.
... View more
07-05-2014
07:18 AM
Luca,
This is a very interesting observation. Currently the utag.sync.js doesn't support switching environments based on the Web Companion directive. This is something we just haven't added in. I'll get this in the queue of things to build, it's a great request.
In the meantime, any one of our services team members can put in place the code directly into your template to handle this.
If you need this immediately, let me know...I can write it for you as well...
... View more
03-28-2013
12:24 PM
No, Dan and Justin are correct with the relative paths. The path will be relative to the container page URL and not our CDN.
... View more
03-28-2013
11:57 AM
Joe, one of our solutions guys may have something better, but you can try this. Add your production version of Opinion Lab, then duplicate it twice once for Dev and once for QA. Set the CSS paths for each Opinion Lab instance respectively. Go into edit mode for the tag and under Advanced Settings for the tags there is a "publish to" configuration. Set the dev instance to publish to dev, and not to qa and prod, rinse and repeat for the other two tags. You should have a situation where when publishing to dev the Opinion Lab Dev tag publishes with the correct CSS path, etc.
We have another feature that is coming out which is target (dev, qa, prod) specific configs for each tag. When this is released you'll be able to enter specific configurations for each target environment. This will be helpful when you have different accounts for different environments.
... View more
02-27-2013
05:32 PM
I cut down the publish history to the last 30 versions. I still have all the data if you need it, but the last 30 should be sufficient. This is a very big profile. I was able to get it to load faster, but I'm still not happy with the results. We're moving in the direction of having these things load on demand, but for right now we load the entire profile. We'll put the enhancement in place to load the history of the last N versions by default soon. Until then, it's a bit faster. You have some JavaScript code extensions in place that are un-used. Anything you can do to cut down the profile size will reduce the load time.
... View more
02-27-2013
03:49 PM
An easy test would be for us to copy your profile over, and remove all but the last 10 publishes and see what happens.
... View more
02-27-2013
03:49 PM
I don't think the delay is a result of the tags or extensions, or even the network. It looks to be a JSON parsing issue once the profile is retrieved, and what is different with yours is you have a lot of versions, and we keep track of a lot of version history.
... View more
02-27-2013
02:19 PM
Landin, we're investigating. We've looked at other profiles and they load very fast but the aaa/main profile does seem to take longer than expected. I benchmarked against our known largest profile and the largest profile loads faster. It could be a indexing issue on the datastore, but rest assured we're on it.
... View more
02-27-2013
02:02 PM
Which profile is experiencing this issue? The overall loading of the profile should be based on basically just the size of the profile. If there is a lot of publish history for example, or a lot of large code extensions, the load of the profile may take longer, but it still should be very fast.
... View more
Public Statistics
| Date Registered | 09-01-2015 05:04 PM |
| Date Last Visited | 10-12-2020 12:50 PM |
| Total Messages Posted | 63 |
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