A parameter an ad platform appends to your landing URL — fbclid for Meta, msclkid for Bing, rdt_cid for Reddit. It ties a conversion back to one ad click.

What does adscapi do with a click ID?

You capture it on the landing page and pass it in clickIds. adscapi forwards it to the platform that reads it — gated on ad-personalization consent where the platform requires it.

Which click IDs does adscapi forward?

fbc and fbp for Meta, rdt_cid for Reddit, msclkid for Bing, qclid for Quora, yclid for Yandex, tblci for Taboola, and more. The decoder lists every one the dispatchers read.

Does the decoder send my URL anywhere?

No. Parsing runs in your browser. Nothing leaves the page.

Click ID & UTM Decoder

Paste a URL or click ID — fbclid, gclid, msclkid, ttclid — and see which platform it belongs to and what adscapi captures server-side.

URL, query string, or click-ID parameter

Parsing runs in your browser. Nothing leaves this page.

Click-ID reference

Every parameter the adscapi dispatchers read, plus the well-known ones they ignore.

Parameter	Platform	What adscapi does with it
`fbclid`	Meta	Carried as fbc/fbp in clickIds; Meta receives them with adPersonalization consent.
`msclkid`	Bing (Microsoft Ads)	Forwarded as the msclkid query parameter on the UET beacon.
`rdt_cid`	Reddit	Sent as click_id on the conversion event.
`qclid`	Quora	Sent as the match key — the Quora dispatcher no-ops without it.
`yclid`	Yandex	Sent as the Yclid column in the offline-conversions upload.
`tblci`	Taboola	Sent as the click-id field — the Taboola dispatcher no-ops without it.
`ob_click_id`	Outbrain	Sent as the ob_click_id query parameter — the dispatcher no-ops without it.
`ndclid`	Nextdoor	Sent as customer.click_id with adPersonalization consent, never hashed.
`ylpcid`	Yelp	Sent as userData.ylpcid with adPersonalization consent, exact and unhashed.
`clickid`	Douyin	Sent as context.ad.callback with adPersonalization consent.
`callback`	Kuaishou	Sent as the callback query parameter — it authenticates the request per click.
`mark_id`	Weibo	Sent as the mark_id query parameter with adPersonalization consent.
`bd_vid`	Baidu	Used to build the logidUrl Baidu attributes the conversion to.
`gclid`	GA4 (Google Analytics)	adscapi accepts it in clickIds, but the GA4 dispatcher does not send it today.
`ttclid`	TikTok	Well-known TikTok click id; the TikTok dispatcher does not read it today.
`li_fat_id`	LinkedIn	Well-known LinkedIn click id; the LinkedIn dispatcher does not read it today.
`twclid`	X (Twitter)	Well-known X click id; the X dispatcher does not read it today.
`epik`	Pinterest	Well-known Pinterest click id; the Pinterest dispatcher does not read it today.
`sccid`	Snapchat	Well-known Snapchat click id; the Snapchat dispatcher does not read it today.

Frequently Asked Questions

Related Tools

Discover more free tools to fix your tracking

Platform Coverage Explorer

Search all 26 ad platforms adscapi dispatches to — support level, required secrets, and setup docs, always in sync with the library registry.

Try it now

UTM Campaign URL Builder

Build tagged campaign URLs with utm_source, medium, and campaign — plus the click IDs (fbclid, gclid) adscapi captures server-side. Copy and share.

Try it now

Event Match Quality (EMQ) Estimator

Check which identity fields you send — email, phone, external ID, click ID, IP — and estimate your Event Match Quality, with the fields to add to raise it.

Try it now

Ready to fire one event to every ad platform?

adscapi is free and open source. Set your platform tokens, call track() once, and every configured Conversions API receives the event — hashed the way each platform expects.

Get started npm install adscapi