Homepage by visitor industry
Visitors you can identify, such as known accounts or logged in users, see a homepage hero and proof points matched to their segment. Unidentified visitors see the generic one.
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 four industry heroes
Coming soonBlu builds a step
About this recipe
When to use it
A healthcare buyer and a fintech buyer don't respond to the same social proof. This shows different homepage hero, social proof, and messaging based on the visitor's detected industry across 4-5 segments, the Demandbase pattern, distinct from per-account ABM.
What it delivers
Personalizes homepage hero, social proof, and messaging by detected visitor industry across 4-5 segments, a vertical-level personalization layer separate from per-account ABM targeting.
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
“Visitors you can identify, such as known accounts or logged in users, see a homepage hero and proof points matched to their segment. Unidentified visitors see the generic one.”
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 four industry heroesCreate a CLIENT PERSONALIZATION on /experiences titled "Industry Vertical Homepage". This is a PERSONALIZATION at the industry-segment level (broader than per-account ABM, narrower than generic). Each variant binds to one industry vertical. Operational sweet spot: 4-5 verticals. ═══ PATH 1: Top-level configuration ═══ Experience type: client_personalization Variants (each binds to an industry audience: adjust to your top 4 verticals): - Control (audience = all: fallback): generic homepage for visitors without industry identification - Variant B (audience = "Technology / SaaS"): Tech/SaaS-specific hero - Audience: account_industry IN ("Technology", "SaaS", "Software") - Variant C (audience = "Financial Services"): Finance-specific hero - Audience: account_industry IN ("Banking", "Financial Services", "Insurance", "Fintech") - Variant D (audience = "Healthcare"): Healthcare-specific hero - Audience: account_industry IN ("Healthcare", "Health Tech", "Pharmaceuticals", "Medical Devices") - Variant E (audience = "Manufacturing / Industrial"): Industrial-specific hero - Audience: account_industry IN ("Manufacturing", "Industrial", "Logistics", "Supply Chain") Targeting: - Pages: homepage "/" and key marketing pages (/solutions, /pricing) - Devices: any - Display frequency: always Metrics: - Form submitted on demo-request form per industry segment - Click on on primary CTA per segment - Demo-request conversion rate per industry (typically the most important downstream metric) Schedule: continuous ═══ PATH 2: Variant HTML content (Visual Editor) ═══ Variant: Control (no DOM changes: fallback) Variant: B (Technology / SaaS) HTML target selector: .homepage-hero Variant DOM: <section class="homepage-hero" data-variant="b" data-vertical="technology"> <h1>The platform that scales with your engineering org</h1> <p>From 10 engineers to 10,000. Used by Snowflake, Databricks, and Datadog.</p> <div class="hero-stats"> <div><strong>500+</strong> SaaS companies</div> <div><strong>99.99%</strong> uptime</div> <div><strong>< 50ms</strong> p99 latency</div> </div> <button class="primary-cta" id="hero-cta-demo">See it in action</button> </section> Variant: C (Financial Services) Same structure with finance-specific copy: <h1>Compliant infrastructure for financial services</h1> <p>SOC2, PCI DSS, ISO 27001. Trusted by leading banks and fintechs.</p> Plus compliance badges and finance customer logos. Variant: D (Healthcare) Same structure with healthcare-specific copy: <h1>HIPAA-compliant data infrastructure for healthcare</h1> <p>BAA-ready. PHI-safe. Trusted by health tech and providers.</p> Plus HIPAA badge and healthcare customer logos. Variant: E (Manufacturing) Same structure with industrial-specific copy: <h1>Real-time operations data for manufacturing</h1> <p>Connect every machine, line, and warehouse. Built for industrial scale.</p> Plus industrial customer logos and IoT-specific imagery. The Visual Editor allows the user to swap logos, adjust copy, and select industry-specific stats per vertical. Avoid over-personalizing (vertical-specific case study links are good; vertical-specific pricing is usually too narrow). Taxonomy notes: - REQUIRES FIRMOGRAPHIC ENRICHMENT: account_industry must be populated via Clearbit, ZoomInfo, IP-reverse lookup, or manual segmentation. Without enrichment, all traffic falls through to Control. - This is a broader, more sustainable personalization than per-account ABM. ABM is high-effort per audience (named heroes); industry-vertical is medium-effort and applies to broader traffic. - Demandbase's research: 4-5 vertical segments is the operational sweet spot. Going beyond 5 makes content maintenance expensive without proportional return. - Don't combine industry-vertical personalization with ABM personalization concurrently on the same page: they'll conflict. Run sequentially or use the experience module's variant-targeting precedence (per-account beats per-industry beats default).
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 /industry-vertical-homepage-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.
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 