Skip to content

Commit e1c517d

Browse files
author
markzegarelli
authored
Merge pull request #3179 from segmentio/DOC-549-mixpanel
DOC-549 Add clarity around device modes to Mixpanel destination
2 parents d3146c5 + 62b050b commit e1c517d

File tree

3 files changed

+13
-9
lines changed

3 files changed

+13
-9
lines changed

.github/styles/Vocab/Docs/accept.txt

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,7 @@ Amberflo
2222
Appboy
2323
Appsflyer
2424
async
25+
background(?:ed|ing)
2526
Blitzllama
2627
blocklist
2728
boolean
@@ -100,4 +101,5 @@ viewability
100101
waitlist
101102
WebKit
102103
Wootric
104+
Xcode
103105
Zendesk

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

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -47,13 +47,18 @@ If you want to track the `page` or `screen` calls to Mixpanel with the name or c
4747
> info ""
4848
> Beginning with "Consolidate Page" calls, the following options are each *mutually exclusive*. [See the code for details](https://github.com/segmentio/analytics.js-integrations/blob/master/integrations/mixpanel/lib/index.js#L96-L139){:target="_blank"}.
4949
50+
### Prioritization of settings
5051

52+
When you use the Mixpanel destination in Cloud-mode, Segment sends events for each option you select. This may result in Mixpanel receiving duplicate events for a single page call.
5153

52-
If you select "Track all Pages to Mixpanel", all `page` calls regardless of how you have customized it will send a `Loaded A Page`. Even if you have the other options enabled, Segment sends this call to prevent double counting your pageviews.
54+
When you use the Mixpanel destination in Device-mode, Segment prioritizes the options to prevent duplicate calls as follows:
5355

54-
If you select "Track Categorized Pages to Mixpanel", Segment sends a `Viewed [category] Page` event.
5556

56-
If you select "Track Named Pages to Mixpanel", Segment sends a `Viewed [name] Page` event.
57+
- If you select "Track all Pages to Mixpanel", all `page` calls regardless of how you have customized it will send a `Loaded A Page`. Even if you have the other options enabled, Segment sends this call to prevent double counting your pageviews.
58+
59+
- If you select "Track Categorized Pages to Mixpanel", Segment sends a `Viewed [category] Page` event.
60+
61+
- If you select "Track Named Pages to Mixpanel", Segment sends a `Viewed [name] Page` event.
5762

5863
> info ""
5964
> If both Option 2 and 3 are enabled, Segment gives precedence to `category`. If you pass both `category` and `name`, (for example, `analytics.page('category', 'name');`), Segment sends a `Viewed category name Page` to Mixpanel.
@@ -339,9 +344,6 @@ Segment doesn't map `$library_version` since that is reserved for Mixpanel's lib
339344

340345
## Features
341346

342-
### Autotrack
343-
344-
Mixpanel discontinued the Autotrack feature in February 2021. The feature is no longer available for use.
345347

346348
### People
347349

@@ -584,7 +586,7 @@ You can check a specific user profile in Mixpanel for Computed Traits by going t
584586

585587
Computed traits without a lookback window search across all historical events, and update in real time.
586588

587-
Computed traits with a lookback window only search across events that occurred within the specified timeframe. Computed traits *with* a lookback window are updated hourly.
589+
Computed traits with a lookback window only search across events that occurred within the specified time frame. Computed traits *with* a lookback window are updated hourly.
588590

589591
![](images/pers-03-lookback.png)
590592

@@ -624,7 +626,7 @@ You can check a specific user profile in Mixpanel for audience events by going t
624626

625627
Audiences without a lookback window searches across all historical events and update in real time.
626628

627-
Audiences with a lookback window only search across events that occurred within the specified timeframe. Audiences *with* a lookback window are updated hourly.
629+
Audiences with a lookback window only search across events that occurred within the specified time frame. Audiences *with* a lookback window are updated hourly.
628630

629631

630632
![](images/pers-10-lookback.png)

src/guides/regional-segment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ redirect_from:
77
---
88
{% include content/plan-grid.md name="data-residency" %}
99

10-
As Schrems II restricts the transfer of personal data to any processors established in countries outside of Europe, all data in European workspaces must be ingested, stored, processed and delivered locally within the EU. Segment offers customers the option to lead on data residency by providing regional infrastructure in both the Europe and the United States.
10+
As Schrems II restricts the transfer of personal data to any processors established in countries outside of Europe, all data in European workspaces must be ingested, stored, processed and delivered locally within the EU. Segment offers customers the option to lead on data residency by providing regional infrastructure in both Europe and the United States.
1111

1212
The default region for all users is in Oregon, United States. Workspaces can be configured to use the EU West Data Processing Region ingest (for supported sources), process, filter, deduplicate, and archive data through Segment-hosted archives hosted in S3 AWS Dublin, Ireland. The regional infrastructure has the same [rate limits and SLA](/docs/connections/rate-limits/) as the default region.
1313

0 commit comments

Comments
 (0)