Conversions API Beyond Meta: LinkedIn, Snapchat, Reddit (and TikTok, Pinterest, Google Ads)
Once you've set up the Conversions API for Meta, the next question is usually: "We also run LinkedIn / Snapchat / Reddit — do they have the same thing?" They do. Almost every major ad platform now has a server-side conversions API, built on the same idea: send hashed customer data and a click ID from your server, and let the platform match it to an ad.
The details differ. Here's what you need to know for each.
The common pattern
Every platform's Conversions API needs four things:
- An ID of the pixel, tag or ad account the events belong to.
- A token that proves you're allowed to send events.
- Identifiers to match the event to a person: hashed email and phone, and the platform's own click ID from the ad link.
- A deduplication ID, if the same event is also sent by the browser tag.
The click ID is the part people forget. Each platform adds its own parameter to the landing page URL, and you need to save it with the lead:
| Platform | Click ID in the URL |
|---|---|
| Meta | fbclid (sent as fbc) |
li_fat_id | |
| Snapchat | ScCid |
rdt_cid | |
| TikTok | ttclid |
epik | |
| Google Ads | gclid |
LinkedIn Conversions API
LinkedIn clicks are usually the most expensive of all the platforms here, especially for B2B audiences, so every lost conversion hurts. Key facts from LinkedIn's documentation:
- Each event needs at least one identifier. LinkedIn recommends sending both SHA-256 hashed email and the
li_fat_idclick ID for the best match. The click ID appears in landing page URLs when enhanced conversion tracking is enabled. - LinkedIn asks for events in real time or at least within a day. Data can take up to 72 hours to appear in reporting.
- Attribution windows can reach 180 days, and up to 365 days for some lead and purchase types — useful for long B2B sales cycles.
- Events sent through both the Insight Tag and the API are deduplicated.
- Integration routes: a LinkedIn marketing partner (GTM, Zapier, CDPs) or a direct integration, which LinkedIn estimates at 1–2 weeks.
Snapchat Conversions API
- The token is created in Ads Manager → Business Details → Conversions API Tokens; you need to be an organization admin. Snap says these tokens don't expire.
- Events go to your Snap Pixel ID — for website and offline events alike — so server events and pixel events can be deduplicated.
- The request format is close to Meta's: an event name, time, action source, hashed user data and custom data.
- Save the
ScCidclick ID from the landing URL and send it with the event for better matching.
Reddit Conversions API
- Authentication uses a conversion access token — a non-expiring key generated in Reddit Ads — plus your Pixel ID.
- Every event needs at least one attribution signal: the
rdt_cidclick ID, email, IP address with user agent, or a mobile advertising ID. Send as many as you have. - A unique conversion ID per event prevents double counting with the Reddit Pixel.
TikTok, Pinterest and Google Ads
The same pattern applies. TikTok's Events API mirrors Meta closely (pixel code, access token, ttclid, event_id). Pinterest's Conversions API uses an ad account ID and a conversion token. Google Ads accepts offline conversions through the Data Manager API, matched by gclid or hashed email and phone.
One CRM, many platforms
Building and maintaining seven integrations is where most teams give up. Every platform has its own event names (Meta's Purchase is Snapchat's PURCHASE and Reddit's Purchase), its own hashing rules and its own quirks.
LeadMe solves this from the CRM side: you connect your lead source once, and send the same stages to Meta, TikTok, Google Ads, Snapchat, Pinterest, Reddit, Yandex and VK. Its website script stores the click IDs of all these platforms with each lead, and each platform's event names and formats are mapped automatically. LinkedIn isn't supported yet — for LinkedIn, use a partner integration such as Zapier or a direct integration for now.
Quick answers
Is a "conversions API" a standard?
No. The name is shared, but each platform has its own API, fields and rules. The concept is the same: server-side events with hashed data and click IDs.
Do I still need each platform's pixel or tag?
Generally yes — the browser tag plus the server API, with deduplication. Same logic as Conversions API vs Meta Pixel.
Which platform should I add after Meta?
The one where you spend the most after Meta. The more expensive the click, the more each recovered conversion is worth.
Related: What Is Meta Conversions API · How to send CRM sales to Meta