PSA Do Not Enable User Data Collection in Google Analytics 4

[@configcat]

We also ran into this bug. Our purchase events sent via the measurement protocol show up again if we include the user_data: {} in the payload (even if the user_data is empty).

[@erikbarcsay]

Thank you so much for the video and this comment! 🙏 Including "user_data" in the payload solved the problem for us too, so we don't need to create a new GA4 property.

[@kevinmclaughlin178]

Thanks! I'll check if that works.

[@pomeshan4794]

@@kevinmclaughlin178 does it work?

[@pomeshan4794]

can you describe in more detail what needs to be done?

[@wasimk.shaikh1141]

Can you please describe in detail what needs to be done?

[@dhawkings]

Can't believe this is still an issue 7 months later. I just ran into the same problem with the UPD setting. I'm using the measurement protocol but not through Sliderule. Got around it by adding user data with just the country set. Empty user data wasn't enough for me.

[@Daniel-NF]

Thank you so much for this video. Unfortunately i have just seen it and not earlier. I have set up some properties last days and i thought i am stupid because it didnt work. There was one moment where i saw realtime data and then it was away and i didnt understand why and thought i am ... ;) What a mess that even 2 months later that still happens. Thank you again!!!

[@alirezasalemy]

This seems to be a bug. After enabling User-provided data collection (Beta) for one of our properties, GA4 will now show those events with a user_id; like purchase. This has forced us to enable Device-based reporting identity because the Observed and Blended will not show those events. Enabling device-based reporting will show those events but you will lose user stitching. This seems to be a bug.

[@RossSedawie]

Oh no, I just found your video after turning this option on and GA4 has lost it's mind. Most of our conversions have bottomed out (but none of them have stopped tracking altogether, the conversion as just sawy lower, about 90% less). And my page path and screen class reports shows for a particular URL Views = 0, Users = 5.282 so it knows there are users on that page, but they are not associating the event (in this case page_view) with that user ID.

[@MeasurementAnalytics]

We've spotted purchase double counting since turning this option on and we're not using Measurement Protocol API. Recommending to all clients not to switch on until properly tested on a demo GA4 account.

[@GoonerAnirudhSharma]

Does it also affect if I'm not using Sliderule analytics?

[@kevinmclaughlin178]

Unclear at this point. If you're using the Measurement Protocol API then almost certainly yes

[@dhawkings]

Yes it does. I'm not using Sliderule and I'm seeing the same thing.

[@h254632]

@GoogleAnalytics, is this issue valid?

[@pomeshan4794]

In order to temporarily remove this problem, we excluded user_id from the request. So we can at least see the number of purchases.

[@ihordeyneha1214]

I guess everybody watch this video after enabling a toggle on.