What is dclid?

A dclid makes paid traffic look like direct traffic

This is the one that costs people real money, and it comes straight from Google's own Analytics documentation. Here is how traffic-source dimensions resolve depending on what's on the URL:

Read that middle row again. A visitor who clicked a paid DV360 display ad, and arrived carrying a dclid and nothing else, is recorded in Analytics as Direct / Unassigned — indistinguishable from someone who typed your URL into the address bar.

Nothing errors. The dclid is present and working perfectly well for its actual job. It simply isn't a signal Analytics uses to populate source and medium, the way gclid is.

The fix is manual tagging. Put UTM parameters on your DV360 destination URLs. When both are present, Analytics uses the UTMs — so you get real channel reporting and keep the dclid doing its Floodlight job underneath.

It is not a gclid substitute

The two look like siblings and behave like distant cousins. dclid comes from Display & Video 360; gclid comes from Google Ads (and Search Ads 360 and DV360). The critical divergence is what you're allowed to do with them afterwards.

Google Ads offline conversion import does not accept a dclid. The identifiers it takes for uploading offline click conversions are gclid, gbraid and wbraid. dclid appears nowhere in that set.

So the instinct you'd carry over from gclid — capture it on landing, store it against the lead in your CRM, upload the conversion weeks later when the deal closes — does not transfer. A dclid sitting in your database has no Google Ads importer to go to.

Its conversion path is a different stack entirely: Floodlight activities in Campaign Manager 360 and Display & Video 360, with the Google tag reading the dclid on the landing page at the time of the visit.

What it actually needs to work

Google's requirement is short but strict. Floodlight activities have to be implemented either using the Google tag or Google Tag Manager with the Conversion Linker. The Google tag reads and tracks the dclid on the landing page, and that read is what later lets DV360 understand the click activity that led to a conversion.

Miss the Conversion Linker in a GTM setup and the parameter arrives on the page, sits in the URL, and is never captured. Same silent-failure shape as a redirect stripping it — except here nothing removed it, nothing read it.

A real value looks like this:

?dclid=CJKu8LrQxd4CFQ1qwQodmJIElw

The expand dclid macro

Enhanced attribution is normally switched on at the Floodlight configuration level. If you can't or don't want to change that account-wide setting, there's a per-placement escape hatch: the "expand dclid" macro, written %edclid!.

Adding dclid=%edclid! to an individual click tag enables enhanced attribution for that click tag even if it isn't enabled for the Floodlight configuration. Useful when you're testing on one placement, or when the account-level change is somebody else's decision.

Common dclid failure modes

• Reading Analytics as if display drove nothing. The big one. Untagged DV360 traffic hides inside Direct, so display looks worthless and search looks better than it is.
• Storing it for a Google Ads upload that can't happen. dclid isn't an accepted offline-conversion identifier. Build the Floodlight path instead.
• GTM without the Conversion Linker. The parameter lands and nothing reads it.
• Assuming auto-tagging covers reporting. It covers attribution inside the Google Marketing Platform. It does not give you channel reporting in Analytics — only UTMs do that.
• Brave. Strips dclid by default for every user — see the Click ID Survival Matrix.

For the wider landscape, see the click ID explainer; for the full build, the tracking-setup playbook.