Show clients results
they can check.

Each client’s sources and rule live in their own workspace. Share reports that carry the method and the limits, so the result holds up in the room.

Clients don’t want a prettier dashboard. They want to know the result is theirs, measured on their own orders, with the rule written down.

Change the rule.Watch the credit move.

Show a client exactly how one of their orders was credited, then let them try the other rules themselves.

  1. MetaSocial · new collection—
  2. Google AdsSearch · generic—
  3. EmailLifecycle · back in stock—
  4. Direct/checkout—
  5. OrderPaid$260
Northwind order · Stripe$260
Meta——
Google Ads——
Email——
Direct——

Reports that answerthe client’s next question.

Share a report with the number, the rule, and the coverage on it. When the client asks how you got there, the answer is already on the page.

  • Rule and period on every report
  • Coverage on every view
  • Share by link
Northwind · SeptemberShared report
Matched revenueStripe payments$48,000
RuleAgreed with the clientLinear
SourcesGoogle Ads, Meta, Stripe, pixel4 of 4
CoverageEvery source syncedComplete

Platform claims,next to the client’s revenue.

Show what each ad platform reported beside revenue matched to the client’s own payments. The difference gets explained, not hidden.

  • Platform-reported revenue labelled
  • Matched revenue from client payments
  • Rule-based credit as a third view
Google Ads reports$31,000
Meta reports$27,500
Northwind’s orders$48,000
Claims added up$58,500
Orders taken$48,000
Known spend$15,000
September

Prepare for the reviewin one question.

Ask weive what to tell the client. The answer comes with its sources and its limits, ready to stand behind.

  • Answers grounded in the client’s data
  • Rule and sources cited
  • Limits stated plainly
What should I tell Northwind about September?

Matched revenue was $48,000 on $15,000 of known spend, 3.2× under Linear. Google Ads search earned the largest share. Credit shows allocation, not lift.

Northwind workspaceLinear ruleStripe payments

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.

Can I manage several clients from one login?

Not yet. Today each client runs in its own workspace with its own sign-in, so sources never mix. Tell us how your team works and we will help you set it up.

Can clients see the results?

Yes. Share a report by link, with the rule, period, and coverage on it.

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.

Results clients can check.Reports that hold up.