Problem with add_to card and purchase push events changing user_pseudo_id.
We are constantly missing the user_pseudo_id lifecycle.
A user has the same User_id and the same user_pseudo_id, throughout the purchase cycle, at the time of purchase, he maintains the same user_id, but exchanges the user_pseudo_id for a new one. What is the reason for this to happen?
I’m not sure what’s happening there. I haven’t looked closely at the Big Query data from GA4 yet but I am going to over the next few weeks. I’ll let you know if I find anything.
But not just with bigquery, let’s focus on GA4, I have a flow with all events with the same client_id, in several cases the purchase events change my client_id. So I have my user_id the same and the client_id only changes in purchase events. This is disrupting my flow. At some point I believe that the app is changing the client_id at the time of conversion.
Can you answer questions like:
How do you collect the “cid,” which we refer to as the client ID in GA and as “user_pseudo_id” in BigQuery?
Do you make any changes before sending? We’ve observed that in some cases, the data comes with the client ID prefixed with “CL.”
Are the purchases sent at the time of purchase or some time afterward?
Can you provide an example of the payload that is sent to GA?
Hello, I created a test property sending purchase data via gtm and the client id does not change. So it’s some part of the shopify slide rules integration, can you help me with that?