Set up your bannerConfigure Your ToolsAnalytics

Segment (Twilio)

How to configure Segment (Twilio) at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Improve the service, Support marketing analytics

Overview

This guide explains how to implement different privacy configurations for Twilio Segment and how to reflect them in the Consenter Manager.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. Segment Analytics.js on a website as a customer data platform that collects events and forwards them to destinations. Each destination (for example an analytics or ad tool) is a separate recipient and must be assessed and entered separately. Twilio Inc. is a US company.

What the service does in this scope. Analytics.js sets first-party cookies ajs_anonymous_id (anonymous visitor), ajs_user_id (logged-in user, after identify) and ajs_group_id (after group) as soon as the site loads; IDs are also persisted in local storage. Segment's Consent Management (Business tier) enforces consent across destinations. EU data residency requires an EU workspace and the EU endpoint events.eu1.segmentapis.com; only EU workspaces store data exclusively in the EU.

Configurations included.

ConfigurationSummary
Configuration A — Medium riskEU workspace; Analytics.js loads after consent; no identify; cloud-mode destinations limited to analytics.
Configuration B — Higher riskUS workspace; identify with traits (email); device-mode and advertising destinations; after consent.

No configuration without prior consent. ajs_anonymous_id is set on load; no consent-free configuration is documented.

Step 1 — Configure Segment

#Configuration areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk
1Processing purposesOperator decisionImprove the serviceImprove the service; Support marketing analytics; Receive personalised marketing offers (if ad destinations)
2Workspace regionCreate EU workspace or request migration; apiHost: "events.eu1.segmentapis.com/v1"EUUS
3LoadingConsenter blocks Analytics.js until consentAfter consentAfter consent
4Consent ManagementSegment Consent Management / consent wrapperMap destinations to consent categoriesMap destinations to consent categories
5Identify / traitsanalytics.identify(userId, traits)Not usedUsed
6DestinationsConnections > DestinationsCloud-mode analytics onlyDevice-mode and advertising destinations
7Persistenceuser.persist, cookie/localStorage keysDefaultDefault

Step 2 — Map the configuration in the Consenter Manager

Processing location. Twilio Inc. is a US company and can be required to disclose data in its possession, custody or control regardless of storage location.

Consenter Manager fieldConfiguration A — Medium riskConfiguration B — Higher risk
Processing purposesImprove the serviceImprove the service, Support marketing analytics
Tracking methodFirst party tracking (cross-session)First party tracking (cross-session)
IdentifierDevice identifiers, IP addressDevice identifiers, IP address, Authentication-derived identifiers, Direct identifier
Data categoriesBrowsing and interaction data, Device characteristics, Device identifiers, IP addressBrowsing and interaction data, Device characteristics, Device identifiers, IP address, Authentication-derived identifiers, direct identifier, Users' profiles
Legal role of data recipientProcessorProcessor
Personalisation modelNo personalisationProfile based (if profiles feed personalised marketing)
Maximum storage durationPer contractPer contract
Processing locationEU workspace; United States as potential access locationUnited States

Privacy-policy follow-up

  • Segment as processor; identifiers; destinations and their roles; region; potential access by US authorities.

Verification checklist

  • No cdn.segment.com load and no ajs_* cookies before consent.
  • Destinations receive data only for granted categories.

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page