B2B inbound series · 2025

Offline Conversions

CRM signals ad platforms trust

VertoDigital VertoDigital
Ebook

The offline conversion your ad platforms can actually use

A practical guide to defining, capturing, and matching offline conversions - so CRM data feeds smart bidding with a signal that filters for quality, comes in volume, and lands close to real-time.

Download PDF

PDF · 773 KB · Free, no form

What's inside

Four chapters on defining, tracking, and collecting offline conversions that actually improve smart bidding.

01 Why offline conversions need to be part of any B2B inbound strategy
02 How to define your offline conversions - lifecycle stages and custom ICP criteria
03 Defining offline conversion tracking - ClickID matching across ad platforms
04 How to collect offline conversions - capture, persist, and choose your stack

32%

of conversions risk going unattributed due to missing ClickIDs, based on a pool of three B2B accounts (2023-2024)

Who it's for

  • CMOs and VPs of Marketing who need pipeline signals ad platforms can actually bid on.
  • RevOps and marketing-ops leads building or auditing the CRM-to-ad-platform data flow.
  • B2B teams running Google, LinkedIn, Microsoft, or Facebook Ads for demand gen.

Defining an ICP Lead conversion

When lifecycle stages fall short on volume or timing, we build a custom conversion instead - the 'ICP Lead.' It scores a lead against company size and title fit the moment it hits the CRM, with no behavior score and no lag.

Company size

  • >500 employees
  • OR >$40M in VC funding
  • OR >$50M in ARR

Job title (AND company size)

  • Data & integration roles - data engineer, ELT/BI specialist, integration architect or analyst
  • Technology & security leadership - VP/Director/Head of IT, Security, Data, Digital, or Product
  • C-suite - CEO, CTO, CDO, CIO, SVP, AVP

How ClickID matching works across ad platforms

Every offline conversion needs a ClickID - the unique identifier an ad platform attaches to a click's URL - to match a later CRM event back to the ad, campaign, and keyword that drove it. Each platform uses its own parameter and its own required fields, so the same CRM event has to be formatted differently depending on where it's headed.

Platform ClickID Required to match Optional parameters
Google Ads gclid ClickID, conversion name, timestamp Conversion value
LinkedIn Ads lin_fat_id Conversion name First name, last name, company name, email, phone number, job title, timestamp
Microsoft (Bing) Ads msclkid ClickID, conversion name, timestamp Conversion value
Facebook Ads fbclid ClickID, conversion name, conversion value, timestamp First name, last name, email, phone number

Building an import flow that actually matches

Native connectors move fast but lose conversions to timestamp restrictions. A custom flow through Zapier, HighTouch, or Segment lets you hold the upload and adjust the timestamp first - one account matched 100% of its eligible MQLs in Google Ads this way.

Step 1

CRM trigger

Lead reaches the MQL stage

Step 2

Hold upload

Wait until the click is 6+ hours old

Step 3

Adjust timestamp

Add 1-2 days, set the time zone

Step 4

CAPI upload

ClickID + conversion name + timestamp

Result

Google Ads

100% match in eligible MQLs

Master trigger

CRM: lead enters SQL stage

Connector

Zapier - one trigger, all platforms

Google Ads · LinkedIn Ads · Facebook Ads

Common Google Ads match errors

ErrorWhat it means
Identifier too oldGoogle only keeps a gclid for 90 days - upload more frequently, or use a conversion that fires sooner.
Click too recentGoogle needs 6+ hours between the click and the upload - retry once that window passes.
Invalid conversion timeA conversion can't predate its click - pad the upload by 1-2 days and check the time zone.

What switching connectors actually changes

We compared native CRM connectors against custom third-party flows across four B2B accounts, all matched in Google Ads (Aug-Sep 2024).

SAL - Company 1

A 3rd-party connector matched 26 SALs, vs. 7 through SFDC's native connector and 22 through the MOps native connector - 73% more than SFDC, 15% more than native MOps.

MQLs & Opps - Company 2

A 3rd-party connector (Zapier) matched 10 MQLs vs. 9 in native HubSpot, and 8 Opps vs. 5 - 10% more MQLs, 37% more Opps.

MQLs - Company 3

A 3rd-party connector matched 96 MQLs vs. 66 through native Marketo - 31% more.

MQLs - Company 4

A 3rd-party connector matched 959 MQLs vs. 723 through native Marketo - 25% more.

Frequently asked questions

What is a ClickID?
A ClickID is a unique identifier - gclid for Google Ads, fbclid for Facebook, msclkid for Microsoft, lin_fat_id for LinkedIn - that an ad platform attaches as a querystring parameter when someone clicks an ad. It encodes the campaign, targeting, and ad details behind that click, so a later CRM event can be matched back to the exact ad that drove it.
Is the MQL stage a good offline conversion to track?
Sometimes. MQL scoring based on behavior (page views, email opens) introduces reporting delay and inconsistent volume - 8 out of 10 MOps lifecycle journeys we review aren't structured for it. MQL works as an offline conversion only when the scoring is attribute-based (job title, company size) rather than behavior-based; otherwise, a custom ICP Lead conversion is more reliable.
Native connectors or third-party connectors - which should I use?
Native connectors (HubSpot, Marketo, Pardot) are the fastest to set up - a few minutes over OAuth - but ad platform API restrictions around conversion timestamps mean fewer conversions actually match. Third-party connectors (Zapier, HighTouch, Segment) let you control the delay and timestamp before uploading, which is why they've matched up to 73% more conversions in our client accounts.

Outsmart, don't outspend.