Skip to content

Commit 32e47f9

Browse files
authored
typo + heading
1 parent 5919be6 commit 32e47f9

File tree

1 file changed

+2
-2
lines changed
  • src/connections/destinations/catalog/actions-mixpanel

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ By default, the Mixpanel (Actions) destination uses `$group_id` as the group key
6565
2. Scroll to the "Group Keys" section. If this section doesn't exist, you may not have the Group Analytics add-on.
6666
3. Create the new group key:
6767

68-
![GIF demonstratin how to set Group key in Mixpanel UI](./images/set-group-key.gif)
68+
![GIF demonstrating how to set Group key in Mixpanel UI](./images/set-group-key.gif)
6969

7070
### Using a different group key
7171
If you already have a group set up in Mixpanel with a different group key and wish to use that one, you can specify it in the `Group Key` field of the destination configuration.
@@ -109,7 +109,7 @@ The group ID that Mixpanel will use is `12345`.
109109
>
110110
> Segment also maps the following traits to Mixpanel reserved properties to fit Mixpanel's use cases: `traits.created` -> `$created`, `traits.email` -> `$email`, `traits.firstName` -> `$first_name`, `traits.lastName` -> `$last_name`, `traits.name` -> `$name`, `traits.username` -> `$username` and `traits.phone` -> `$phone`.
111111
112-
### Example
112+
##### Example
113113
For example, if you map `traits.email` to Mixpanel, Segment automatically transforms this into Mixpanel's reserved property `$email`.
114114

115115
![Screenshot of mapping traits.email from Segment to Mixpanel email field, which Segment transforms to $email](./images/traits-mapping-screenshot.png)

0 commit comments

Comments
 (0)