Customer Experience Agent Studio provides data residency (DRZ) to keep your data-at-rest physically within a specified geographical region or location. When you specify a region, your data-at-rest is not stored outside that region. Pricing is the same for all regions.
Specifying a region is particularly helpful in the following use cases:
- Your system has regulatory or policy requirements that govern where your data must reside.
- Your network latencies might be improved when the data is in the same region as your customers.
Available regions
| Region ID | Description |
|---|---|
us |
Multi-region data centers in the United States. |
eu |
Multi-region data centers in the European Union. Agent data in the EU multi-region is not stored in the EUROPE-WEST2 (London) or EUROPE-WEST6 (Zürich) regions. |
Available features for regional serving
All features are available in all supported regions.
ML processing
Machine learning (ML) processing occurs within the specific region or multi-region where the request is made. For the details on data residency support for each model and region, see Gemini Enterprise Agent Platform - Data residency.
The following models supported by CX Agent Studio are not mentioned on the Gemini Enterprise Agent Platform page, but the ML processing still occurs within your selected region or multi-region:
- gemini-3.1-flash-live
Data-at-rest
All Customer Experience Agent Studio developer user and end-user data is included in data-at-rest. For example:
- Callback Code
- Tool Code and Configurations
- Agent Instructions and Prompts
- Application Variables
- Conversation History
Specify a region using the API
To use regionalization you must specify a region for every API request.
Required fields:
- Provide the region ID for the
locationURL path or resource parameter.
Cloud Logging
See the Cloud Logging documentation to control the region where your logs are stored.