Skip to content

Commit cdadb59

Browse files
authored
Add Group ID is for mapping of track event to group key $group_id
In the Troubleshooting section, modify the following (original) statement: "Ensure that the mapping(s) handling your track events have the field for Group ID mapped to a valid value. By default, this field is mapped to the event variable context.groupId." To the following that mentioned using of group key $group_id: "For Mixpanel (Actions) destination that uses $group_id as the group key, ensure that the mapping(s) handling your track events have the field for Group ID mapped to a valid value. By default, this field is mapped to the event variable"context.groupId."
1 parent 9fcd29a commit cdadb59

File tree

1 file changed

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

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -133,5 +133,5 @@ If you want to confirm, you can configure the new destination to point to a diff
133133

134134
### Track events are not attributed to Mixpanel Groups
135135

136-
Ensure that the mapping(s) handling your `track` events have the field for **Group ID** mapped to a valid value. By default, this field is mapped to the event variable `context.groupId`.
136+
For Mixpanel (Actions) destination that uses $group_id as the group key, ensure that the mapping(s) handling your `track` events have the field for **Group ID** mapped to a valid value. By default, this field is mapped to the event variable `context.groupId`.
137137

0 commit comments

Comments
 (0)