Skip to content

Commit e67a57c

Browse files
authored
Add info about Mixpanel's distinct_id
Our public documentation does not contain information regarding how distinct_id is set when customers use Mixpanel (legacy) in cloud-mode. Source code: https://github.com/segmentio/integrations/blob/master/integrations/mixpanel/lib/index.js#L749-L755
1 parent e240a5b commit e67a57c

File tree

1 file changed

+6
-0
lines changed
  • src/connections/destinations/catalog/mixpanel

1 file changed

+6
-0
lines changed

src/connections/destinations/catalog/mixpanel/index.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -485,6 +485,12 @@ If you're testing in Xcode remember you must first background the app, then the
485485

486486
## Appendices
487487

488+
489+
### Distinct ID
490+
491+
In Device-mode, when a `distinct_id` is present in the browser, it will be automatically sent to Mixpanel. While in Cloud-mode, the `distinct_id` is set to Segment's `userId` if one is present. If there is no `userId` on the payload, `anonymousId` is set instead.
492+
493+
488494
### IP
489495

490496
If an `ip` property is passed to Mixpanel, the value will be interpreted as the IP address of the request and therefore automatically parsed into Mixpanel geolocation properties (City, Country, Region). After that IP address has been parsed, they will throw out the IP address and only hold onto those resulting geolocation properties. As such, if you want to display an IP address as a property within the Mixpanel UI or within raw data, you will simply want to slightly modify the naming convention for that property.

0 commit comments

Comments
 (0)