Set up your bannerConfigure Your ToolsAnalytics

matelso

How to configure matelso at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Support marketing analytics

Overview

This guide explains how to implement different privacy configurations for matelso call tracking 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. matelso call tracking on a website: static tracking numbers, and dynamic call tracking with the matelso Search & Replace (S&R) script.

What the service does in this scope. Static call tracking uses a single number per advertising measure; dynamic call tracking embeds a script that "plays out an individual call number to each visitor". The S&R script collects web data of the visitor and must set a cookie to work. matelso states that its platform uses only first-party cookies, "for which we request the user's consent", and that without consent no web data is collected. Conversions can be transferred to tools such as Google Ads or GA4.

Configurations included.

ConfigurationSummary
Configuration A — Lower riskStatic single-number pools placed directly in the page, without the S&R script.
Configuration B — Higher riskDynamic call tracking with the S&R script and conversion transfer to ad platforms; after consent.

Consent. matelso itself recommends integrating dynamic call tracking into consent management. Configuration A involves no script on the website; the call data is processed when the visitor calls, not through the website.

Step 1 — Configure matelso

#Configuration areaWhere to configure itConfiguration A — Lower riskConfiguration B — Higher risk
1Processing purposesOperator decisionSupport marketing analytics (per channel, aggregate)Support marketing analytics
2Number typematelso control panel: book single number or dynamic poolSingle number per channel, inserted in page HTMLDynamic pool
3S&R scriptWebsite / tag managerNot embeddedEmbedded, blocked until consent
4Fallback for refusalsSingle-pool number as search text in the dynamic pool—Configure
5Conversion transferIntegrations (Google Ads, GA4)Not usedUsed (each receiving platform needs its own entry)

Step 2 — Map the configuration in the Consenter Manager

Configuration A requires no Consenter Manager entry for website tracking (no script or cookie on the website).

Consenter Manager fieldConfiguration B — Higher riskBasis and conditions
Processing purposesSupport marketing analyticsAttribution of calls to campaigns.
Tracking methodFirst party tracking (cross-session)First-party cookie set by the S&R script.
IdentifierDevice identifiers, IP addressCookie; IP with each request.
Data categoriesBrowsing and interaction data, Device identifiers, Device characteristics, IP address, User-provided dataWeb data of the visitor; caller data linked through the dynamic number. Add "direct identifier" if caller phone numbers are linked to the web session.
Legal role of data recipientProcessorVerify against your matelso DPA.
Personalisation modelNo personalisation—
Maximum storage durationNot documented—
Processing locationPer contractmatelso is a German company; check sub-processors for US providers.

Privacy-policy follow-up

  • matelso as recipient; dynamic number allocation and linking of calls to web sessions; cookies; conversion transfers to ad platforms.

Verification checklist

  • B: no S&R script and no matelso cookie before consent.
  • B: refusers see the single-pool fallback number.

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