Missing is not zero.
When a source hasn’t synced, its value stays unknown and named. It never quietly becomes $0 in a total.
Find the spend that brings
new customers.
weive follows every first order in Stripe back through the ads and visits before it, so you can see which campaigns bring new customers, and which only take credit for them.
Recorded touchesOutcome
MetaAd click
Google AdsSearchOrganic searchVisit
DirectReturn
Stripe · First order$186Order #1042 · new customerMeta40%
Google Ads10%
Organic search10%
Direct40%
Every ad platform will tell you it found your customer. weive starts from the first order and works backwards, thread by thread, until you can see who really brought them in.
Change the rule.Watch the credit move.
One new customer, four recorded touches. Pick a rule and weive re-splits the same first order. The order never changes; only how its credit is shared.
- MetaAd click · Spring launch
- Google AdsSearch · running shoes
- Organic searchVisit · /trail-runner
- DirectReturn visit · checkout
- First orderCustomer cus_8f2 · new
First order · Stripe$186
Meta—
Google Ads—
Organic search—
Direct—
Every new customer,traced to the first order.
Connect your ad accounts and Stripe, then add the pixel. weive links the visits that started a journey to the payment that ended it, with the order one click away.
- First-order revenue from Stripe, not ad dashboards
- Campaign and keyword on every recorded touch
- The order, the customer, and the source on every row
Order #1042New customer · 4 touches
- Meta · Ad clickCampaign: Spring launch
- Google Ads · SearchKeyword: running shoes
- Organic search/products/trail-runner
- Stripe · First orderPaid · new customer$186
Every touch recorded before the order
Two platforms claim it.One order pays.
Google Ads and Meta both count the conversions they believe they drove. weive puts those claims beside the first orders that really happened, so the overlap is visible instead of double-counted.
- Platform-reported revenue, labelled as a claim
- First-order revenue matched to Stripe
- Return on spend from both connected ad accounts
Google Ads reports$41,200
Meta reports$38,600
First orders in Stripe$52,400
Known spend$21,500
New-customer revenue$52,400
Return on spend2.4×
SeptemberClaims overlap, orders don’t
Six rules,one set of orders.
First touch rewards the campaign that found the customer. Last touch rewards the one that closed. Compare them on the same orders before you move a single dollar.
- Every rule on identical first orders
- Credit by channel, per rule
- Totals always add back to the orders
New-customer revenue · $52,400Share by rule
First touchMeta leads
LinearEven split
Last touchSearch leads
MetaGoogle AdsOrganic and direct
Same orders, different rules
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.
What counts as a new customer?
A customer whose first payment in Stripe falls inside the period you are reading. Later payments are separate outcomes with their own journeys.
Does weive replace the ad platforms’ conversion counts?
No. Each platform’s count stays visible as that platform’s report. weive adds a separate view anchored to your real orders.
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.