Skip to content

Add info on troubleshooting Group properties not attribute Mixpanel groups #6840

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

tanjinhong72
Copy link
Contributor

Proposed changes

Added the following to troubleshooting section.

Group properties are not attributed to Mixpanel Groups

If the Mixpanel (Actions) destination uses $group_id as the group key, ensure that the mappings handling your Group events have the field for Group ID mapped to a valid value and the field for Group Key is left blank or without value. By default, the field Group ID is map to the event variable groupId and leaving the field for Group Key as blank will use $group_id as the group key.

Merge timing

Related issues (optional)

https://segment.zendesk.com/agent/tickets/545764

…panel group

Added the following
-----------------------------------------------------------------

### Group properties are not attributed to Mixpanel Groups

If the Mixpanel (Actions) destination uses $group_id as the group key, ensure that the mappings handling your `Group` events have the field for **Group ID** mapped to a valid value and the field for **Group Key** is left blank or without value. By default, the field **Group ID** is map to the event variable `groupId` and leaving the field for **Group Key** as blank will use $group_id as the group key.
@tanjinhong72 tanjinhong72 marked this pull request as ready for review September 19, 2024 00:58
@tanjinhong72 tanjinhong72 requested a review from a team as a code owner September 19, 2024 00:58
@@ -137,6 +137,10 @@ To send Track events with a custom Group Key, include the key as a property of T
```js
analytics.track('Example Event', { custom_group_key : 'group1' });
```
### Group properties are not attributed to Mixpanel Groups
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Group properties are not attributed to Mixpanel Groups
### Group properties aren't attributed to Mixpanel Groups

@@ -137,6 +137,10 @@ To send Track events with a custom Group Key, include the key as a property of T
```js
analytics.track('Example Event', { custom_group_key : 'group1' });
```
### Group properties are not attributed to Mixpanel Groups

If the Mixpanel (Actions) destination uses $group_id as the group key, ensure that the mappings handling your `Group` events have the field for **Group ID** mapped to a valid value and the field for **Group Key** is left blank or without value. By default, the field **Group ID** is map to the event variable `groupId` and leaving the field for **Group Key** as blank will use $group_id as the group key.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If the Mixpanel (Actions) destination uses $group_id as the group key, ensure that the mappings handling your `Group` events have the field for **Group ID** mapped to a valid value and the field for **Group Key** is left blank or without value. By default, the field **Group ID** is map to the event variable `groupId` and leaving the field for **Group Key** as blank will use $group_id as the group key.
If the Mixpanel (Actions) destination uses `$group_id` as the group key, ensure that the mappings handling your `Group` events have the **Group ID** mapped to a valid value the **Group Key** is left blank or without value. By default, the **Group ID** maps to the event variable `groupId`. If you leave the **Group Key** blank, the `$group_id` is used as the group key.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants