Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change this to work without needing Firebase? #2

Open
kendallb opened this issue Jan 4, 2024 · 2 comments
Open

Change this to work without needing Firebase? #2

kendallb opened this issue Jan 4, 2024 · 2 comments

Comments

@kendallb
Copy link

kendallb commented Jan 4, 2024

Zaraz has full support for Bing in such a way that mimics how the client side pixel normally sends data to Bing, so the need for Firebase to store credentials should not be necessary?

https://github.com/managed-components/bing/tree/main

As you can see all it needs is the Bing UET Tag ID and it can send all the eCommerce events over:

image

Is it possible to rework this tool to work without Firebase, or is there something I am missing here?

@kendallb
Copy link
Author

kendallb commented Jan 4, 2024

I am considering forking this project and trying to see if I can build my own template in a similar fashion to how Zaraz does it.

My question though, is how do you actually debug the code in the template to make sure it works? Is there a way to fire a break point in Chrome or something when the code runs, so you can see what it is doing? For server side tags, I have no ideas how you would do that (perhaps you just debug it old school with logging?).

@Bukashk0zzz
Copy link
Member

This tag uses Offline conversion tracking to track everything.

That means you can pass user email, phone number, name, etc., to Bing Ads.
Also, you can do all of this without cookies/browsers etc.

That's the whole idea of the tag -> Do not rely on Browser.
In our cases, we often send webhooks from CRM to sGTM and then to Bing Ads.

What Zaraz does it use cookies to store Bing click id and then send it to Bing Ads on purchase.
That requires a browser and does not allow you to send user PII data, which, from our experience, brings lower results in attribution.

Not sure that forking tag helps you in any way.
Basically, you need to write completely different tags that use different APIs etc. And sure that this is a good idea as it will have lower attribution and you will rely on not documented API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants