I definitely think you are on the right
I definitely think you are on the right track. But haven't done your setup, only had non enhanced conversions w/ Zaraz. I would like to get to the setup you are targeting at some point. I switched recently to Google Tag Gateway in Cloudflare, and disabled the Zaraz third-party tool for GA4. Need to baseline that and ill probably circle back after that.
Seems correct with sending the user_data payload, which minimally as you probably know must have the "email" key (and value), and also you can do: "phone_number", and address too (I forget the format).
One area that you may have issue with is how the email (and phone and address if you send those), I believe need to be hashed. I assumed that Google only hashes these values, (but also found out later that you can hash it yourself on the client side with SHA-256 and it needs to be normalized based on their expectation too.
Once user_data object is properly hashed, you should be OK using Zaraz + GA4 third-party tool.
5 Replies
I follow as google recommends and obviously in well formatted way as like gtm datalayer.
And I am manually hashing the user param and assign the values as event property in tool settings. However, i am still confused about auto mapping it as like e-commerce params.
I don’t want to utilize gtag gateway, cause there’s no point loading up gtm scripts and i am moving my analytics completely to server side and at some point i feel like browser based tracking is going to be old fashioned (but not at this moment or any soon) then basically zaraz comes in.
And using zaraz i can send 99.99% accurate data server side + 1st part cookies of analytics eg: Meta Pixel.
If i use GTM ( i still use gtm, since there’s production sites pushing data for last few years, so migration cannot be executed ,) I usually spin up vps for gtm sst and used to set gtm browser + server side tracking.
With zaraz we can only do SST and it’s fine when the paylod has sufficient parameters for pixels.
And my problem isn’t about hashing user data, mapping it to user property in ga4. Zaraz team said only few words in their docs about the user property.
https://developers.cloudflare.com/zaraz/faq/
How about try adding each field individually, so:
up.name, etc. (I don't work at Cloudflare, just trying to help)