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/regional-segment-eu.md
+12-6Lines changed: 12 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,11 @@ hidden: true
9
9
10
10
Segment provides regional infrastructure across Europe, Middle East, Africa and Asia Pacific with [rate limits and SLA](/docs/connections/rate-limits/).
11
11
12
-
As Schrems II restricts the transfer of personal data to any processors established in countries outside of Europe, all data in European workspaces ingest, store, process and deliver locally within the EU. You can set up workspaces in the EU where data is received via the Dublin, Ireland endpoint hosted in the EU for all sources, with the exception of [cloud object sources](/docs/connections/sources/#object-cloud-sources) and cloud event sources that aren't supported. Segment-hosted archives hosted in S3 AWS Dublin, Ireland, process, filter, validate, deduplicate, and archive data for EU workspaces.
12
+
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. Workspaces you configure 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.
13
+
14
+
> info ""
15
+
> [Cloud object sources](/docs/connections/sources/#object-cloud-sources) and cloud event sources aren't supported in EU workspaces.
16
+
13
17
14
18
> info ""
15
19
> Regional Segment for Europe is currently in beta. Segment’s [First-Access and Beta terms](https://segment.com/legal/first-access-beta-preview/) govern this feature.
@@ -18,11 +22,12 @@ As Schrems II restricts the transfer of personal data to any processors establis
18
22
To create a workspace with a different data processing region:
19
23
1. Log in to your segment account.
20
24
2. Click **New Workspace**.
21
-
3. 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 Central*.
25
+
3. 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*.
22
26
4. Click **Create workspace**.
23
27
24
28
> info ""
25
-
> 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.
29
+
> 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.
30
+
26
31
27
32
## Regional Data Ingestion
28
33
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 across locations within a region, but never across regions.
@@ -35,16 +40,17 @@ To set your Data Ingestion Region:
35
40
2. Select the **Settings** tab.
36
41
3. Click **Regional Settings**.
37
42
4. Choose your **Data Ingestion Region**.
38
-
* If you’re in the US region, you can select from: Dublin, Singapore, Oregon, and Sydney.
39
-
* Segment’s EU instance only supports data ingestion from Dublin with the `events.eu1.segmentapis.com` endpoint.
43
+
* If you’re in the *US West* data processing region, you can select from: Dublin, Singapore, Oregon, and Sydney.
44
+
* If you're in the *EU West* data processing region, Segment’s EU instance only supports data ingestion from Dublin with the `events.eu1.segmentapis.com` endpoint.
45
+
40
46
41
47
### Client-side sources
42
48
You can configure Segment’s client-side SDKs for Javascript, iOS, Android, and React Native sources to send data to a regional host after you’ve updated the Data Ingestion Region in that source’s settings.
43
49
44
50
All regions are configured on a per-source basis. Configure the region for each source separately if you don't want to use the default region.
45
51
46
52
> info ""
47
-
> Dublin is the only region for EU instances and defaults automatically.
53
+
> For workspaces that use the EU West Data Processing region, the Dublin Ingestion region is preselected for all sources.
48
54
49
55
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 the code when you switch regions.
Copy file name to clipboardExpand all lines: src/connections/storage/warehouses/schema.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -258,7 +258,7 @@ analytics.track('Register', {
258
258
Then you can expect to see columns named `plan` and `account_type` as well as the default `event`, `id`, and so on. That way, you can write queries against any of the custom data sent in track calls.
259
259
260
260
> info "Note"
261
-
> Because `properties` and `traits`are added as un-prefixed columns to your tables, there is a chance of collision with our reserved column names. For this reason, properties with the same name as reserved column name (for example.`user_id`) are discarded.
261
+
> Because Segment adds `properties` and `traits` as un-prefixed columns to your tables, there is a chance the names can collide with the reserved column names. For this reason, Segment discards properties with the same name as the reserved column name (for example,`user_id`).
262
262
263
263
Your event tables are one of the more powerful datasets in Segment SQL. They allow you to see which actions users perform when interacting with your product.
0 commit comments