Product page layout test
Compares your current product page against a full-width hero with a floating details panel and a video-first layout.
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 layout test
Coming soonBlu builds a step
About this recipe
When to use it
Image placement, information order, and CTA position on a PDP all compete for the same attention, and the right combination isn't obvious without testing. This runs three layouts head to head.
What it delivers
Runs a client-side experiment with three layout variants to find which product detail page layout drives the highest add-to-cart rate.
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 your current product page against a full-width hero with a floating details panel and a video-first layout.”
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 layout testCreate a CLIENT EXPERIMENT on /experiences titled "Product Page Layout". ═══ PATH 1: Top-level configuration ═══ Experience type: client_experiment Variants: - Control (34%): existing PDP: image gallery on left, details on right - Variant B (33%): full-width hero image with floating details panel - Variant C (33%): video-first layout with autoplay product demo Targeting: - Pages: page URL contains "/products/" - Devices: any (note: variant B's floating panel needs explicit mobile design; variant C autoplay should respect prefers-reduced-motion) - Audience: all visitors - Display frequency: always Primary metric: goal_completed_in_experience where experience_id = <this> (goal fires on Cart created within session of exposure) Secondary metrics: - Click on where target_id = "add-to-cart-button" - Placed order within 7 days of exposure - Time on PDP (time from View page to next View page or Session end) Guardrail: bounce rate on PDPs must not increase >5% Schedule: 14 days, 2,000 unique PDP visitors per variant minimum ═══ PATH 2: Variant HTML content (Visual Editor) ═══ Variant: Control (no DOM changes) Variant: B (full-width hero + floating panel) HTML target selector: .product-detail (replace structure) Replacement HTML: <article class="pdp-hero-layout" data-variant="b"> <div class="hero-image-wrapper"> <img src="[primary product image]" alt="[product name]" class="hero-image" /> </div> <aside class="floating-details-panel"> <h1 class="product-title">[Product name]</h1> <div class="product-price">[$X.XX]</div> <div class="product-rating">★★★★☆ (123 reviews)</div> <div class="variant-selectors"><!-- size, color etc --></div> <button class="add-to-cart-btn" id="add-to-cart-button" data-variant="b">Add to Cart</button> </aside> <section class="product-description"><!-- collapsed below the fold --></section> </article> Variant: C (video-first) HTML target selector: .product-detail (replace structure) Replacement HTML: <article class="pdp-video-layout" data-variant="c"> <div class="video-hero"> <video autoplay muted loop playsinline poster="[product poster]"> <source src="[product demo video]" type="video/mp4" /> </video> </div> <div class="product-actions"> <h1>[Product name]</h1> <div class="product-price">[$X.XX]</div> <button class="add-to-cart-btn" id="add-to-cart-button" data-variant="c">Add to Cart</button> </div> <section class="product-info"><!-- description, reviews --></section> </article> Taxonomy notes: - Cart created is the canonical add-to-cart event; it fires with product_id, quantity, Order total. - "add-to-cart-button" target_id must be preserved across variants for click-rate comparability.
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 /product-page-layout-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 