Mixpanel User Identification Splitting Profiles via Stape Tag

Google Tag Manager Server Container
1

Hi,

I am using Mixpanel Server Tag Template. I am using custom domain mapping. Within the Mixpanel template, I have enabled automatic distinct ids for all Mixpanel tags types such as Track, Alias, Identify and people set commands.

When the page view track event fires, the distinct id is this:
$device:s-1728057671904-174154-334236-517827

And all the subsequent pageviews, have the above distinct id which is all good. Now when I signup, the distinct id is split b/w two profiles:

User profile A: $device:s-1728057671904-174154-334236-517827
User profile B: s-1728057671904-174154-334236-517827

All the event history is showing up in profile A without name and email and B profile, does not have any event history, however it has name and email.

Stape Cookie Value (stape_mixpanel_distinct_id) is also set to:
s-1728057671904-174154-334236-517827

Shouldn’t all the events be logged under one distinct ID that was generated initially during a page view event - $device:s-1728057671904-174154-334236-517827 since we are using automatic distinct id option. Why does it split into two profiles?

Thanks,

Arif

2

Example

Distinct ID split

Part 1

image
image855×533 23 KB

Part 2

image
image1836×848 40.3 KB

Both are same, however, the $device: part is stripped off.

3

Any help here to deal with this problem?

4

Hi @Arif_Ahmed,
I tried to reproduce your problem, but it didn’t work for me. I will try to spend a little more time and let you know