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/guides/regional-segment.md
+44-3Lines changed: 44 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,49 @@ Regional Data Ingestion enables you to send data to Segment from both Device-mod
25
25
26
26
{% include content/eu-cloud-event-sources.html %}
27
27
28
-
### Client-side sources
28
+
### Configuring Segment Sources
29
+
30
+
To send data from mobile apps to the correct region, you must update your SDK configuration to use the right endpoint. You must do this even if your source settings are already configured in Segment itself.
31
+
32
+
> warning "Use the correct endpoint"
33
+
> Starting in Q2 2025, Segment will reject data sent to the wrong region. Your SDK must be configured to send data to the correct regional endpoint to prevent dropped events.
34
+
35
+
Segment's EU instance only supports data ingestion through the Dublin region, using this endpoint:
36
+
37
+
`https://events.eu1.segmentapis.com/v1`
38
+
39
+
#### SDK configuration examples
40
+
41
+
Use the examples in this section to configure mobile SDKs to point to the EU endpoint. These examples use JavaScript-style syntax for clarity. Refer to your platform's documentation for exact implementation.
42
+
43
+
{% codeexample %}
44
+
{% codeexampletab iOS/Android/Xamarin/Flutter %}
45
+
```js
46
+
// Pseudocode example — set these options using your platform's syntax
47
+
constanalytics=newAnalytics({
48
+
writeKey:'<YOUR_WRITE_KEY>',
49
+
apiHost:"events.eu1.segmentapis.com/v1",
50
+
// other options...
51
+
})
52
+
```
53
+
{% endcodeexampletab %}
54
+
55
+
{% codeexampletab React Native %}
56
+
```js
57
+
// Pseudocode example — set these options using your platform's syntax
58
+
constanalytics=newAnalytics({
59
+
writeKey:'<YOUR_WRITE_KEY>',
60
+
proxy:"https://events.eu1.segmentapis.com/v1",
61
+
useSegmentEndpoints:true,
62
+
// other options...
63
+
})
64
+
```
65
+
{% endcodeexampletab %}
66
+
{% endcodeexample %}
67
+
68
+
If you're using the Segment EU endpoint with Analytics-C# source, you must manually append `/v1` to the URL (like `events.eu1.segmentapis.com/v1`).
69
+
70
+
For workspaces using the `EU WEST` data processing region, the Dublin ingestion region is preselected for all sources.
29
71
30
72
To route data from your client-side sources to the correct region, you'll need to make two updates:
31
73
@@ -38,8 +80,7 @@ Segment client-side SDKs (like Analytics.js, iOS, and Android) typically fetch u
38
80
39
81
To avoid data being sent to the wrong region, **you must add the correct endpoint configuration directly in your SDK setup.**
40
82
41
-
> warning "Use the correct endpoint"
42
-
> Starting in Q2 2025, Segment will reject data sent to the wrong region. Your SDK must be configured to send data to the correct regional endpoint to prevent dropped events.
83
+
43
84
44
85
Use the following code examples to point your SDK to the EU endpoint:
0 commit comments