Missing is not zero.
When a source hasn’t synced, its value stays unknown and named. It never quietly becomes $0 in a total.
Credit the long cycle on
the record that matters.
B2B revenue starts as a lead and closes as a payment, often months later. Choose whether to credit the HubSpot lead or the Stripe payment, and see every touch recorded in between.
102 days of touchesOutcome
Google AdsDay 1Organic searchDay 12
MetaDay 57
DirectDay 99
Stripe · Invoice paid$6,490Northwind Ltd · annual planGoogle Ads40%
Organic search10%
Meta10%
Direct40%
A hundred days is a long time to remember where a deal began. weive remembers every recorded touch, from the first search to the paid invoice, and lets you choose which record earns the credit.
Change the rule.Watch the credit move.
A 102-day cycle. Try time decay and watch the early touches fade; try first touch and watch them take everything. Same deal, different questions.
- Google AdsSearch · revenue attribution
- Organic search/blog/models
- MetaRetargeting ad
- Direct/pricing · three visits
- Invoice paidScale · annual
Annual invoice · Stripe$6,490
Google Ads—
Organic search—
Meta—
Direct—
Months of touches,kept in one thread.
Early searches, a blog post, a retargeting ad, a form, and a paid invoice. weive keeps every recorded step on the journey, however long it takes.
- Every recorded touch, however early
- The lead and the payment on one timeline
- Gaps between touches shown in days
Northwind Ltd102 days
- Google Ads · Searchrevenue attribution
- Organic search/blog/models
HubSpot · Lead createdForm: Talk to salesLead- Stripe · Invoice paidScale · annual$6,490
Long cyclesmake the rule matter.
Compare how first touch, U-shaped, and time decay credit the same deals before deciding which question you’re really asking.
- Every rule on the same deals
- Credit by channel, per rule
- The deals themselves never change
Q3 deals · $118,400Share by rule
First touchEarly search wins
U-shapedBoth ends
Time decayLate touches win
Google AdsOrganic and MetaDirect
What you didn’t recordstays out of the credit.
Sales calls, events, and referrals that never reach a connected source aren’t invented. weive names them as unrecorded instead of spreading credit across what it can see.
- Recorded touches only
- Unrecorded activity named
- Coverage stated on every deal
Deal coverageNorthwind Ltd
Google Ads and MetaClicks and spendSyncedHubSpotLeadsSyncedStripeInvoices and paymentsSyncedCalls, events, referralsNot in a connected sourceUnrecorded
Unrecorded is not uninfluential.Credit covers what was recorded. The rest is named, not guessed.
Three promisesbehind every number.
Credit is not cause.
Attribution shows how a rule shares credit across recorded touches. It never claims an ad caused the sale.
One order, counted once.
Two platforms can claim the same sale. weive credits the payment once, and keeps each claim visible beside it.
Three stepsfrom scattered data to a decision.
Connect your sources.
Google Ads, Meta, HubSpot, and Stripe connect in a few clicks. One snippet adds the pixel to your site.
Choose your rule.
Linear, first touch, last touch, last non-direct, time decay, or U-shaped. Switch whenever you like; the outcomes never change.
Decide with the gaps in view.
Every number carries its sources, its rule, and its coverage, so the next budget move starts from evidence.
Worth askingbefore you start.
Can weive credit HubSpot leads and Stripe payments?
Yes. Pick whichever record marks the outcome you care about, or read both side by side.
How far back does a journey go?
Journeys include every touch recorded before the outcome in your connected data, so long cycles keep their earliest touches.
Does attribution prove a campaign caused the sale?
No. Attribution shows how credit is shared across recorded touches. weive keeps that separate from causal lift, so credit is never presented as proof.