Missing is not zero.
When a source hasn’t synced, its value stays unknown and named. It never quietly becomes $0 in a total.
Every repeat order is its own outcome in weive, with its own journey. See what happened between the first purchase and the next, and which channels were there when customers returned.
A second order isn’t a footnote to the first. weive treats it as a new outcome, with its own touches, so loyalty gets measured on its own terms.
A returning customer, four touches since their first order. Pick a rule and see who gets credit for bringing them back.
Read first orders and repeat orders as separate outcomes, month by month. Both come straight from Stripe, so the split is a fact, not an estimate.
weive keeps the visits and clicks recorded after the first order, so the story between purchases stays intact and the repeat order can be credited fairly.
Ask weive about repeat revenue and the answer keeps its limits: what was credited, under which rule, and what credit can’t tell you.
Meta retargeting was credited $8,200 of repeat revenue under Linear, about 20% of the total. Credit shows how revenue was shared; it doesn’t show customers returned because of the ad.
When a source hasn’t synced, its value stays unknown and named. It never quietly becomes $0 in a total.
Attribution shows how a rule shares credit across recorded touches. It never claims an ad caused the sale.
Two platforms can claim the same sale. weive credits the payment once, and keeps each claim visible beside it.
Google Ads, Meta, HubSpot, and Stripe connect in a few clicks. One snippet adds the pixel to your site.
Linear, first touch, last touch, last non-direct, time decay, or U-shaped. Switch whenever you like; the outcomes never change.
Every number carries its sources, its rule, and its coverage, so the next budget move starts from evidence.
Yes. Any later Stripe payment is a separate outcome, whether it’s a repeat order or a subscription renewal.
You can read every payment a customer has made from connected Stripe data. weive doesn’t project future value.
No. Attribution shows how credit is shared across recorded touches. weive keeps that separate from causal lift, so credit is never presented as proof.