I have this scenario.
I have User-ID feature enabled in my GA with session unification ON.
Inside my app when user logging I push userId to dataLayer and then I publish the custom event.
Inside my "All View" I can see 2 users witch is good (since merging still did not happen) and inside my User-ID View I can see just user with set User-ID
Now, the thing I noticed is that when the custom event that is published from the client is showing in both Non UserID and UserID Views.
But when I publish Custom Event from the Server thru the API, With only passing User-ID That event is only showing inside User-ID View.
My question is is this expected? Or should I publish the Event from the Client directly through API with User-Id, or Session Unification will do the job and I'll only have 1 event showing instead of two, meaning that it will figure out that Event is actually associated to that specific User?
Thanks!
Seeing the endpoint you are using the problem is definitely due to the fact that you are sending only the uid
parameter and not the cid
as well.
In order for the hit to be successful, only one of the two uid
or cid
parameters can be sent, however by sending only the uid
the hit will be shown only in the User-ID view.