msclkid (Microsoft Click ID) is the value Microsoft Advertising appends to your landing page URL when auto-tagging is on and someone clicks an ad. Microsoft describes it as a 32-character GUID that is unique for each ad click, and it’s what ties an offline conversion or a server-side event back to that click (Microsoft Advertising API docs).
How msclkid auto-tagging works
With auto-tagging enabled, the click ID arrives on the URL the way Microsoft’s example shows it: www.contoso.com/?msclkid={msclkid}. The same documentation adds a few details:
- auto-tagging is on by default for new accounts, and you can switch it off;
- adding or updating a conversion goal switches it back on automatically;
- Microsoft points to it for tracking leads through offline conversion goals.
So if your leads close on the phone or in a CRM, the msclkid is the thread between the sale and the ad.
Format
The account documentation calls it a 32-character GUID. Microsoft’s Conversions API guide shows it as a UUID written without hyphens, dd4afcccb1c94a4cad9544dd7e5006ab, and asks you to send it that way.
It’s one value per click. Two clicks on the same ad by the same person give you two IDs, which makes the msclkid stricter than gclid: Google says a GCLID can be created at impression time and reused when the same person clicks the same ad again (Google Ads Help).
Where you see it, and the 90-day limits
| Place | Microsoft’s rule |
|---|---|
| Landing page URL | msclkid appended after the ad click |
| Your storage | keep the most recent value per user in a first-party cookie, local storage or a server-side store, overwrite it when a newer one arrives, suggested retention 90 days |
| Offline conversion upload | conversion time within the last 90 days, later than the click, and inside the goal’s conversion window |
| Conversions API event | eventTime within the last 90 days, a limit separate from the attribution window |
The storage and API rules come from the Conversions API guide, the upload rules from the OfflineConversion reference, which also accepts a hashed email or phone instead of the MSCLKID for enhanced conversions. If the UET tag and the Conversions API both report the same conversion, Microsoft asks for a shared eventId so it isn’t counted twice.
If your leads come from Meta, start from a click ID you own. DropCPL records its own click_id for every Meta ad click on your landing page’s domain, next to the ad_id and the fbclid. Start free →
msclkid and the other click IDs
The big ad platforms all run the same play. gclid for Google, ttclid for TikTok and fbclid for Meta are all values the platform adds to your URL so you can hand the conversion back later. What differs is the way back: Microsoft takes it through offline conversion uploads or its Conversions API, Google through an offline conversion import, Meta through the Conversions API.
None of them is a good primary key for your own reporting. Each exists only for one platform’s traffic and is only readable by that platform. The key that survives every source is a click ID you generate yourself, with the platform’s ID stored next to it.
DropCPL works with Meta only and doesn’t connect to Microsoft Advertising. On Meta traffic it logs its own click_id with the ad_id, campaign_id and fbclid, in a first-party cookie set server-side on the landing page’s domain.
Related terms
- gclid: Google’s auto-tagging equivalent
- fbclid: Meta’s click identifier
- ttclid: TikTok’s click identifier
- gbraid and wbraid: Google’s parameters for some iOS clicks
- Tracking identifiers: click ID, UTM and first-party cookie compared