Channels Extension...two issues: 1 - Channels are being populated from on-site page to page navigation. Shouldn't this only populate from off-site landings? 2 - I have "allow repeat channel responses" unchecked but am still getting repeat channels.

Bronze Contributor
Bronze Contributor
Channels Extension Issues
2 REPLIES 2

Channels Extension...two issues: 1 - Channels are being populated from on-site page to page navigation. Shouldn't this only populate from off-site landings? 2 - I have "allow repeat channel responses" unchecked but am still getting repeat channels.

Tealium Employee
Hi Kevin, 1) I believe what you want to do is set the load rule for when this should run. To set this for the extension, move to the "Attribute Period/Population" tab and select a load rule from the "Data Source" drop-down option. This uses load rules defined in the "Load Rules" tab so be sure you have something setup before assigning the load rule. My assumption is that you'll create a load rule that uses multiple or conditions such as: querystring - contains - aff=cj or querystring - contains - aff=pj or querystring - contains - aff=lc This will allow the extension to run only in the 3 instances above which is much more strict - and also not be not as likely to match randomly. You'll also want to make sure the condition in that applies each Channel Name is strict enough that a random match won't occur. In regard to your off-site landing question, I presume that you're referring to when a customer clicks a link in an email and is redirected to the client website. If you are not, then most likely we can't track this type of request because Tealium is not loaded on the site from where the user originated. I guess I'm not quite clear on the question so I just wanted to provide a bit of clarification from my side. 2) I'm curious if you are just seeing the same Channel for some of the originator and closer values. This is normal considering a Channel can span several output if only a few channels have been used. If you are okay telling me the account and profile I can take a deeper look. Or feel free to contact your account manager and they can have this looked into more. Be sure to provide a few sample URLs that you are using so that we can test with a true channel redirect. Just a side note in case you weren't aware, there is a lengthy post about this extension that can be read here https://community.tealiumiq.com/posts/553333. Please let me know if this helps.

Channels Extension...two issues: 1 - Channels are being populated from on-site page to page navigation. Shouldn't this only populate from off-site landings? 2 - I have "allow repeat channel responses" unchecked but am still getting repeat channels.

Gold Contributor
Gold Contributor
Hi Kevin, I'm also using the Channels extension, though found the extension needed a lot of bespoke work to get working as I want (trying to mimic the Adobe Analytics "channel stacking" report that Adobe Consulting configure). I'm almost there with some great help from Tealium's support team. I wanted to record the channel in a stack each time a visit starts (PPC, display, natural search, affiliate, social, redirects, email etc) and also record the channel each time someone goes to another site and then back to my site within the same visit. Eg, I may start a session using PPC and check out a competitor site a few mins later and then come back to my site again via PPC (perhaps using the same or a different adword click). To do this I needed: - An extension for a list of social site referring domains - Another for natural search (Adobe Analytics is great here as it maintains a list for you) - A campaign code syntax per managed channel (similar to Dan's comment above) - A cookie to determine if the page view is the 1st page view in a visit; which is then used to stop unwanted channel values from firing on each page view - Set the "channels" hierarchy rules in the Channel Extension. This is very messy / horrible process as you can't add rules in the position you want without deleting and starting again (I believe an update may be offered to allow drag-and-drop) I should have it properly working next week. Let me know if you need any more help. If it helps, the cookie extension code is: if (typeof utag.loader.RC('first_page_view') === 'object') { var browserName=navigator.appName; var expirydate= "expires=0"; if (browserName=="Microsoft Internet Explorer") { expirydate=''; } document.cookie = "first_page_view=false" + ";path=/;domain=" + utag.cfg.domain + ";"+ expirydate; b.first_page_view='true'; }
Public