From d2bd314e71a219019616d78dbc0a1ae0b57c24f4 Mon Sep 17 00:00:00 2001
From: joeynmq <37472597+joeynmq@users.noreply.github.com>
Date: Mon, 6 Nov 2023 16:56:23 +0800
Subject: [PATCH 1/2] Add note about sending Track events with a custom Group
 Key to Mixpanel

---
 .../destinations/catalog/actions-mixpanel/index.md           | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/src/connections/destinations/catalog/actions-mixpanel/index.md b/src/connections/destinations/catalog/actions-mixpanel/index.md
index 3011da4294..f273369196 100644
--- a/src/connections/destinations/catalog/actions-mixpanel/index.md
+++ b/src/connections/destinations/catalog/actions-mixpanel/index.md
@@ -135,3 +135,8 @@ If you want to confirm, you can configure the new destination to point to a diff
 
 If the Mixpanel (Actions) destination uses $group_id as the group key, ensure that the mappings handling your `track` events have the field for **Group ID** mapped to a valid value. By default, this field maps to the event variable `context.groupId`.
 
+To send Track events with a custom Group Key, you can include the key as a property of Track events. For example:
+```js
+analytics.track('Example Event', { custom_group_key : 'group1' });
+```
+

From 2330c50789f39aff4c71c74c8d204b590487a3f6 Mon Sep 17 00:00:00 2001
From: stayseesong <83784848+stayseesong@users.noreply.github.com>
Date: Mon, 4 Mar 2024 09:59:06 -0800
Subject: [PATCH 2/2] Update
 src/connections/destinations/catalog/actions-mixpanel/index.md

---
 src/connections/destinations/catalog/actions-mixpanel/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/connections/destinations/catalog/actions-mixpanel/index.md b/src/connections/destinations/catalog/actions-mixpanel/index.md
index f273369196..858ccf04b8 100644
--- a/src/connections/destinations/catalog/actions-mixpanel/index.md
+++ b/src/connections/destinations/catalog/actions-mixpanel/index.md
@@ -135,7 +135,7 @@ If you want to confirm, you can configure the new destination to point to a diff
 
 If the Mixpanel (Actions) destination uses $group_id as the group key, ensure that the mappings handling your `track` events have the field for **Group ID** mapped to a valid value. By default, this field maps to the event variable `context.groupId`.
 
-To send Track events with a custom Group Key, you can include the key as a property of Track events. For example:
+To send Track events with a custom Group Key, include the key as a property of Track events. For example:
 ```js
 analytics.track('Example Event', { custom_group_key : 'group1' });
 ```