Regional Segment

Regional Data Ingestion enables you to send data to Segment from both Device-mode and Cloud-mode sources through regionally hosted API ingest points. The regional infrastructure can fail-over across locations within a region, but never across regions.

Some Segment SDKs require specific endpoint configuration to send data to the correct regional infrastructure. This section provides setup details for mobile SDKs, server-side SDKs, custom integrations, and supported cloud sources.

Use this table as a reference to determine how to configure your source or SDK to send data to the correct endpoint:

To send data from mobile apps to the correct region, you have to update your SDK configuration to use the right endpoint. You must do this even if your source settings are already configured in Segment itself.

Segment's EU instance only accepts data through its Dublin-based endpoint:

https://events.eu1.segmentapis.com/v1

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.

1
const analytics = new Analytics({
2
  writeKey: '<YOUR_WRITE_KEY>', // Required: your source's write key from Segment
3
  apiHost: "events.eu1.segmentapis.com/v1", // Routes data through EU endpoint
4
  // You can also configure options like flushInterval, debug, or storage providers
5
})

1
const analytics = new Analytics({
2
  writeKey: '<YOUR_WRITE_KEY>', // Required: must belong to an EU workspace
3
  proxy: "https://events.eu1.segmentapis.com/v1", // Required for EU data routing
4
  useSegmentEndpoints: true, // Ensures proxy is used instead of default US host
5
  // You can also set options like flushInterval or trackAppLifecycleEvents
6
})

If you're using the Segment EU endpoint with the Analytics-C# source, you must manually append /v1 to the URL (like events.eu1.segmentapis.com/v1).

For workspaces using the EU WEST data processing region, the Dublin ingestion region is preselected for all sources.

Once you finish updating your SDK(s), make sure your source settings in Segment also reflect the correct region.

If you're using Segment's server-side SDKs (like Node.js, Python, and Java) or making direct HTTP API requests, you'll need to update the endpoint your data is sent to. This is required to match your workspace's region and avoid rejected traffic.

Use this example to configure server-side SDKs like Node.js, Python, and Java:

1
// Example configuration — adjust for your SDK's syntax
2
const analytics = new Analytics({
3
  writeKey: "<YOUR_WRITE_KEY>", // Required: must belong to an EU workspace
4
  host: "https://events.eu1.segmentapis.com", // EU endpoint — do not include /v1 for these SDKs
5
  // You can configure other options like flushInterval or request retries
6
});

If you're sending data using custom HTTP requests or through a proxy and you've reused a write key originally issued for a US-based workspace, you'll need to do the following:

• Update your request target to: https://events.eu1.segmentapis.com/v1.
• Make sure the write key belongs to an EU workspace.

Data sent to the EU endpoint using a US-region write key will get rejected.

The following cloud sources are supported in EU workspaces:

• Amazon S3
• Iterable

Segment maintains and hosts these sources, and they don't require SDK-level configuration.

If you're using other cloud sources not listed here, they may only be available in US-based workspaces. Reach out to Segment Support if you're unsure whether a cloud source is supported in the EU.

Segment workspaces use US data residency by default. If you need EU data residency, reach out to your Segment account executive to enable EU workspace creation. Once the feature is enabled, you can create a new EU workspace by following these steps:

1. Log in to your Segment account.
2. Click New Workspace.
3. Select your Data processing region. This determines where Segment collects, processes, and stores the data sent to and from your workspace. You can choose between US West and EU West.
4. Click Create workspace.

Sources within EU workspaces deliver Segment data to EU-based AWS storage.

Regional Segment in the EU changes the way you configure the Segment Data Lakes (AWS) environment

Use Segment's custom CIDR 3.251.148.96/29 while authorizing Segment to write in to your Redshift or Postgres port. BigQuery doesn't require you to allow a custom IP address.

• Regional Segment is currently limited to the EU. Future expansion of Regional Segment beyond the EU is under evaluation by Segment Product and R&D.
• Edge proxies are deprecated. Customers using Regional Endpoints may see US-based IP addresses in event payloads, Segment recommends using the US-based endpoint (api.segment.io) to preserve client IP addresses. For EU customers, Segment recommends using a Regionalized EU workspace.

The following integrations marked with a ✅ (checkmark) support EU Regional endpoints.

The following Sources marked with a ✅ (checkmark) are supported in EU workspaces.