Skip to content

Commit 9b03684

Browse files
authored
Update index.md
1 parent 626ecd0 commit 9b03684

File tree

1 file changed

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

1 file changed

+3
-0
lines changed

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -135,3 +135,6 @@ If you want to confirm, you can configure the new destination to point to a diff
135135

136136
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`.
137137

138+
### Why is Broadman, Oregon appearing in all user's profile location field?
139+
140+
If you are seeing traffic from Boardman or see Segment as the browser, this is most likely because you are sending calls to Mixpanel (Actions) from the server side (our AWS servers reside in Boardman, Oregon). In order to prevent the Boardman issue, you would have to manually pass the IP information in the context object from the server.

0 commit comments

Comments
 (0)