Regionalization

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. For example, if Belgium customers use europe-west1, they can expect better latency.

Available regions

Country grouping	Geographical location	Endpoint	Resource Location
Global	Global serving, data-at-rest in US	`contactcenterinsights.googleapis.com`	`us-central1`
Americas	South Carolina	`us-east1-contactcenterinsights.googleapis.com`	`us-east1`
Americas	Oregon	`us-west1-contactcenterinsights.googleapis.com`	`us-west1`
Americas	Montréal	`northamerica-northeast1-contactcenterinsights.googleapis.com`	`northamerica-northeast1`
Europe	Belgium	`europe-west1-contactcenterinsights.googleapis.com`	`europe-west1`
Europe	London	`europe-west2-contactcenterinsights.googleapis.com`	`europe-west2`
Europe	Frankfurt	`europe-west3-contactcenterinsights.googleapis.com`	`europe-west3`
Asia Pacific	Tokyo	`asia-northeast1-contactcenterinsights.googleapis.com`	`asia-northeast1`
Asia Pacific	Mumbai	`asia-south1-contactcenterinsights.googleapis.com`	`asia-south1`
Asia Pacific	Singapore	`asia-southeast1-contactcenterinsights.googleapis.com`	`asia-southeast1`
Asia Pacific	Sydney	`australia-southeast1-contactcenterinsights.googleapis.com`	`australia-southeast1`

Sample Commands

Permissions required for this task

To perform this task, you must have the following permissions:

contactcenterinsights.analyses.create

REST

Before using any of the request data, make the following replacements:

PROJECT_ID: your Google Cloud project ID.
LOCATION_ID: regional location.
CONVERSATION_ID: the ID of the conversation you want to analyze. This value was returned in the `createConversation` response.

HTTP method and URL:

POST https://LOCATION_ID-contactcenterinsights.googleapis.com/v1/projects/PROJECT_ID/locations/LOCATION_ID/conversations/CONVERSATION_ID/analyses

To send your request, expand one of these options:

curl (Linux, macOS, or Cloud Shell)

Note: The following command assumes that you have logged in to the gcloud CLI with your user account by running gcloud init or gcloud auth login , or by using Cloud Shell, which automatically logs you into the gcloud CLI . You can check the currently active account by running gcloud auth list.

Execute the following command:

curl -X POST \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     -H "Content-Type: application/json; charset=utf-8" \
     -d "" \
     "https://LOCATION_ID-contactcenterinsights.googleapis.com/v1/projects/PROJECT_ID/locations/LOCATION_ID/conversations/CONVERSATION_ID/analyses"

PowerShell (Windows)

Note: The following command assumes that you have logged in to the gcloud CLI with your user account by running gcloud init or gcloud auth login . You can check the currently active account by running gcloud auth list.

Execute the following command:

$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
    -Method POST `
    -Headers $headers `
    -Uri "https://LOCATION_ID-contactcenterinsights.googleapis.com/v1/projects/PROJECT_ID/locations/LOCATION_ID/conversations/CONVERSATION_ID/analyses" | Select-Object -Expand Content

You should receive a JSON response similar to the following:

{
  "name": "projects/PROJECT_ID/locations/LOCATION_ID/operations/OPERATION_ID"
}

Python Client

While using the python client, both the host and the resource location needs to be updated to point to the regional instance.

options = ClientOptions(api_endpoint="us-east1-contactcenterinsights.googleapis.com" )
request = contact_center_insights_v1.ListConversationsRequest(
    parent=f"projects/{project_id}/locations/us-east1",
)
client = contact_center_insights_v1.ContactCenterInsightsClient(client_options=options)

Cloud Logging

See the Cloud Logging documentation to control the region where your logs are stored.