Attribution for Long Sales Cycles: Crediting a Late Deal

What follows is the detail: the mechanical problem, what it does to a budget two quarters later, the four things to persist and what destroys each, honest model choice, the reporting cadence, and the platform side.

Every ad platform measures conversions inside a window: a period after the click during which a conversion can still be credited to it. Google Ads lets you set that window per conversion action, currently up to about ninety days. Meta's default attribution setting is a seven day click window. LinkedIn offers a selectable range in a similar band. The exact numbers move; the shape does not. Once the window closes, the click is gone from the platform's ledger and nothing you upload later can be attached to it.

For a checkout that is fine, because the decision fits inside the window. For a deal that takes nine months it means the platform never learns the outcome at all. The model behind Smart Bidding or automated delivery is trained only on what happens in the first days after the click: a form fill, a content download, a demo request. Those are the events it will keep buying, whether or not they ever become customers. See attribution window for the mechanics in short form.

Follow the money through one planning cycle and the damage is easy to trace. The channels that start relationships, LinkedIn, YouTube, podcasts, a good comparison page, look expensive, because everything they produce closes too late to be counted. The channels that catch demand at the end, branded search above all, look extraordinary, because they are the last thing a buyer touches before signing something they had already decided to sign.

So budget moves down the funnel. Branded search gets more money than it can spend, the top of the funnel is cut, and for a quarter or two the numbers improve, because the pipeline built earlier is still closing. Then it runs out. Two quarters after the cut, new pipeline falls, and nobody links it back to a budget decision made three quarters before.

That delay is worth naming out loud in the planning meeting. In a nine month cycle, the feedback on a budget decision arrives roughly nine months late, which is longer than many people stay in the role that made it. Long-cycle attribution is mostly about shortening that loop honestly, rather than pretending the loop is short.

A nine month journey survives only if four pieces of data survive with it. Each one has a familiar way of getting destroyed.

• The first touch and its click IDThe gclid, fbclid, li_fat_id or msclkid captured on the very first visit, with the UTMs and the landing page. Capture it once, store it first-party, and never let a later visit overwrite it.
• Every touch in between, timestampedThe webinar in March and the pricing page in June are what makes a multi-touch model possible at all. Without timestamps you have a set of sources, not a journey.
• The identity joinThe link between the anonymous visitor and the CRM contact, made at the first form fill, call or booking. If that join is missing, everything before the form is orphaned.
• The deal value at closeThe amount and currency on the won deal, written back onto the same record. Without it you can only rank channels by lead count, which is the metric that caused the problem.

The usual causes of loss are mundane. Session storage that clears when the browser does. A cookie with a lifetime measured in days, which on Safari is shorter than most people expect. A CRM where lead source is one editable field that the last rep to touch the record overwrites. And a re-tracking migration halfway through the year that starts history again from zero.

Last click is the default in most reporting, and in a long cycle it is close to useless. In a nine month journey the last click is almost always branded search or a direct visit, because a buyer who has decided types your name. Crediting the deal there tells you that people who were already going to buy went and bought.

First click has the opposite failure. It gives everything to the top of the funnel, which flatters whichever channel produces the cheapest awareness traffic and hides how much of it never came back. In a nine month cycle it is at least the more useful error, because the top of the funnel is exactly what last click erases. It is still a single-touch model pretending a nine month decision had one cause.

The practical answer is to keep both visible and treat neither as the truth. First click tells you what starts pipeline. Last click tells you what closes it. The interesting number is the gap between them, and any channel with a large gap is a channel somebody in the business is arguing about.

4:33

Linear, time decay and position based all spread credit across the journey. Choosing between them is choosing a question, not choosing a truth.

• Linear splits credit evenly across every touch. It answers: which channels appear in the journeys that close? Useful for content and for channels that never get the last click, and it flatters anything that produces a lot of small touches.
• Time decay weights recent touches more heavily. It answers: what moved this deal in the months that mattered? Reasonable when the last quarter is the sales process, and it will always understate the first touch.
• Position based, usually forty per cent to the first touch, forty to the last and the rest shared, answers: what opened this and what closed it? For most B2B teams it is the least argued-about default.

Pick one as the number in the board deck and keep the others available for the argument. What matters more than the choice is being able to switch models without re-tracking, so a disagreement is settled by looking rather than by rebuilding. A model you cannot change is a model you will end up defending for the wrong reasons.

A nine month deal is rarely one person. A developer finds you through a comparison page, the head of marketing sees a LinkedIn ad two months later, the CFO reads the pricing page in month seven, and procurement books the call. Four people, four journeys, one deal.

Contact-level attribution either splits that deal across four records or credits it to whichever contact happens to sit on the opportunity. Neither is right. The workable pattern is to roll journeys up to the account: match contacts to a company by email domain or by the CRM's own account object, treat the account as the unit that converts, and put the deal value on the account rather than on a person.

It is not perfect. Free email addresses do not resolve, subsidiaries look like separate companies, and a buying committee member who never fills in a form stays invisible. But account level is close enough to make a channel comparison honest, and contact level is not. Multi-touch attribution for B2B goes further into the mechanics.

Long-cycle attribution fails more often on reporting habits than on data. Four changes make it usable.

1. Report on cohorts by first-touch month, not on the current month. The question is what January's spend produced, and the answer is not available in January. A cohort report lets a month keep filling in for a year instead of being judged the week it ends.
2. Treat time to close per channel as a first class metric. If LinkedIn deals close in eleven months and Google deals in five, that is a cash flow fact rather than a footnote, and it changes what a blended cost per acquisition means.
3. Use pipeline created as the leading indicator and revenue closed as the lagging one. Pipeline created is available now, moves with spend and is close enough to steer on. Revenue is the audit that tells you whether the steering was right.
4. Re-read the quarter nine months later, without changing the model. This is the discipline nobody keeps. A quarter's real channel mix is only visible once its deals have closed, and if the model changed in between, the comparison is worthless.

Together these turn attribution from a monthly scorecard argument into something closer to a cohort profit and loss. It is slower, and it is the only version that matches how the business actually earns.

The platform side of a long cycle has one hard constraint: a signal that arrives after the conversion window is worth nothing to bidding, however true it is. So you send two things at two different times.

The early signal is the intermediate stage: sales qualified lead, or opportunity created, whichever your team sets within a few weeks of the form fill. It arrives inside the window, it carries far more information than a raw form fill, and it is the signal automated bidding can actually train on. Give it an estimated value if you have a defensible average deal size, so value based bidding has something to work with.

The late signal is the closed deal with its real amount. It will often arrive too late to be credited to the original click, and it is still worth sending: it keeps your conversion actions honest, it feeds the platform's own modelling, and in accounts with a shorter tail it lands in time. Mature teams map the two to separate conversion actions, bid on the early one and report on the late one.

Watch the mechanics. Google's offline conversion import matches on the gclid and will not accept a click beyond its conversion window, so an intermediate stage inside that window is often the only thing that lands. Meta's Conversions API matches on the click ID plus hashed identifiers, so a later event can still match the person even where the click has aged out. LinkedIn and Microsoft Ads accept the equivalent uploads.

LeadJourney captures the click IDs on the first visit, server-side on your own domain at 95%+ accuracy: gclid, gbraid and wbraid, fbclid, li_fat_id and msclkid, plus the UTMs and the landing page. That anonymous first click is joined to the person at the form fill, call or booking, and the journey then follows the CRM stages to the closed deal. There is no attribution window cutoff in LeadJourney's own reporting: the journey keeps recording until the deal closes, however long that takes, and time to close per channel is a report rather than a spreadsheet exercise.

First click, last click, linear, time decay and position based are switchable without re-tracking, so changing the model is a reporting decision instead of a migration. HubSpot, Salesforce, Pipedrive, Close, Attio, GoHighLevel, ActiveCampaign and Odoo have native integrations, any other CRM connects by webhook or Zapier, and the connection runs both ways: LeadJourney reads stages and deal values, and writes the first touch, campaign, click ID and full journey back onto the contact and the deal, so sales sees the source before the first call.

You map any lifecycle or deal stage onto a conversion action, qualified lead, proposal sent, closed won, or all three, and the event goes server to server with the deal amount and currency attached: to Meta over the Conversions API with event deduplication, to Google Ads as offline conversion imports matched on the gclid, to LinkedIn over its Conversions API and to Microsoft Ads as offline conversions. The honest limit is the one every tool shares. An upload cannot beat a platform's own conversion window, which is exactly why the intermediate stage matters. Setup is one script on the site or in the GTM container, live in about 21 minutes, hosted in Frankfurt with a signed data processing agreement.

Read verified reviews on Trustpilot, G2 and leadjourney.io/testimonials.

Related pages: long sales cycle attribution and the multi-touch attribution guide for B2B. For the platform side, read sending LinkedIn CRM deals back over the Conversions API. For the definitions, see attribution window and time decay attribution, and for the metric a long cycle distorts most, the true cost per lead.