Content blocks by browsing behavior
What someone has been reading on your site decides what they see next: two pricing visits brings up the ROI calculator, a security page visit brings up the security case study.
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 behavior variants
Coming soonBlu builds a step
About this recipe
When to use it
Firmographics tell you who a visitor is. Behavior tells you what they're actually thinking about right now. This swaps in content blocks based on recent on-site signals, viewed pricing twice surfaces an ROI calculator, downloaded a security paper surfaces a security case study.
What it delivers
Personalizes content blocks based on recent on-site behavioral signals rather than firmographic data, matching page content to what a visitor is actively evaluating.
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
“What someone has been reading on your site decides what they see next: two pricing visits brings up the ROI calculator, a security page visit brings up the security case study.”
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 behavior variantsCreate a CLIENT PERSONALIZATION on /experiences titled "Intent-Data Content Personalization". This is BEHAVIORAL personalization: each variant binds to an audience defined by recent on-site behavior, not by firmographic attributes. Different from ABM and industry-vertical personalizations. ═══ PATH 1: Top-level configuration ═══ Experience type: client_personalization Variants (each binds to a behavioral audience): - Control (audience = all: fallback): generic content blocks - Variant B (audience = "high pricing intent"): show ROI calculator and pricing-comparison content - Audience: View page where Page URL contains "/pricing": count >= 2 in last 7 days - Variant C (audience = "security/compliance research"): show security case study and compliance content - Audience: View page where Page URL contains "/security" OR "/compliance": count >= 1 in last 14 days OR Click on on a security-whitepaper download link in last 14 days - Variant D (audience = "integrations research"): show integration directory and integrations case studies - Audience: View page where Page URL contains "/integrations": count >= 2 in last 7 days - Variant E (audience = "case study readers"): show more case studies and customer logos - Audience: View page where Page URL contains "/case-studies" OR "/customers": count >= 2 in last 14 days Targeting: - Pages: homepage "/" and key landing pages: anywhere a "Featured content" block renders - Devices: any - Display frequency: always Metrics (behavioral personalization): - Form submitted on demo-request OR contact form per behavioral segment - Click on on the personalized content block (per-variant CTR) - Demo-request conversion rate per segment (the downstream signal that intent-matched content drives conversions) Schedule: continuous ═══ PATH 2: Variant HTML content (Visual Editor) ═══ Variant: Control (no DOM changes: fallback for visitors without strong intent signals) Variant: B (high pricing intent: show ROI calculator) HTML target selector: .featured-content-block (the homepage block where featured content lives) Variant DOM: <section class="featured-content" data-variant="b" data-intent="pricing"> <h2>Calculate your ROI with [Brand]</h2> <p>Based on what you've been reading, here's how teams like yours quantify the impact:</p> <div class="roi-calculator-embed"> <!-- Lightweight embedded calculator: team size + tool spend to estimated savings --> <label>Your team size: <input type="number" id="roi-team-size" value="50" /></label> <label>Current tool spend ($/year): <input type="number" id="roi-current-spend" value="120000" /></label> <div class="roi-result"> Estimated savings: <strong id="roi-savings">$48,000/year</strong> </div> </div> <a href="/pricing" class="content-cta" id="content-cta-pricing">See pricing to </a> </section> Variant: C (security research: show security case study) HTML target selector: .featured-content-block Variant DOM: <section class="featured-content" data-variant="c" data-intent="security"> <h2>How [Customer] passed their SOC2 audit with [Brand]</h2> <p>SOC2 Type II certified. PCI DSS Level 1. ISO 27001. Built for security teams.</p> <div class="case-study-card"> <img src="/case-studies/customer-security.jpg" alt="Customer security case study" /> <h3>Read the case study</h3> <p>How [Customer] reduced compliance overhead by 60%</p> </div> <a href="/security" class="content-cta" id="content-cta-security">Explore security to </a> </section> Variant: D (integrations research: show integration directory) HTML target selector: .featured-content-block Variant DOM: <section class="featured-content" data-variant="d" data-intent="integrations"> <h2>200+ pre-built integrations</h2> <p>Connect [Brand] to your existing stack: Salesforce, Slack, Snowflake, GitHub, and more.</p> <div class="integration-logo-grid"> <img src="/logos/salesforce.svg" alt="Salesforce" /> <img src="/logos/slack.svg" alt="Slack" /> <img src="/logos/snowflake.svg" alt="Snowflake" /> <img src="/logos/github.svg" alt="GitHub" /> <img src="/logos/aws.svg" alt="AWS" /> </div> <a href="/integrations" class="content-cta" id="content-cta-integrations">Browse integrations to </a> </section> Variant: E (case-study readers: show more case studies) HTML target selector: .featured-content-block Variant DOM showing more customer stories. The Visual Editor allows the user to refine copy, embed actual ROI-calculator widgets, and select case studies that match the visitor's likely industry. Taxonomy notes: - This recipe uses canonical event-history-based audiences. The platform's personalization engine evaluates audience rules at render time using the visitor's prior View page and Click on event history. - Audience evaluation: "View page where Page URL contains '/pricing': count >= 2 in last 7 days" requires the platform to query the visitor's event history at render time. Confirm your /experiences personalization engine supports event-history-based audience rules (most modern platforms do; some legacy ones only support attribute-based). - The 7-day and 14-day windows are starting points; tune based on your typical buying cycle. B2B SaaS with longer cycles may use 30-day windows. - This personalization compounds with ABM and industry-vertical: a visitor from a target account in financial services who has viewed /pricing 3 times sees the most personalized experience: but the variants must be ordered by precedence (per-account beats per-industry beats per-intent beats default). - For privacy compliance, ensure your cookie consent banner allows behavioral tracking before evaluating intent-based audiences.
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 /intent-data-content-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.
