Trust badges near the CTA
Compares no badges, security badges, guarantee badges and all of them together beside your main call to action.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Set up the trust badge test
Coming soonBlu builds a step
About this recipe
When to use it
Trust badges near a CTA are cited for as much as a 102% lift when integrated correctly, which means most integrations aren't correct. This tests placement and badge selection directly.
What it delivers
Tests the placement and selection of trust badges - security, money-back guarantee, payment methods, accreditations - near the primary CTA.
How you prompt this
Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.
Tell Blu Agent what you want
“Compares no badges, security badges, guarantee badges and all of them together beside your main call to action.”
recipe.md preview
Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.
Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.
Outputs
How the recipe runs
Blu follows the steps in order and shows you each one before anything goes live.
- 01Set up the trust badge testCreate a CLIENT EXPERIMENT on /experiences titled "Trust Badges Near CTA". ═══ PATH 1: Top-level configuration ═══ Experience type: client_experiment Variants: - Control (25%): no trust badges near the primary CTA (existing state for many pages) - Variant B (25%): security badges only: SSL, "Secure Checkout", payment encryption icons - Variant C (25%): guarantee badges only: "30-day money-back guarantee", "Free returns", "Cancel anytime" - Variant D (25%): combined: small row showing security + guarantee + payment methods (Visa/MC/AmEx/Apple Pay icons) Targeting: - Pages: high-intent pages: /pricing, /checkout, key product pages, signup pages - Devices: any - Audience: all visitors - Display frequency: always Primary metric: goal_completed_in_experience where experience_id = <this> (goal: Subscription started OR Placed order within 24 hours of exposure) Secondary metrics: - Click on on the primary CTA (target_id matches the page's primary CTA) - Checkout completed within session - Subscription started or Placed order within 24 hours Guardrail: page-bounce rate must not increase >5% (badges shouldn't add visual clutter that drives users off the page) Schedule: 21 days ═══ PATH 2: Variant HTML content (Visual Editor) ═══ Variant: Control (no DOM changes: no trust badges) Variant: B (security badges) HTML target selector: .primary-cta-block (insert after the CTA button) Variant DOM: <div class="trust-badges trust-badges--security" data-variant="b" data-badges="security"> <span class="trust-item"><svg>...</svg> SSL Secure</span> <span class="trust-item"><svg>...</svg> 256-bit encryption</span> <span class="trust-item"><svg>...</svg> PCI compliant</span> </div> Variant: C (guarantee badges) HTML target selector: .primary-cta-block (insert after the CTA button) Variant DOM: <div class="trust-badges trust-badges--guarantee" data-variant="c" data-badges="guarantee"> <span class="trust-item"><svg>...</svg> 30-day money-back</span> <span class="trust-item"><svg>...</svg> Cancel anytime</span> <span class="trust-item"><svg>...</svg> Free returns</span> </div> Variant: D (combined) HTML target selector: .primary-cta-block (insert after the CTA button) Variant DOM: <div class="trust-badges trust-badges--combined" data-variant="d" data-badges="combined"> <div class="trust-row trust-row--security"> <span class="trust-item">🔒 Secure Checkout</span> <span class="trust-item">30-day guarantee</span> </div> <div class="trust-row trust-row--payment"> <img src="/badges/visa.svg" alt="Visa" /> <img src="/badges/mastercard.svg" alt="Mastercard" /> <img src="/badges/amex.svg" alt="AmEx" /> <img src="/badges/apple-pay.svg" alt="Apple Pay" /> </div> </div> The Visual Editor allows the user to swap badges, adjust placement (inline-after-CTA vs. below-button vs. floating-near-CTA), and refine typography. Badges should look authentic: only display certifications the merchant actually has. Taxonomy notes: - Only display trust badges that reflect real certifications, guarantees, or payment methods the merchant actually offers. Fake or aspirational badges erode trust. - For SaaS pages, "guarantee" framing tends to outperform "security" framing; for ecommerce checkout, both matter. - Build Grow Scale's 2026 data: badges placed directly below or beside the Add to Cart button increase purchase confidence by 42%.
Install Intempt and run it
- 1
Sign up
Create a free Intempt workspace.
- 2
Connect your data
Add the sources this recipe reads from.
- 3
Ask Blu
Type /trust-badges-near-cta-test in Blu once this recipe is live there.
- 4
Review and approve
Blu builds each step and waits for your OK before anything goes live.
Related recipes
Sid ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Sid ChaudharyPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Sid ChaudharyReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe 