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

Universal Analytics compatibility #8

Open
mbaersch opened this issue Mar 19, 2021 · 4 comments
Open

Universal Analytics compatibility #8

mbaersch opened this issue Mar 19, 2021 · 4 comments

Comments

@mbaersch
Copy link

if Universal Analytics instead of GA4 tags are used to send requests to the server-side container, simple tracking for pageviews and even most events is possible (when the UA event action is named properly). But as UA does not allow to send individual event parameters like GA4 there is no way to set the "value" for the "Purchase" event. The information still exists in the event model when using UA but is called 'x-ga-mp1-tr'. Getting the value from eventModel.value || eventModel['x-ga-mp1-tr'] would at least allow some data to get through when a UA purcase e-commerce event hits the server container.

@Bukashk0zzz
Copy link

As workaround for now you can use my Facebook server side tag https://github.com/gtm-server/facebook-tag

It supports GA4/UA clients and works with _fbc cookies.

@mbaersch
Copy link
Author

thank you but I already have my own tag. This is about avoiding those patches and make this one more useful

@FDivecha
Copy link

You can try sending up to 4 parameters in the UA event category, value etc. This isn't a "clean" solution, but you can make it work. Another alternative is to simply create a dummy GA4 account and use it to pass all the parameters you need.

@mbaersch
Copy link
Author

You can try sending up to 4 parameters in the UA event category, value etc. This isn't a "clean" solution, but you can make it work.

That's what I do right now... But I do neither love to use a patched FB tag nor tagging with a dumm y GA4 tag client-side. I guess we all have to wait until there Is a FB client-side tag that can send all hits in parallel to FB and a local endpoint at the same time.

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

3 participants