I’m trying to setup the event deduplication, and have installed the Unique Event ID variable into my Tag Manager Setup. I have then added the variable into the GA tag, and the Facebook tag. The idea is that the GA tag is managed server-side, and the event ID is ingested into the server-side FB tag. All that works well.
My problem is weird though: when I debug the web container, I see a different unique ID value in the FB and GA tag. Obviously that’s not good since the value should be the same.
I attach a bunch of screenshots showing the tag set up and the tag runtime values.
Could someone point out why the values of the “Unique ID” is different? It does fire on the same “Event: Container Loaded” event so I’d expect the same value. What am I missing?
Basically, I would have expected that the variable would have a unique value for each event fired (so 1 for “DOM Loaded”, 1 for “Window Loaded”, etc.) but would stay the same for all TAGS across a single event - that’s the idea right?
Thank you Enrico.
I do have both tags with “All pages” trigger, and I do see them triggering at the same event step called “Event: Container Loaded”.
Not completely sure what you mean by “Google Tag activates consent initialization” : do you mean selecting an option in this section of the Tag Manager UI? (see screenshot). I tried the “No additional consent required” just now but still have the same issue of the ID being different between FB and GA4
Hey, again, thanks for the help.
The two tags already have the same trigger, and both have the “once per page” setting also matching.. so hence the confusion..
Yay !! Success !
I removed the Google Optimise which indeed is long deprecated, and now it works as expected. Thanks so much for the help, super happy it all works now.
