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

Purchase events are sent with "firebase_conversion" parameter set to 1 #32

Open
blazejstarosta opened this issue Jun 9, 2023 · 1 comment

Comments

@blazejstarosta
Copy link

I'm trying to narrow down an issue with event attribution.

I'm collecting most of the GA4 data on the front-end of my website, however Add to cart, Remove from cart and Purchase events are being sent through Measurement Protocol. In order for these events to be properly attributed to the ongoing GA4 session and user actions, I'm taking the session_id from ga cookie and I'm sending it along with the timestamps with the forementioned events.

According to Simo Ahava, this should work: https://www.simoahava.com/analytics/session-attribution-with-ga4-measurement-protocol/

And it does seem to work fine with "add to cart" and "remove from cart" events. When I created a view in GA4 that shows me, for example, all kinds of statistics about acquisition from organic sources, the add to cart events show up assigned to specific sources.

However, none of the organic sources show any purchases. As a matter of fact, all the purchase events are being attributed to "Direct" source, without exception. None of them have been attributed to anything else.

That led me to investigate the events in GA4 and I've noticed that all the "purchase" events sent from this library are marked with the parameter "firebase_conversion" set to "1". This parameter is not set at all for Add to cart and Remove from cart events.

When I googled, I found few unanswered questions about firebase conversions always being attributed to "Direct".
Could this be the culprit? Since firebase conversions are dedicated for in-app purchases, it's possible that Google is overriding these conversions as "Direct". Is there a reason for the "Purchase" event to be sent with this parameter? Is it possible to disable it?

@Luxato
Copy link
Contributor

Luxato commented Jun 20, 2023

@blazejstarosta I am currently on the exact same issue. All my conversions are being attributed to direct despite sending correct client id, session id and timestamp.
It seems like though that the firebase_conversion is something that's always there and it's not sent via this library as a parameter.
Did you manage to solve this issue? I would appreciate any advice.

Thanks.

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