08-31-2018 09:40 AM
I'm replacing our existing Floodlight tags with the gtag.js versions. I've configured the tags as required but when I go to test, I'm only seeing requests for the Global Site Tag portion and not the Floodlight portion.
I also tried adding the tag as a custom container using the pixels provided by Google and the tag works correctly, showing pixels for both the Global Site Tag and Floodlight portions.
09-05-2018 11:14 AM
Interesting behavior when you implement with a custom container, @MichaelMerritt - maybe it's worth a support ticket to make sure the integrations remain compatible. Many of us need to run these pixels in parallel, it would be great to have more info on compatibility or to know when it's necessary to use custom containers.
09-05-2018 11:15 AM
I'm having the same problem but I have a solution that only sort of "works" (it doesn't pull back the referrer URL in the request URL). The support folks seem to be avoiding this question as I've read through at least 20 threads with no solution.
Set up a Doubleclick gtag.js template as your "global" tag. I've only included my advertiser ID, allow custom scripts set to yes and standard counting. Apply an all pages rule to this and you have the global snippet.
Set up a second tag (and for every subsequent tag) using the standard doubleclick floodlight template, proceed as you normally would and apply the page specific load rule. I've found this has worked but doesn't function exactly the same as it would with a direct implementation. After some more testing, I may just do these all in custom containers until there is an actual solution but it looks like it will track conversions properly.
09-05-2018 11:16 AM
These reports are interesting because the August release notes state that bundling issues have been addressed for both tags mentioned here.
09-05-2018 12:43 PM
Interesting. Perhaps the issue that they fixed was regarding layering in multiple Google accounts (DCM, AdWords, DS, GA) into a single gtag.js container? I'm really not sure as today was my first time playing around with these tags in Tealium, but there are definitely some kinks that need to be worked out.
09-05-2018 04:13 PM
Sorry, it looks like this implementation still does not work properly. The floodlight should recognize the presence of the 1st party cookie dropped by the global tag (gclaw). It should automatically add this into the request URL but it does not. Unfortunately, this is still broken. I'll let you know if I find another solution but I think Tealium needs to address this. The issue is most likely that this is firing from an iframe and can't read the domain cookies.
09-06-2018 08:46 AM
08-20-2019 01:13 AM