Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Dexem is a French call tracking and conversational analytics platform that links incoming phone calls to the web source, campaign and keyword that generated them.
Dexem is a French call tracking and conversational analytics platform. It uses dynamic number insertion to display different phone numbers to different visitors, then links each incoming call back to the web source, campaign, keyword and page that generated it. Teams use it to measure which marketing drives phone calls.
To attribute a call, Dexem stores a visitor identifier and session data through cookies or similar identifiers, and records call metadata such as the caller number, duration and source. Depending on configuration it may also record call audio. This connects online browsing behaviour with offline phone activity.
Because Dexem combines website tracking with telephone data, it processes personal data including phone numbers and behavioural identifiers. The tracking identifiers are non essential, so they fall under the ePrivacy Directive consent rule, and any call recording is additionally sensitive and regulated. This makes Dexem a medium risk processing activity.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Prior consent is required before the Dexem tracking script sets identifiers, because attribution cookies are not strictly necessary. If calls are recorded, you must inform callers and obtain a valid legal basis for the recording, typically consent, and provide a way to object. Do not load the script before website consent is given.
Dexem is established in France and processes call tracking data within the European Union, which avoids the transfer concerns of United States based call analytics tools. Confirm the hosting region and sign the data processing agreement, and document retention periods for call records and recordings.
Gate the Dexem script behind your consent banner so number insertion and identifiers only activate after opt in. Configure a clear caller notice for any recording, set short retention for audio, and minimise the data captured. Keep your processing records and privacy policy aligned with both the web tracking and the telephony processing.
Websites using Dexem must obtain user consent under GDPR regulations.
DPIA considerations
Linking online identifiers to phone calls, and optionally recording audio, can be higher risk processing. A DPIA is often advisable to document the data flows, retention of call records and recordings, and the safeguards applied, especially where recording is enabled.
Sample consent text
We use Dexem call tracking to understand which marketing source led to your call. With your consent we set an attribution identifier; calls may be recorded and you will be informed beforehand.
Third-party domains contacted
dexem.comapp.dexem.comtag.dexem.comgoogle-analytics.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| dexem_visitor | Functional | 6 months | Identifies the visitor so a dynamic phone number can be matched to the web session |
| dexem_session | Functional | Session | Links the current browsing session to a call for attribution |
| dxm_source | Analytics | 6 months | Stores the marketing source and keyword associated with the visit for call attribution |
| _ga | Analytics | 2 years | Google Analytics cookie used when call data is forwarded to Google Analytics for reporting |
Dexem collects user analytics data — you legally need a consent banner. Try FlowConsent free.
Dexem uses functional cookies that identify the visitor and session so a dynamic phone number can be matched to a web visit, plus a cookie that stores the marketing source. If you forward call data to Google Analytics, its cookies also apply. The tracking cookies need consent before they load.
Yes for the tracking tag. The dynamic number insertion stores or reads information on the device, so ePrivacy requires consent. Call recording also requires a clear legal basis and that callers are informed before recording starts.
The dynamic number tag and analytics rely on consent under Article 6(1)(a) GDPR and Article 5(3) ePrivacy. Call recording can rest on legitimate interest or consent under Article 6(1)(f) or (a) depending on the purpose and on CNIL guidance.
No, not by Dexem itself. Dexem develops, hosts and supports its services in France, so personal data stays in the European Union. Transfers only occur if you connect Dexem to a third country tool such as Google Analytics.
A full DPIA is usually not mandatory for standard call tracking, but a screening assessment is recommended, particularly where calls are recorded. Large scale recording or sensitive call content can make a DPIA necessary.
Load the Dexem tag only after consent to tracking, disclose call tracking in your privacy and cookie policies, and play a recording notice at the start of calls. Set short retention for recordings and call data, and sign a data processing agreement with Dexem.
Alternatives include CallRail, Ringover analytics, Magnetis and CallTrackingMetrics. For EU based businesses, Dexem's French hosting is a strong point because it avoids cross border transfers.
List the Dexem visitor and session cookies and the marketing source cookie, explain their purpose and duration, and note that hosting is in France. Add Google Analytics cookies only if you forward call data, and review the entry when the tag changes.