Regional Segment is available to customers on the Business Tier plan.
See the available plans, or contact Support.
As Schrems II restricts the transfer of personal data to any processors established in countries outside of Europe, all data in European workspaces must be ingested, stored, processed and delivered locally within the EU. Segment offers customers the option to lead on data residency by providing regional infrastructure in both Europe and the United States.
The default region for all users is in Oregon, United States. Workspaces can be configured to use the EU West Data Processing Region ingest (for supported sources), process, filter, deduplicate, and archive data through Segment-hosted archives hosted in S3 AWS Dublin, Ireland. The regional infrastructure has the same rate limits and SLA as the default region.
To ensure a smooth transition from a US-based Segment workspace to an EU workspace, Segment will provide additional support and tooling to help with the transition later this year. Use the form link below to provide more information about your current setup and goals for transitioning.
The Segment UI doesn’t support moving workspaces between regions. To request help with this move, complete the Data Residency Workspace Provisioning Flow form.
Regional Data Ingestion
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.
Cloud event sources aren’t supported in EU workspaces.
For workspaces that use the EU West Data Processing region, the Dublin Ingestion region is preselected for all sources.
To set your Data Ingestion Region:
- Go to your source.
- Select the Settings tab.
- Click Regional Settings.
- Choose your Data Ingestion Region.
- If you’re in the US West data processing region, you can select from: Dublin, Singapore, Oregon, and Sydney.
- If you’re in the EU West data processing region, Segment’s EU instance only supports data ingestion from Dublin with the
All regions are configured on a per-source basis. You’ll need to configure the region for each source separately if you don’t want to use the default region.
All Segment client-side SDKs read this setting and update themselves automatically to send data to new endpoints when the app reloads. You don’t need to change code when you switch regions.
Server-side and project sources
When you send data from a server-side or project source, you can use the
host configuration parameter to send data to the desired region:
- Oregon (Default) —
- Dublin —
Create a new workspace with a different region
Use this form if you need to transition from your existing US-based workspace to an EU workspace.
To create a workspace with a different data processing region, reach out to the Segment Support team, and they will assist you with enabling the feature. Once the feature has been enabled, you’ll be able to self-serve and create a new workspace in a different data processing region by following these steps:
- Log in to your Segment account.
- Click New Workspace.
- Select your Data processing region. This determines the location in which Segment collects, processes, and stores data that’s sent to and from your workspace. You can choose from US West or EU West.
- Click Create workspace.
Once you create a workspace with a specified data processing region, you can’t change the region. You must create a new workspace to change the region.
EU Storage Updates
Segment Data Lakes (AWS)
Regional Segment in the EU changes the way you configure the Segment Data Lakes (AWS) environment
Warehouse Public IP Range
Use Segment’s custom CIDR
188.8.131.52/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. For non-EU customers.
Destination support and Regional endpoint availability
Don't see a regional endpoint for a tool you're using?
As more of the partner tools you use (Sources and Destinations) start to support a regional endpoint, Segment will update this list. Your contact for that tool should have a timeline for when they’re hoping to support regional data ingestion. You can also visit Segment’s support page for any Segment-related questions.
The following integrations marked with a (checkmark) support EU Regional endpoints.
This page was last modified: 04 Apr 2023
Questions? Problems? Need more info? Contact Segment Support for assistance!