Missing is not zero.
When a source hasn’t synced, its value stays unknown and named. It never quietly becomes $0 in a total.
Follow every lead to
the first payment.
Connect HubSpot and Stripe. weive keeps the lead and the payment as separate outcomes, and when they belong to the same person, shows the whole thread from first click to first charge.
Click, lead, nurtureFirst charge
Google AdsSearch
HubSpotLeadEmailNurture
DirectBilling
Stripe · First charge$649Scale plan · 23 days after the leadGoogle Ads40%
Email20%
Direct40%
The lead and the payment are two different moments, often weeks apart. weive keeps both, links them when they’re the same person, and credits each one on its own.
Change the rule.Watch the credit move.
Twenty-three days from the first search to the first charge. Pick a rule and see how the payment is credited across the journey.
- Google AdsSearch · attribution software
- Organic search/case-studies
- EmailNurture · day 14
- Direct/settings/billing
- First chargeScale · monthly
First charge · Stripe$649
Google Ads—
Organic search—
Email—
Direct—
From first clickto first charge.
When a HubSpot lead and a Stripe customer share an email, weive shows one journey with both outcomes on it, in the order they happened.
- Lead and payment on one timeline
- Days from lead to payment
- Touches before and after the lead
ada@northwind.co2 outcomes · 23 days
- Google Ads · SearchCampaign: attribution software
- HubSpot · Lead createdForm: Start trialLead
- Email · NurtureDay 14 · opened
- Stripe · First chargeScale · monthly$649
Credit the lead.Credit the payment.
The campaigns that create leads aren’t always the ones present before payment. Read both splits side by side under the same rule.
- Separate credit for leads and payments
- The same rule on both
- Channel shifts made visible
Credit by outcomeLinear rule
On leads1,060 leads
On first charges$71,400
Google AdsEmail and organicDirect
Which campaigns bringleads that pay?
Ask weive where paying customers came from. The answer separates leads that paid, leads that haven’t yet, and records that couldn’t be linked.
- Paying leads by campaign
- Unlinked leads counted, not dropped
- Rule and coverage cited
Which campaigns bring leads that become paying customers?
Of 238 paying customers linked to a lead, Google Ads search came before 61% of those leads. 822 leads haven’t paid yet; they’re excluded, not counted as lost.
HubSpot leadsStripe paymentsLinear rule
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.
How does weive know a lead and a payment are the same person?
When the records share an identifier, such as the same email in HubSpot and Stripe, weive links them. Records that don’t match stay separate.
Is the payment credited to the lead source?
No. The payment is credited across the touches before it under your rule. The lead is a milestone on that path, not a channel.
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.