-
Does anyone truly understand how to best configure Google Server Side firing?
On mobile so apologize for formatting in advance.
So on Facebook it’s very well documented around how to set up client and server side firing, but Google just seems like a mess.
From what I can tell there are two key aspects to setting up server side on Google…
Part 1: GCLID Upload
– API upload of Upload Click Conversion
– Enhanced Conversion data
– Sending transaction id to client side pixel to dedupePart 2: gtag (this is where it gets a bit confusing)
– Adjust tag behavior based on consent
– Add in the UA account
– Pass ecommerce data into the gtagFrom what I’ve read it appears that the steps above in part 2 are required to pass WBRAID, but what is the true benefit here of doing these? How will this benefit reporting on WBRAID? Or do we just wait until the upload similar to GCLID is ready?
I’m just very unsure about part 2 here or if I’m missing anything in this strategy overall. Any insight would be awesome.
Thanks in advance!
Sorry, there were no replies found.
Log in to reply.