13 min readCompliance

Consent Mode v2 for link tracking: what the DMA changed

Consent Mode v2 and the Digital Markets Act rewrote short-link analytics: what the four signals mean, how server-side recovery works.

Sasha Ehrlich
Compliance · EU residency

Consent Mode v2 stopped being optional on 2024-03-06. From that date, EU and EEA traffic into Google's advertising products has had to pass two new signals - ad_user_data and ad_personalization - alongside the original ad_storage and analytics_storage. The change was driven not by GDPR but by the Digital Markets Act (Regulation (EU) 2022/1925), and specifically by DMA Art. 5(2), which forbids designated gatekeepers from combining or cross-using personal data across services without explicit consent.

For a URL shortener that intersects the redirect data plane in awkward ways. A short link is what the user clicked; the consent state on the landing page decides whether the click can be attributed. Those two events happen on different domains, in different cookie jars, often in different sessions. The gap between them is where most attribution loss now lives.

The same consent gate governs any advertising pixel you fire on a redirect, including link retargeting, where the pixel has to stay suppressed until the visitor opts in.

This post is the working compliance counsel's read on what changed, what the four signals actually mean for a redirect service, where server-side recovery is legal under the EDPB's current guidance, and where it is not. Most of the engineering work for server-side tracking via redirects is fine under GDPR; some of it is not fine under the DMA.

The DMA, in one paragraph

The Digital Markets Act became applicable on 2024-03-07. It designates "gatekeepers" - Alphabet, Amazon, Apple, ByteDance, Meta, Microsoft, Booking - and imposes ex ante obligations on them. DMA Art. 5(2) is the one that matters for tracking: a gatekeeper shall not process personal data of third-party-service end users for online advertising, nor combine personal data across its services, without consent.

For Art. 5(2), Google's compliance mechanism is Consent Mode v2. The two new signals - ad_user_data and ad_personalization - let the gatekeeper observe whether the publisher has obtained Art. 5(2)-grade consent before click telemetry is used for advertising or personalisation. Without those signals set to granted, Google's advertising products fall back to aggregated or modelled conversions with no per-user attribution.

The DMA does not replace GDPR. It sits on top. A controller still needs an Art. 6 lawful basis under GDPR; Consent Mode v2 adds a second gate that closes for gatekeeper-routed advertising data even when the GDPR gate is open.

The four signals, in plain terms

The v2 spec ships four boolean signals. Each can be granted or denied. Defaults can be set per-region.

The four Consent Mode v2 signals as a table: ad_storage, ad_user_data and ad_personalization (both DMA v2 additions) and analytics_storage, each with its granted effect and its denied fallback

ad_storage is the original v1 signal. Controls whether cookies or other storage are written for advertising. When denied, Google tags fire without identifiers; conversion measurement degrades to cookieless, modelled aggregates. The redirect decides what UTMs and click identifiers land on the page, and those become the keys consent attaches to. The tag-platform consent documentation is the canonical reference for what each signal does downstream.

ad_user_data is new in v2. Controls whether user data may be sent to Google for advertising at all. This is the DMA Art. 5(2) signal. When denied, the tag cannot transmit user data - including hashed identifiers, IP, user-agent - to Google Ads. Server-side tagging does not bypass this; the signal travels with the event.

ad_personalization is also new. Controls whether transmitted data may be used for personalised advertising, including remarketing. A common configuration is ad_user_data=granted plus ad_personalization=denied, which permits attribution but blocks remarketing.

analytics_storage controls whether storage is written for analytics. The GA4 tag honours this; when denied, GA4 runs cookieless and uses consent-mode modelling to reconstruct attribution at aggregate level. Modelling needs a minimum traffic volume and a 7-day learning period.

None of the four signals are decided at the shortener. The shortener emits the click; the landing page reads the signals; the tag on the landing page decides what to do with them. The shortener's job is to deliver clean state - preserved UTMs, preserved click identifier, fast redirect - so the banner can resolve before the tag fires.

What goes wrong on the redirect data plane

Three failure modes show up on every shortener that takes the redirect path seriously.

First, the click identifier survives but the consent signal does not. A Meta-ad click hits s.elido.me/abc123?fbclid=…. A shortener that passes the query string through redirects to https://customer.example/landing?fbclid=…, so the fbclid is preserved. The page loads, the banner appears, the user denies. Meta CAPI has already received a click keyed to that fbclid - but the user has now denied advertising use. The shortener did nothing wrong; the controller has a CAPI deduplication problem to solve on their endpoint. Elido passes the query string through when a link's pass-through switch is on (the default for new workspaces): the fbclid reaches the landing page, and a parameter already in the stored destination wins over one appended to the short URL. With the switch off, the redirect goes to the stored destination and the fbclid is dropped.

Second, a shortener can append identifiers the landing page does not understand. Some shorteners (Bitly's bitly_session, Rebrandly's _branch_match_id) append vendor-specific parameters that need stripping or special handling under denied consent. Elido appends nothing: the visitor lands on the destination exactly as you stored it, UTMs included.

Third, the landing page consent state is unknowable from the redirect's vantage point. The shortener cannot see a banner that has not loaded yet. Server-side fallback decisions cannot be conditioned on a consent state that does not yet exist. The only honest default: do not fire any advertising-purpose server-side event at redirect time; let the banner resolve, then let the page or its proxy fire with the consent state attached.

Vendors who fire Measurement Protocol or CAPI events directly from the edge are betting the user will grant consent. Under DMA Art. 5(2) that bet is not theirs to make. The EDPB Guidelines 02/2023 on the technical scope of Article 5(3) ePrivacy made the related point about pre-consent identifier injection: it is processing, it needs a basis, and the absence of a banner is not a basis.

The mitigations below are the ones that hold up under both GDPR and DMA. They share a common thread: the consent state has to be observed before any data is transmitted to a gatekeeper or used for advertising.

A four-step pipeline: click on s.elido.me, landing page where the banner resolves consent, first-party server that attaches the consent state, then the gatekeeper, with denied traffic falling back to aggregated counts

Measurement Protocol with consent state attached. GA4's Measurement Protocol accepts the same consent parameters as the gtag client. The pattern: the landing page resolves the banner, posts the consent state to the customer's first-party server, and the first-party server forwards a mp/collect request to GA4 with consent.ad_user_data and consent.ad_personalization set. Server-side, but downstream of consent resolution. Elido does not forward conversions to GA4, and its click forwarder sends no consent fields, so this step runs on your own server; the GA4 server-side tracking post linked above walks through it.

Conversion API with consent strings. Meta CAPI accepts data_processing_options and opt_out; LinkedIn's Conversions API accepts enlli; TikTok's Events API accepts limited_data_use. All of them signal the consent state to the platform. The pattern is identical: landing page resolves, posts to first-party server, first-party server fires with the consent state attached.

Aggregated server-side reporting. Where the consent state denies advertising or analytics use, server-side reporting that is genuinely aggregated and lacks per-user identifiers is generally fine under DMA Art. 5(2) and under GDPR Art. 6 on a legitimate-interest basis. The EDPB's Guidelines 04/2023 on anonymisation reiterate that pseudonymised data is not anonymous and that low-k k-anonymity still re-identifies. Conservative practice is to publish counts at the workspace level with a ≥10 threshold.

First-party identifier resolution. The most resilient approach is to identify the user on the landing page via a GDPR Art. 6(1)(b) signal - they signed in, they completed a form, they clicked a confirmed email link - and to attribute backwards. This does not depend on ad_storage or ad_user_data at all. The click attribution after Safari ITP post covers the pattern; it is the right answer for the post-DMA world too.

Three patterns turn up in tooling-vendor pitches and should not.

Two columns contrasting legal mitigations (Measurement Protocol post-resolution, CAPI consent strings, aggregated reporting, first-party id) against unlawful ones (edge CAPI pre-consent, hashing IP as anonymous, gatekeeper id syncing)

The first is firing CAPI events from the edge before the landing page consent resolves. This is the failure mode described above. There is no consent state to attach; firing the event implies the controller has obtained consent, which it has not. Some vendors describe this as "deterministic attribution"; under DMA Art. 5(2) it is a data combination operation the user has not authorised.

Hashing the IP and treating the hash as anonymous fails too. The EDPB has been clear since Opinion 4/2007 on the concept of personal data and reiterated in Guidelines 04/2023 that hashed identifiers remain personal data when the hash is reversible by anyone with access to the population. IP hashes are easily reversible at scale; the hash does not change the legal character of the processing.

Then there is server-side identifier syncing with gatekeepers. Forwarding the click event to Google or Meta with a hashed email or hashed phone number, and relying on the gatekeeper to match it against their own identifier graph, is the operation DMA Art. 5(2) specifically restricts. The matching is a cross-service data combination by the gatekeeper. Consent for it has to be explicit and at the user level. The presence of the hash does not make the operation lawful; the absence of consent makes it unlawful.

Recent CJEU and EDPB context

Two recent regulator moves sharpen the picture.

The CJEU's judgment in Case C-621/22 (Royal Lichtervelde, 2024) reiterated the joint-controller analysis from Wirtschaftsakademie (C-210/16) and Fashion ID (C-40/17). When a publisher integrates a third-party tag and that tag transmits user data to the third party, the publisher and the third party are joint controllers for that processing. GDPR Art. 26 requires a transparent arrangement between them. For a Consent Mode v2 customer, the Art. 26 arrangement with Google needs to be in place and the consent state has to flow honestly. Faking ad_user_data=granted to recover attribution is a joint-controllership liability for both sides.

The EDPB's Guidelines 03/2024 on consent signals in advertising contexts (consultation draft, final expected Q3 2026) explicitly addresses Consent Mode v2. The draft holds that the ad_user_data signal is, under GDPR Art. 7(4), conditional on freely given consent, and that banners bundling ad_storage with ad_user_data without granular controls fail the Art. 7 freely-given test. Most current banners bundle them. The redesign is on the customer; the shortener surfaces clean state, it does not design the banner.

For the broader transfer-impact picture - consent granted, data still leaves the EU - the Schrems II and tracking pixels post covers the TIA angle. DMA does not solve that problem; it adds another constraint.

What Elido does (and does not) do at the redirect layer

Elido is the processor; the controller decides the consent posture and operates the banner. The redirect data plane does the minimum:

  • Sends the visitor to the destination as stored, UTMs included. Query parameters on the short URL are copied only when the link's Pass query parameters through switch is on; then ad click identifiers (fbclid, gclid, msclkid, ttclid and others) reach the landing page, where your banner and tags decide what happens to them. Workspaces have a default for new links, on for workspaces created from 12 November 2026. There is no allow or deny list of parameters yet.
  • Gates its own pixel page. When a link opts in to a splash page with retargeting pixels, no pixel loads until the visitor accepts on a consent card, and a Sec-GPC: 1 or DNT: 1 header counts as a decline.
  • Fires a server-side advertising event only if you save a Meta or TikTok access token under Settings, Pixels. Then each click is sent as a Meta PageView or TikTok ViewContent with the IP shortened to its network and the user agent; in no-personal-data mode Meta events are skipped and TikTok gets the event without them. These events are not gated by the splash consent card, so only turn them on with a lawful basis for that processing. The internal click event written to our analytics store has the IP truncated to /24 or /48, with city-level location and the full user agent kept, per GDPR data minimisation. It is not shared with a third party unless you turn on a forwarding integration.
  • Does not forward conversions to GA4, Meta CAPI, LinkedIn, TikTok or Reddit, so consent-aware conversion forwarding is not available yet. Today conversion tracking attributes Stripe and Shopify revenue to a link, and click events (not purchases) can be forwarded to GA4, Mixpanel, Klaviyo, Brevo and Datadog; the setup is in the conversion tracking docs guide.
  • Reads no consent payload today, because there is no conversion forwarding to gate. Pass consent state in your own back-end when you send events to ad platforms.

There is no consent-state breakdown in /features/analytics today, because Elido never sees the banner's decision on your site. A per-campaign view of granted, denied and unset, so the marketing team can see how much attribution is lost to denials, is planned.

What Elido does not do: implement the banner, pre-decide consent, or honour granted consent for users who have not actually granted it. Those decisions live with the controller, where GDPR and DMA both put them.

The procurement question

For a controller scoping a shortener under DMA Art. 5(2), three questions.

Does the shortener forward click data to any third-party advertising or analytics service at redirect time, independent of the landing page consent state? If yes, that is a DMA Art. 5(2) exposure to terminate.

Does the shortener support consent-state forwarding to its server-side conversion endpoints? If no, the controller will need a separate server-side tagging proxy (GTM server container, Stape, Snowplow) between the landing page and the gatekeeper APIs.

Does the shortener's analytics layer share aggregated data with any third party? Some marketing-tilted ones publish "industry benchmarks" that turn out to be customer click data with sub-graphs identifiable by traffic shape - what's the joint-controller analysis under Wirtschaftsakademie and Fashion ID?

A shortener that hedges on any of these adds a DMA risk surface the controller will defend in audit.

Where this lands

Consent Mode v2 is not a marketing initiative. It is a compliance mechanism for DMA Art. 5(2) that ships through Google's tag platform. The four signals are honest about what consent has been obtained; server-side mitigations work when the consent state travels with the event; the attribution loss in a denied-consent world is real but smaller than it looks once first-party identifier resolution is in place. The shortener's part is a clean redirect and no advertising event before consent. Elido's server-side click events to Meta and TikTok don't carry a consent signal yet, so where consent decides, leave those forwarders off for the workspace or turn on no-personal-data mode (which skips Meta). Consent-aware forwarding is planned, so today that logic lives on the controller's own server.

The EDPB's expected Q3 2026 guidance will move the floor. Designing for the current floor only is short-sighted; designing for what Art. 5(2) intends - explicit, granular, freely given consent for cross-service data combination - is the position that survives the next round of enforcement.

Try Elido

Paste a URL, get a working short link

No signup. Link lives for 30 days. Sign up to keep it forever.

Free account required. The free plan includes 25 links in total. Already have an account? Log in

Try Elido

EU-hosted URL shortener with custom domains, deep analytics, and an open API. Free tier - no credit card.

Tags
consent mode v2
google consent mode
digital markets act
dma compliance
ad_user_data
ad_personalization
server-side tracking
measurement protocol

Continue reading