Short Answer
Most lead-generation advertisers need both, for different jobs. A conversions API sends events from your server to the ad platform as they happen, so the platform receives a more complete signal than a browser tag alone provides. An offline conversion import sends what happened later in your CRM, such as a qualified lead or a closed deal, so the platform learns which clicks produced customers. Both paths need a deduplication rule and a consent rule before any data leaves your systems.
What A Conversions API Does
A conversions API is a server-to-platform connection. When a visitor submits a form, your server sends that event to Meta, Google, LinkedIn or Microsoft directly, alongside the browser tag. That helps when browsers block or drop tags.
Sending the same event twice is the most common fault. Meta treats a Pixel event and a Conversions API event as one only when they carry the same event_id and the same event name and the second arrives within 48 hours of the first one Meta receives. Customer details sent this way are normalized and hashed first, but hashed data is still personal data and stays under your consent and privacy obligations.
What Offline Conversion Imports Do
An offline import tells the platform what happened after the form. Your CRM records that a lead was qualified, became an opportunity or became a customer, and that outcome is uploaded and matched to the original ad click by its click ID (GCLID for Google, MSCLKID for Microsoft) or by hashed lead details such as email and phone. Each platform sets a clock.
| Platform and method | What matches the outcome | Upload window |
|---|---|---|
| Google Ads offline conversion import | GCLID | 90 days after the last click |
| Google Ads enhanced conversions for leads | Hashed lead details, with the GCLID whenever possible | 63 days |
| Microsoft Advertising offline conversions | MSCLKID, or SHA-256 hashed email or hashed phone | Conversion time within the last 90 days |
| LinkedIn Conversions API | SHA-256 hashed email and other identifiers | 90 days |
| Meta Conversions API for CRM | Leads from Meta Lead Ads (Instant Forms) | No window stated; Meta's fit guideline is a target stage reached within 28 days of the lead |
If your sales cycle runs longer than the window, the final sale never reaches the platform. Import an earlier stage, such as qualified lead, instead.
What Changed In 2026
Google now routes these uploads through Data Manager. Google set June 15, 2026 as the date offline conversion import and enhanced conversions for leads uploads move to the Data Manager API, and from that date the Google Ads API accepts no new adopters of offline conversion imports. In April 2026 Google combined enhanced conversions for web and for leads into one setting. Meta describes its separate Offline Conversions API as legacy and points advertisers to the Conversions API. If your import was built before mid-2026, check which method it uses.
How To Decide
| Question | If yes | If no |
|---|---|---|
| Do most leads start on your website form? | A conversions API for the form event, plus an import for later CRM stages | If most start in Meta Lead Ads, Meta's Conversions API for CRM covers the CRM stages |
| Does the click ID reach your CRM on most leads? | Click-ID imports match reliably | Fix capture first, or rely on hashed lead details |
| Is your sales cycle shorter than the import window? | Import the won deal | Import an earlier stage, such as qualified |
| Are CRM stages updated within days? | Daily or weekly uploads are worth running | Fix the stage process first; late data teaches the platform little |
| Do you record each lead's advertising consent? | Upload only consented leads | Do not upload until you do |
Questions To Ask Before You Build
- Who owns the CRM stage definitions, and do sales and marketing use the same ones?
- How will you test that the browser and server copies of an event count once?
- Which consent state allows a lead to be uploaded, and where is it stored?
- How often will uploads run, and who is told when one fails?
- Which stage, and which value, should each platform optimize toward?
Common Mistakes
- Sending the same outcome through both paths without deduplication, which inflates conversions.
- Uploading outcomes after the platform's window has closed.
- Treating hashed data as anonymous.
Next Step
The Conversion Signal Readiness assessment scores your current tracking against these questions. To have the architecture reviewed, see Server-Side Conversion Engines and request a CAPI Architecture Review, or read how DIMG builds each path on Conversion API and Offline Conversions.