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 campaigns that
bring real leads.
A form fill in an ad dashboard isn’t a lead until it lands in your CRM. weive credits the leads in HubSpot, across the touches recorded before each one.
Before the leadOutcome
Google AdsSearch
MetaLead adOrganic searchGuide
DirectDemo page
HubSpot · Lead created1 leadada@northwind.co · Book a demoGoogle Ads0.25
Meta0.25
Organic search0.25
Direct0.25
Platforms count form fills. Your sales team counts people. weive credits the leads that actually exist in HubSpot, and shows the platform’s count beside it, never instead.
Change the rule.Watch the credit move.
One demo request, four touches. Pick a rule and see how a single lead is shared across the campaigns that came before it.
- Google AdsSearch · marketing attribution
- MetaLead ad · guide
- Organic search/guides/attribution
- Direct/demo
- Lead createdForm: Book a demo
Lead · HubSpot1.00 lead
Google Ads—
Meta—
Organic search—
Direct—
Reported, created,and credited.
Platform-reported leads, leads that reached HubSpot, and leads matched to a recorded touch are three different counts. weive shows all three, so you always know which one you are reading.
- Platform counts kept as claims
- HubSpot leads as the outcome
- Matched leads you can open one by one
1,180Platform-reported
940Created in HubSpot80%
702Matched to a touch75%
September
Cost per lead,on leads you can open.
Read each channel’s spend beside the CRM leads it earned credit for. Cost per lead is calculated on real leads, under a rule you can name.
- Spend from both connected ad accounts
- Credited leads per channel
- Rule stated on the view
Leads · SeptemberLinear rule
Google Ads$18,600 spend412$45Meta$9,800 spend268$37Organic searchNo spend196—
DirectNo spend64—Leads · cost per lead
A lead with no touchstays honest.
Some leads arrive with no recorded touch at all. weive counts and shows them as unattributed instead of handing them to whichever channel spent the most.
- Unattributed is a state, not a channel
- Counted on every report
- Never redistributed by guesswork
Lead coverageSeptember
Leads in HubSpotAll created leads940Matched to a recorded touchCredited under the rule702No recorded touchShown as unattributed238
Unattributed is not a channel.These leads are counted and shown, never quietly given away.
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.
Which CRM does weive connect to?
HubSpot connects today, alongside Google Ads, Meta, and Stripe.
Does weive judge lead quality?
No. weive credits leads that exist in your CRM. What happens next, like a payment, can be read as a separate outcome.
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.