Outside of the built-in third-party integrations, what have you all successfully used Zaraz for? I'm
Outside of the built-in third-party integrations, what have you all successfully used Zaraz for? I'm particularly interested in whether Zaraz can be used for services that either add a lot of content to the DOM (e.g., BaazarVoice), are interactive in some way (e.g., chat bots like Gorgias), or more intensive analytics services that track user interaction (e.g., Hotjar).
9 Replies
Hi there zaraz community, I'm trying to understand how the Web API part of Zaraz could be utilised. I've inspected the code of the managed components, and it seems like the payload should be matched exactly to the integration. What exactly is the reasoning behind using Zaraz then in terms of server side? Why wouldn't I just make API calls to the native integrations from Meta (Graph API), TikTok Events API themselves?
For example, my webhook is making a call to the Zaraz WebAPI route, but this payload is only consistent with Meta Conversions API. I want to add GA4 + TikTok, etc. But does this mean I have to dive into the docs of all those and construct those payload bodies myself? I've inspected the TikTok managed component, the schema is configured as "email, phone" and not
em. TikTok also provides a Payload Converter API that enables you to POST your pixel payload and they will convert it for you.
How can I use Zaraz with just 1 body and have it figure out the payload for the 3rd party tool? Thanks
Or am I supposed to manually create actions in the dashboard and map all the variables to what I am sending? So I treat the Meta Conversions API schema as "base" and in the trigger or action thing in the dashboard i parse all the variables
I kind of expected Zaraz to be able to map pre-defined events to other providers and map the events and payload bodies accordingly
Without any extra configuration from my side
Zaraz is such a cool idea I wish there were more docs etc around it.
We are using the managed component of floodlight in our zaraz: https://github.com/managed-components/floodlight However I miss the implementation of handling parameters when I come to my site from an ad (handling the dclid parameter https://support.google.com/campaignmanager/answer/9182069?hl=en) to correctly track conversions to a specific campaign. Is this not part of the managed component? I already created an Issue on GIT but didnt get an answer yet, so I thought its maybe good to ask here 🙂 cheers
GitHub
GitHub - managed-components/floodlight
Contribute to managed-components/floodlight development by creating an account on GitHub.
Enhanced attribution - Campaign Manager 360 Help
Make sure your Floodlight activities are implemented either using the Google Tag Manager using the Conversion Linker. Learn more about the Conversion Linker in Google Tag Manager E
Is there some explanation on the earlier thread here ?
Its agnostic and should work for all of them
I currently have it working for GA4
It seems to mutate the fields to match the integration payload
if I am wrong someone please correct me
But that is what it appears to be doing
Can we get some clarity on if we fill out the purchase payload exactly how it's filled out in the docs if it will act as an agnostic payload to all integrations.
Unknown User•5d ago
Message Not Public
Sign In & Join Server To View
Can you checkout what I responded on ur message in my thread? Thanks
Unknown User•5d ago
Message Not Public
Sign In & Join Server To View