Missing is not zero.
When a source hasn’t synced, its value stays unknown and named. It never quietly becomes $0 in a total.
Know which channels
earn your orders.
Connect your ad accounts, Stripe, and the pixel. weive credits every order once, across the touches before it, and keeps each platform’s own claim beside it, never added on top.
Before the orderThe order
MetaReel ad
TikTokTagged link
Google AdsBrand search
DirectCart
Stripe · Order$300Order #EX-1042 · paidMeta$75
TikTok$75
Google Ads$75
Direct$75
Add up what every ad platform claims and you’ll usually have sold more than you did. weive starts from the orders you actually took, and counts each one exactly once.
Change the rule.Watch the credit move.
One $300 order, four touches across three channels. Pick a rule and see how the same order is shared.
- MetaReel ad · new arrivals
- TikTokTagged link · creator
- Google AdsBrand search
- Direct/cart
- Order #EX-1042Paid
Order · Stripe$300
Meta—
TikTok—
Google Ads—
Direct—
When two platformsclaim one order.
Each platform reports the conversions it believes it drove. weive shows those claims overlapping the orders that really happened, so you can see the overlap instead of paying for it twice.
- Platform-reported revenue per channel
- Order-matched revenue beside it
- Overlap made explicit, never summed
Google Ads reports$52,000
Meta reports$56,000
Orders in Stripe$80,000
Claims added up$108,000
Orders taken$80,000
Counted once$80,000
September
Claims drift up.Orders stay honest.
Track matched revenue beside what platforms report, day by day. When the lines separate, you know exactly where to look.
- Daily matched revenue from Stripe
- Platform-reported revenue as a dashed claim
- Known spend from every connected account
Matched revenue$80,000Derived
Known spend$26,000Observed
Return3.1×Within scope
04081216202530
Matched to ordersPlatform-reported
September
One order,shared to the cent.
Open any order to see each touch’s share under your rule. Shares always add back to the order, so nothing is created or lost along the way.
- Each touch’s share, in dollars
- Shares sum to the order exactly
- Refunds read straight from Stripe
Order #EX-1042Linear · $300
Meta · Reel ad01 Sep25%$75.00TikTok · Tagged link05 Sep25%$75.00Google Ads · Brand09 Sep25%$75.00Direct · Cart11 Sep25%$75.00Shares add to $300
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 store data does weive read?
Orders and payments from Stripe. Visits and campaign tags come from the weive pixel on your store pages.
Do refunds change the credit?
Refunded payments are read from Stripe and reflected in the revenue for that period.
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.