RevOpsXL
GTM Diagnostic Request the audit

HubSpot offline conversions: tie ad spend to revenue on long sales cycles

Alexandra-Emily Kokova

Alexandra-Emily Kokova

Published 12 November 2026 - 7 min read

Google, LinkedIn and Meta accept a conversion for a set number of days after the ad, and a six-month deal closes after all of them. Send the stage that falls inside the window and answer the revenue question in the CRM.

In short

HubSpot’s ad conversion events send a contact’s lifecycle stage change back to Google Ads, LinkedIn or Meta. Google takes click-ID conversions for up to 90 days after the click, and Meta wants the optimised stage within 28 days of the lead, so closed-won on a long cycle arrives too late. Send SQL or opportunity created, value it by how often it closes, and read revenue against spend in the CRM with a two-quarter lag.

On this page

Ad platforms count what happens on the page: a form fill, a demo request, a download. The revenue arrives in the CRM six or eight months later, on a deal the ad platform never hears about. The usual way the two meet is a spreadsheet built by hand once a quarter, and by the time it’s built the next quarter’s budget is already committed.

HubSpot can send a contact’s lifecycle stage change back to Google Ads, LinkedIn and Meta. Those are offline conversions, and they let the platforms learn which clicks turned into sales conversations. They don’t fix a long cycle by themselves, since every platform stops accepting conversions well before a six-month deal closes.

What an offline conversion is

An offline conversion is an event that happens outside the ad platform, usually in the CRM, and gets sent back to it afterwards. The platform matches it to the person who clicked, counts it against that campaign, and uses it to decide who to bid on next.

Google matches on the click ID it adds to the landing page URL, the GCLID, and on hashed contact details through enhanced conversions. LinkedIn matches on a hashed email plus name, job title, company and country, with its own click ID as a backup. Meta goes through its Conversions API with a click ID and, optionally, an email or phone number, and needs a Meta pixel on the site. If the click ID was never captured, or the email on the contact doesn’t belong to anyone on that network, the conversion has nobody to land on.

Why closed-won arrives too late

Each platform accepts a conversion for a limited time after the ad interaction. Most B2B sales cycles are longer.

PlatformLimitFor a six-month deal
Google Ads, click IDImported up to 90 days after the clickClosed-won is rejected
Google Ads, enhanced conversions for leadsUp to 63 days after the last clickClosed-won is rejected
LinkedInThe event has to be dated within the past 90 days. Lead, MQL, SQL and purchase types can use a 180- or 365-day windowAn SQL counts. A purchase can, if the longer window is switched on
Meta, conversion leadsThe stage you optimise for has to happen within 28 days of the lead being createdOnly an early stage works

Take a made-up buyer who clicks a Google ad in January, books a demo in February and signs in August. The demo fits inside Google’s 90 days. The signature, seven months after the click, doesn’t. Google’s help page says it in fewer words: if your conversion happens after 90 days, upload an event that happens within them. It also asks for uploads at least daily.

LinkedIn is the exception worth knowing about. Its MQL and SQL conversion types only arrived in the API in August 2026, and its own documents disagree on the default window, so check the setting on each conversion rather than assuming it.

What HubSpot sends natively

HubSpot calls them ad conversion events. They’re set up in the ads tool for each connected ad account and come with Marketing Hub Starter, Professional and Enterprise, with a limit of 5, 50 and 100 events.

The trigger that matters for B2B is a lifecycle stage change. Google and Meta also accept form submissions as a trigger, and Meta accepts page views. Deal stage changes aren’t among the native triggers. Sending opportunity created or closed-won from the deal pipeline takes a custom build, usually a workflow that calls Google’s offline conversion API, or a third-party connector.

Only stage changes made after the event is created get sent, so nothing from last quarter is backfilled. The value is also a fixed number per event. HubSpot used to offer a deal amount option for Google and has removed it, so the platform gets the same figure for every SQL, however large the deal turned out to be.

HubSpot also asks whether to send every contact who reaches the stage or only the ones who interacted with your ads. It recommends sending everyone and letting the platform do the matching. Meta is stricter on its side. It only takes lifecycle data for contacts who came through its own lead ads, Instant Forms or Website Forms, and it accepts a backfill of seven days at most.

Which stage to send

Pick the earliest stage your sales team would stand behind in a pipeline review. For most B2B teams that’s sales qualified lead, or the point an opportunity is created. It falls inside the windows, and it’s much closer to revenue than a form fill.

MQL has the most volume, which is why it gets picked. If an MQL is anyone who downloaded two guides, the platform will learn to find people who download guides, and it will find them cheaply. Meta puts a number on the useful range: it wants a stage that roughly 1% to 40% of leads reach, and at least two stages in the funnel it can see.

For the value, use what the stage is worth on average rather than the average deal. If a third of SQLs close and the average deal is €30,000, an SQL is worth about €10,000 to the bidding. Those figures are made up for the example. Yours come from last year’s closed deals, and they change when the sales team changes how it qualifies.

Reading spend against revenue

Offline conversions change what the platforms bid on and nothing else. The platform only ever sees the early stage, so what the ads earned has to be worked out in the CRM.

Group deals by the quarter the first contact on them was created, and keep the campaign and source on that contact. Read a quarter’s spend against the pipeline created from it, then against revenue two or three quarters later, when those deals have closed.

The source on the contact has to be right first. If most contacts arrive as Offline Sources because an enrichment tool created them, the cohort has nothing to group by, which is the subject of HubSpot lead source. Who gets credit once the deal closes is a separate argument, covered in closed deal attribution, and the models behind it are in marketing attribution.

What none of this separates is the effect of a better signal from the budget change that usually ships with it. If you want to know which one moved cost per opportunity, change one of them per quarter.

Alexandra-Emily Kokova

Hands-on practitioner, ecosystem architect and GTM strategist, in and around HubSpot since 2014, building the systems B2B revenue runs on across the EU, UK, Nordics, the Gulf and North America.

Published 12 November 2026

Contact me on LinkedIn

Common questions

HubSpot calls them ad conversion events. They send a contact’s lifecycle stage change, and on Google and Meta a form submission, back to a connected Google Ads, LinkedIn or Meta ad account, so the platform can count it against the ad the person clicked.

Marketing Hub Starter, Professional and Enterprise. Starter allows 5 events, Professional 50 and Enterprise 100.

Not with the native ad conversion events, which use lifecycle stages and form submissions. A deal stage needs a custom build, such as a workflow that calls Google’s offline conversion API, or a third-party connector.

Up to 90 days after the click when matching on the GCLID, and up to 63 days after the last click for enhanced conversions for leads. Conversions uploaded later are not imported.

Not when deals take longer than the platform’s window. Send the earliest stage sales would stand behind, usually SQL or opportunity created, with a value based on how often that stage closes.

Get the next field note by email

New field notes twice a month. One short email when one goes up, nothing else.