Skip to content

Commit ea5e564

Browse files
committed
Update mixpanel-swift.md
1 parent 6f729dc commit ea5e564

File tree

1 file changed

+1
-3
lines changed
  • src/connections/sources/catalog/libraries/mobile/apple/destination-plugins

1 file changed

+1
-3
lines changed

src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/mixpanel-swift.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -82,9 +82,7 @@ The first thing you'll want to do is to identify your users so Mixpanel knows wh
8282

8383
As soon as you have a `userId` for a visitor that was previously anonymous you'll need to [`alias`](/docs/connections/spec/alias/) their old anonymous `id` to the new `userId`. In Mixpanel only **one** anonymous user history can be merged to **one** identified user. For that reason you should only call `alias` once, right after a user registered, but before the first `identify`.
8484

85-
When you call the Identify method from the client in either a browser using Analytics.js or one a mobile SDKs, several things occur:
86-
Segment recognizes and translates the [special traits](/docs/connections/spec/identify/#traits) so that they fit the expectations of Mixpanel's API.
87-
The table below shows the mappings. Pass the key on the left and Segment transforms it to the key on the right before sending to Mixpanel.
85+
When you call the Identify method from the client in either a browser using Analytics.js or one a mobile SDKs, several things occur: Segment recognizes and translates the [special traits](/docs/connections/spec/identify/#traits) so that they fit the expectations of Mixpanel's API. The table below shows the mappings. Pass the key on the left and Segment transforms it to the key on the right before sending to Mixpanel.
8886

8987
<table>
9088
<tr>

0 commit comments

Comments
 (0)