Demo or self-serve CTA by company size
Use the personalization engine to show different CTAs to visitor audiences you define. It does not use firmographic company-size data.
Authored by Intempt Technologies
Recipe curators
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 two CTA paths
Coming soonBlu builds a step
About this recipe
When to use it
The same CTA doesn't convert an enterprise buyer and a solo user equally well. This shows enterprise-firmographic visitors a demo CTA and smaller-company visitors a self-serve CTA, targeted by firmographics, not a random split.
What it delivers
Personalizes the primary CTA by firmographic audience targeting, showing a demo CTA to enterprise-fit visitors and a self-serve CTA to smaller-company visitors.
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
“Use the personalization engine to show different CTAs to visitor audiences you define. It does not use firmographic company-size data.”
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 two CTA pathsCreate a CLIENT PERSONALIZATION on /experiences titled "Demo vs Self-Serve Routing". This is a PERSONALIZATION (not an experiment): different audiences see different content based on targeting rules. There is no random traffic split; instead each variant binds to a specific audience segment. There are no primary/secondary metrics: personalizations measure on existing CRM/CDP metrics rather than hypothesis-bound experiment metrics. ═══ PATH 1: Top-level configuration ═══ Experience type: client_personalization Variants (each variant binds to a specific audience): - Control: standard self-serve CTA, audience = "all" (default; falls through if no other variant matches) - Variant B: enterprise demo CTA, audience = "enterprise visitors" - Audience definition: company size > 200 employees OR domain matches enterprise patterns (firmographic enrichment via the Accounts object) - Variant C: SMB self-serve CTA with social proof, audience = "SMB returning visitors" - Audience definition: company size 1-50 employees AND has at least one prior Session start Targeting (experience-wide): - Pages: page URL is the homepage "/" or marketing landing pages - Devices: any (firmographic data is identity-based, not device-based) - Audience: specific (each variant has its own audience binding) - Display frequency: always Metrics (existing CRM/CDP metrics: not hypothesis-bound): - Form submitted on demo-request form (per audience) - User created (self-serve signup) (per audience) - Deal created (downstream attribution to demo route) Schedule: continuous: personalizations are not time-boxed like experiments. Edit the variants when needed; no statistical horizon. ═══ PATH 2: Variant HTML content (Visual Editor) ═══ Variant: Control (audience = all: fallback) HTML target selector: .hero-cta-block (default contents: keep existing) Existing self-serve CTA stays as the catch-all. Variant: B (audience = enterprise visitors) HTML target selector: .hero-cta-block (replace contents) Variant DOM: <div class="hero-cta-block" data-variant="enterprise" data-audience="enterprise"> <h2>Enterprise teams move faster with [Product]</h2> <p>See how [Brand] adapts to your org's complexity in a 30-min demo.</p> <button class="primary-cta" id="demo-cta">Book a Demo</button> <p class="secondary-link"><a href="/contact-sales">Talk to sales to </a></p> </div> Variant: C (audience = SMB returning visitors) HTML target selector: .hero-cta-block (replace contents) Variant DOM: <div class="hero-cta-block" data-variant="smb-returning" data-audience="smb-returning"> <h2>Welcome back: ready to get started?</h2> <p>Free for teams up to 5. No credit card required.</p> <button class="primary-cta" id="signup-cta">Start Free Trial</button> <div class="social-proof"> <p>Trusted by 12,000+ teams like yours</p> </div> </div> The Visual Editor opens for each variant individually so the user can refine copy, social proof selection, and CTA design per audience. Taxonomy notes: - Personalizations differ from experiments in that variants don't compete; each one delivers to its own audience segment. The Setup tab hides Primary/Secondary Metrics and replaces the traffic-percentage stepper with an audience picker per variant. - Firmographic enrichment (company size, domain matching) typically requires an integration like Clearbit or ZoomInfo; the Accounts object is the canonical place to store this data. - "Returning visitor" detection uses Users.First seen being older than the current session.
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 /demo-vs-self-serve-routing-personalization 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.
