Overview · 2:34
See the right proof meet the right context.
See how one widget connects campaign context with relevant customer stories.
8 chapters · Captions · Full transcript
Read the transcript
Different reasons to visit
Your campaigns speak to different needs. Your proof can, too. One visitor wants smoother agency handovers. Another wants a straightforward start. The same pricing page can support both conversations.
Start with proof you trust
Start with approved customer stories from forms, imports, or Smart Invites. In the widget builder, choose Proof Match. Your base pool defines the available proof. Stored Proof Intelligence labels help you select relevant use cases.
Connect context to relevant stories
For Driftlane, one rule connects the pricing page and agency campaign with project handover stories. Campaign parameters are labels on your links. A second rule connects the getting started campaign with a different set of stories. Choose the context. Choose the proof that fits. You control the rule order.
Preview the match and understand why
Open the Context Simulator. Enter the page and campaign. From six approved stories, this rule selects three, including Marina’s handover experience. Change only the campaign, and the selected proof changes. Now Lena’s getting started story belongs in the preview. You can inspect the match before publishing.
One placement, relevant proof
Preview your widget and publish the reviewed configuration. The page and widget stay consistent. Each visit receives proof selected for its available, permitted context. It connects the campaign’s message with a customer experience that speaks to the same need.
Keep a useful fallback
What if no campaign rule matches? The base pool remains available. In a separate example, the contextual selection is too small. Use base pool provides a deliberate fallback. It keeps useful proof available without inventing a missing customer story.
Connect the rest of the workflow
Need another perspective? Proof Gap Autopilot can guide a focused collection request. With Proof Impact configured, inspect rule-level exposures and attributed conversions. These are observations, not guaranteed gains. Business Auto-Optimize adds observational recommendations; publishing and decisions remain under your control.
Make the next story relevant
For SaaS campaigns, agency pages, and product pages: context, rules, relevant proof. Build your first Proof Match widget with ReTestimonial. Available on Premium and Business.
One wall of love for everyone is a wall for nobody.
An agency on LinkedIn, a developer from Hacker News, and a price-shopping founder from Product Hunt all land on /pricing — and you show all three the same five testimonials. The agency wants to see other agencies. The developer wants the API quote. The founder wants to know it pays back.
Contextual Match uses bounded request context to choose a proof filter — without maintaining a separate widget for every campaign or page.
Read. Match. Serve.
Matching is resolved server-side before the widget renders. The browser still makes the normal widget-data request.
Read
The loader sends bounded page path, referrer domain, UTM source, medium, campaign and content, plus optional page tags with the widget-data request.
Match
Enabled rules are evaluated by priority. The first matching rule applies its configured proof filters to the eligible testimonial pool.
AND path = "/pricing"
THEN match tag AGENCY
Serve
The server returns the selected proof and match metadata. The async runtime then renders the response inside the widget's Shadow DOM.
Four context groups. No identity profile required.
Rules use the request context implemented by the public widget API. Language can also guide translation, but is not a match condition.
Context chooses the rule. Filters choose the proof.
Each contextual rule reuses the widget's implemented auto-sync filters, including tags and optional Proof Intelligence fields.
Priority rules. Explicit fallback.
Enabled rules run in priority order. If the contextual pool is too small, choose the base auto-sync pool or keep the contextual result without overriding it.
One <script> tag. Four shipped variants.
All four visitors hit the same URL with the same widget. The widget renders the proof their context calls for.
Not a feature flag. The delivery layer.
Contextual Match combines widget selection filters, Proof Intelligence enrichment, and Proof Impact evidence without claiming unsupported integrations.