See what brings
customers back.

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.

Change the rule.Watch the credit move.

A returning customer, four touches since their first order. Pick a rule and see who gets credit for bringing them back.

  1. EmailWin-back · 15% off—
  2. MetaRetargeting ad—
  3. Google AdsBrand search—
  4. Direct/account/orders—
  5. Repeat orderSecond purchase$92
Repeat order · Stripe$92
Email——
Meta——
Google Ads——
Direct——

Watch repeat revenuegrow beside the first.

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.

  • First and repeat payments kept apart
  • Monthly totals from connected payments
  • Every bar opens to the orders inside it
Revenue by order typeQ3 · Stripe
$61k
$70k
$79k
JulyAugustSeptember
Repeat ordersFirst orders

The touchesbetween two purchases.

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.

  • Touches after the first order, in sequence
  • Each repeat order credited on its own journey
  • The customer’s history one click away
Customer cus_31aTwo outcomes
  1. Stripe · First orderPaid$64
  2. Email · Win-back15% off, opened
  3. Meta · RetargetingAd click
  4. Stripe · Repeat orderPaid$92

Ask what brought them back.Get an honest answer.

Ask weive about repeat revenue and the answer keeps its limits: what was credited, under which rule, and what credit can’t tell you.

  • Answers cite the rule and the sources
  • Coverage stated in every answer
  • No causal claims from credit alone
Did retargeting drive repeat orders last quarter?

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.

Stripe paymentsMeta adsLinear rule

Three promisesbehind every number.

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 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.

01

Connect your sources.

Google Ads, Meta, HubSpot, and Stripe connect in a few clicks. One snippet adds the pixel to your site.

02

Choose your rule.

Linear, first touch, last touch, last non-direct, time decay, or U-shaped. Switch whenever you like; the outcomes never change.

03

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.

Does weive track renewals as well as repeat orders?

Yes. Any later Stripe payment is a separate outcome, whether it’s a repeat order or a subscription renewal.

Can I see lifetime value?

You can read every payment a customer has made from connected Stripe data. weive doesn’t project future value.

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.

Know what brings them back.Without overclaiming why.