Trial CTA copy test
Compares three wordings of the trial signup button to see which one gets more people to sign up.
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 CTA copy test
Coming soonBlu builds a step
About this recipe
When to use it
'Start Free Trial' vs. 'Get Started' vs. 'Try It Free' all sound reasonable, and picking one by opinion leaves conversion on the table. This runs a random traffic split to measure which one actually converts.
What it delivers
Runs a client-side experiment with a random traffic split, testing which CTA button copy drives more trial signups on a landing page.
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 three wordings of the trial signup button to see which one gets more people to sign up.”
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 CTA copy testCreate a CLIENT EXPERIMENT on /experiences titled "Free Trial CTA Copy Test". This recipe has TWO creation paths: both must be completed: ═══ PATH 1: Top-level configuration (Setup tab) ═══ Experience type: client_experiment (random traffic split, no per-variant targeting) Variants: - Control (33% traffic): existing CTA copy - Variant B (33% traffic): "Try It Free for 14 Days" - Variant C (34% traffic): "Get Started: No Credit Card" Targeting (experience-wide): - Pages: page URL contains "/" (the homepage/landing page): adjust to specific landing page paths as needed - Devices: any (desktop + mobile + tablet) - Audience: all visitors - Display frequency: always Primary metric: goal_completed_in_experience where experience_id = <this experience> (the goal fires when the user completes signup after exposure) Secondary metrics: - Click on where target_id = "hero-cta" (CTA click-through rate) - User created within 7 days of exposed_to_experience (signup conversion) Guardrail: bounce rate (sessions with only one View page) must not increase by >5% vs. control Schedule: 14 days minimum, 95% statistical significance required to ship ═══ PATH 2: Variant HTML content (Visual Editor) ═══ For CLIENT experiments, each variant ships an HTML object that the Visual Editor renders. Open each variant in the Visual Editor (/experience/:id/variants/:variantId/editor) and apply the DOM patches below. Variant: Control HTML (no change: measures the existing CTA): <button class="hero-cta" id="hero-cta" data-variant="control"> [keeps existing CTA copy] </button> Variant: B HTML target selector: #hero-cta Replacement HTML: <button class="hero-cta" id="hero-cta" data-variant="b"> Try It Free for 14 Days </button> Variant: C HTML target selector: #hero-cta Replacement HTML: <button class="hero-cta" id="hero-cta" data-variant="c"> Get Started: No Credit Card </button> The Visual Editor lets the user refine the HTML (typography, color, animation) without leaving the canvas. The exposed_to_experience event fires the moment the variant DOM is applied to the page; goal_completed_in_experience fires when the downstream conversion event matches the configured goal. Taxonomy notes: - exposed_to_experience and goal_completed_in_experience are canonical platform events; they are emitted automatically by the SDK once the experience is live. The recipe does not need to instrument these manually. - Click on.target_id matches the button's id attribute. Ensure the id is preserved across all variants for consistent measurement. - User created is the canonical signup event.
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 /free-trial-cta-copy-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 