Overview · 2:34
See the journey behind your proof.
Follow one signup from earlier proof exposures to a decision your team can inspect.
9 chapters · Captions · Full transcript
Read the transcript
What happened after the proof?
A customer story is part of the journey. But which proof appeared before someone signed up? Proof Impact connects eligible widget impressions with the actions that follow.
Define the outcome that matters
Start with the outcome that matters to your business: a signup, a lead, or a purchase. For Driftlane, choose Customer signup. Give the event a clear name, include it in reporting, and choose its attribution window.
Connect your website
Install a published widget and connect your website’s successful signup to the tracking integration. The setup guide includes framework examples. Send test conversion offers an isolated diagnostic. Creating an event alone does not connect your website.
Follow one example journey
Here is one example journey. A visitor encounters Marina’s story on the agency page, then Lena’s on pricing, and creates an account in the same tab. After processing, the signup has qualifying earlier proof. Proof Impact reports observed attribution, not causal or incremental lift.
Three ways to allocate credit
One signup. Three ways to understand the proof that preceded it. Last-touch credits the latest qualifying exposure. First-touch credits the earliest. Fractional shares credit across both. The allocation changes; the actual signup count stays at one. These are different perspectives on the same journey.
Find the useful detail
Look beyond a total. Explore the customer stories, widgets, and page paths connected to your outcomes. Filter to the page you want to inspect. When you use Contextual Proof Match, rule-level reporting adds another useful perspective.
Understand the evidence
Missing attribution deserves investigation. Was there a qualifying exposure inside the window? Data Quality helps you inspect incomplete evidence. Consent and identity settings also affect what can be connected. A missing match does not prove there was no influence.
Turn evidence into a next step
Export the attribution summary for your team. Use the evidence to review placement or guide collection priorities. For purchases, browser-reported values and signed server evidence remain distinct.
Make the next decision informed
Track. Understand. Act. Start measuring your proof with ReTestimonial. Available on Premium and Business.
Your testimonials are off the books.
Every other line on the marketing report has a number next to it. Social proof — the thing your visitors actually read before they buy — usually has a question mark. So it gets defended with vibes, and cut first.
Proof Impact gives testimonials their own line: which accepted widget impressions were observed before each configured conversion, under that event’s same-tab or consented-identity scope. Attribution credit you can inspect — not a causality claim.
From impression to observed outcome in four entries.
first-party context · configured per eventDefine the outcome before you instrument it.
Conversions aren’t loose strings here. Each outcome is a configured event with a role — Primary, Secondary, or Guardrail — and a value policy, created from 9 starter templates or from scratch. Fire a dry-run test conversion to verify the wiring before anything counts.
3 ways to read the same ledger.
same total · different creditLast-touch
All credit to the proof seen closest to the conversion.
First-touch
All credit to the proof that opened the journey.
Fractional
Credit split evenly across every qualifying touch.
Give proof its own line on the revenue report.
Start free — no cardRefunds un-count themselves.
Attribution numbers only matter if the revenue underneath them is honest. Signed order lifecycle events — HMAC-SHA256 signatures, timestamped requests, monotonic revisions — keep the ledger reconciled when orders change: COMPLETED, PARTIALLY_REFUNDED, REFUNDED, CANCELLED.
Attribution without the creepy parts.
Read the Proof Impact Privacy & Data GuideNumbers you can defend in a data review.
Most attribution tools oversell what observation can prove. We wrote the boundary into the product instead — the same sentence appears on this page, in the dashboard, and in the docs:
Why buy attribution that refuses to overclaim? Because the first hard question in every revenue review is “where did this number come from?” — and this one has an answer.
Attribution starts on Premium.
start free · upgrade when ready| Capability | Free $0 | Pro $29/mo | Premium $49/mo | Business $79/mo |
|---|---|---|---|---|
| Widgets, forms & Wall of Love | ||||
| Observed attribution · 3 models | — | — | ||
| Conversion event catalog + dry-run test | — | — | ||
| Server API keys & signed orders | — | — | ||
| Attribution summary, ledger & JSON exports | — | — | ||
| Experiments (analysis beta) | — | — | — | |
| Auto-Optimize (no live promotion) | — | — | — |
Asked before buying.
Is this causal attribution — does it prove a testimonial drove revenue?
No, and the product says so on every surface: Proof Impact reports observed attribution, not causal or incremental lift. Proof Impact shows which accepted widget impressions were observed before a configured conversion, under each event's lookback window and identity scope. That's evidence you can inspect and defend — not a causality claim. Randomized experiments (an analysis beta on Business) are the path toward lift questions.
How much setup work is it?
Three steps. Publish a widget (the embed you likely already have), create a conversion event — 9 ready-made templates like customer_signup and purchase_completed cover the common outcomes — and add one conversion call where the outcome happens. The dashboard generates copy-paste snippets with your real embed key, and a dry-run test conversion verifies the wiring without storing anything.
Do I need a cookie banner for this?
Proof Impact sets no cookies. It uses same-tab sessionStorage, honors Global Privacy Control and Do Not Track by default, supports an explicit consent mode and an origin allow-list, and stores consented identities only as salted, per-project hashes. The details live in the Proof Impact Privacy & Data Guide at /privacy/proof-impact.
Which plan do I need?
Attribution is included on Premium ($49/mo) and above — all 3 models, the event catalog, server keys, and exports. Business ($79/mo) adds the experiments analysis beta and Auto-Optimize. You can start on Free with widgets and testimonial collection, then upgrade when you want the attribution ledger.
What happens when an order is refunded?
Attributed value follows the money. The signed order lifecycle accepts COMPLETED, PARTIALLY_REFUNDED, REFUNDED, and CANCELLED states with monotonic revisions, and reconciles attributed value when an order changes — a refunded order stops counting. Browser-reported values are always flagged separately from server-authenticated ones.
Does it work with my stack?
If the widget embeds on your site, Proof Impact works there. Conversions arrive three ways: a browser call (window.retestimonial.convert), a server-to-server call authenticated with a rtpi_ API key, or signed order lifecycle calls from your backend. Getting data out is just as open: attribution summary CSV, a raw ledger export, and a full JSON export for your BI tool.
How fast do conversions show up, and how far back does attribution look?
Conversions are accepted immediately and attributed by durable background jobs — typically within minutes, with automatic retries so nothing is silently dropped. Lookback is configured per event: 4 hours–30 days per event, with 4 hours, 1 day, 7 days, 30 days windows to choose from.