`zaraz.track` payload transformation
One thing I am struggling with a bit with Zaraz is the control over how my
zaraz.track event payloads get transformed for each individual tool (e.g. GA4 vs Meta). There are some events that I may want to be translated over to a "standard/recommended" event on Meta or GA4 but I'd like to use our own event schema to dictate how those events are translated. Is this something that you'd use the context enricher for?5 Replies
For example. Lets say I have an event named
form_submission but I want it to be sent to Meta as Lead and GA4 as generate_lead
Context enrichers seem to be the way to go here the more I read through the docs.Unknown User•4mo ago
Message Not Public
Sign In & Join Server To View
yeah i found the worker variable types shortly after sending this.
Unknown User•4mo ago
Message Not Public
Sign In & Join Server To View
The way i typically like to do this is via transforming the values and not relying on a ton of unique actions/triggers per platform. Most platforms have similar data models but some just need slight tweaks to the data structure here and there. We're still leveraging a TMS to implement the
zaraz.track calls (GTM proxied via our own custom cloudflare worker). We typically have a list of our own standard events that map to some of Google/Meta/TikTok etcs... odd choices for naming conventions.
I typically find using an event map easier than the tedious management of triggers/actions if avoidable