You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/actions-segment-profiles/index.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,4 +37,7 @@ To enable the Segment Profiles destination to send data to an existing Profile s
37
37
The Segment Profiles destination is not subject to API call or MTU costs. Any users or accounts created and updated by the Segment Profiles destination will not count towards your API call or MTU usage.
38
38
39
39
###Error loading options from Segment Profiles
40
-
Make sure you have a Public API token in your settings. If the Segment Profiles Destination doesn’t have a Public API token in the settings, the**Select Mappings** section fails to find any Profile (Engage) Spaces, which means you can't set your mappings.
40
+
Make sure you have a Public API token in your settings. If the Segment Profiles Destination doesn’t have a Public API token in the settings, the**Select Mappings** section fails to find any Profile (Engage) Spaces, which means you can't set your mappings.
41
+
42
+
###Succesful syncs but no changes on profiles
43
+
Make sure that the Endpoint Region setting matches the region of your workspace. If the region is correct and you don't see any profile changes,[contact Segment](https://segment.com/help/contact/){:target="_blank"}.