Coming soon
Email and SMS campaign results
Ranks every email and SMS send by the revenue it produced, so you can see which subject lines, offers and content earn their place.
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
Build the campaign leaderboard
Coming soonBlu builds a step
About this recipe
When to use it
Sends, opens, clicks, conversions, and revenue per send is the standard lifecycle-marketing view, and most teams only get it inside one specific ESP. This builds the same leaderboard natively.
What it delivers
Builds a campaign-level leaderboard with sends, opens, clicks, conversions, and revenue per send, for the lifecycle marketer view.
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
“Ranks every email and SMS send by the revenue it produced, so you can see which subject lines, offers and content earn their place.”
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.
StepWhat happensBuilds
- 01Build the campaign leaderboardCreate a Dash board (12-column composition canvas) titled "Email/SMS Campaign Performance". Persona: Lifecycle Marketer, Email Manager, or CRM Lead running campaigns through Klaviyo, Customer.io, or similar. Question answered: "Which campaigns are working? Which subject lines, content, and offers drive revenue?" Distinct from Marketing Attribution Dashboard (channel-level revenue, mostly paid acquisition) and Ecommerce Lifecycle Dashboard (lifecycle stage migration). Campaign Performance is operational per-send: the dashboard an email marketer opens after every campaign deploy. Board-level configuration: - defaultDateRange: last_30_days - exclusionPeriod: today (most campaign attribution windows extend 7 days; today's data is incomplete) - visibility: project - boardFilters: none by default; marketers can filter to specific campaign_id patterns (e.g., flow vs. broadcast) at runtime - boardBreakdowns: campaign_id Layout: 4 rows. Row 1: Campaign performance KPIs (heightPx: 200, four metric cards at widthUnits: 3): - Card 1: Insights metric to source recipe: campaign-performance-leaderboard, vizType: metric, titleOverride: "Total Sends (30d)" - Card 2: Insights metric to source recipe: campaign-performance-leaderboard, vizType: metric, titleOverride: "Average Open Rate" - Card 3: Insights metric to source recipe: campaign-performance-leaderboard, vizType: metric, titleOverride: "Total Email Revenue (30d)" - Card 4: Insights metric to source recipe: campaign-performance-leaderboard, vizType: metric, titleOverride: "Average Revenue per Send" Row 2: The leaderboard (heightPx: 520, full-width single card at widthUnits: 12): - Card 1: Insights to source recipe: campaign-performance-leaderboard, displayMode: table (sortable top 30 campaigns by Revenue / Revenue per Send / Open Rate / Click Rate / CTOR / Conversion Rate). The strategic centerpiece: every email marketer's morning view. Row 3: Performance scatter and funnel (heightPx: 440, two cards at widthUnits: 6): - Card 1: Insights to source recipe: campaign-performance-leaderboard, displayMode: chart, vizType: scatter (X-axis: Click Rate, Y-axis: Conversion Rate, bubble size: Revenue per Send: the four-quadrant performance matrix) - Card 2: Funnel to source recipe: email-purchase, displayMode: chart, vizType: funnel_steps (the canonical email-to-purchase journey, with per-campaign breakdown showing where in the funnel campaigns leak) Row 4: Channel context (heightPx: 400, two cards at widthUnits: 6): - Card 1: Insights to source recipe: revenue-by-channel, displayMode: chart, vizType: bar (filter: UTM source = email; shows email's contribution to total channel revenue) - Card 2: Insights to source recipe: customer-lifecycle-distribution, displayMode: chart (lifecycle stage distribution of email-engaged users: answers "are emails reaching Champions or At Risk?") Annotations: - Row 2 (the leaderboard, full-width) is the centerpiece. Default sort is Revenue per Send (RPS): the metric that ties every campaign directly to dollar contribution. Industry benchmarks: $0.10-$0.50 RPS for typical DTC; >$1.00 RPS is best-in-class. - Row 3 Card 1 (scatter quadrant) tells you what to copy and what to fix: - Top-right quadrant (high CTR + high CR) = your best campaigns; replicate their subject lines, content, and offer structure - Top-left (high CTR + low CR) = great email but landing-page mismatch; fix the post-click experience - Bottom-right (low CTR + high CR) = great offer but email content underperformed; A/B test creative - Bottom-left (low CTR + low CR) = the campaign didn't connect; either retire the audience segment or rethink the offer - Row 3 Card 2 (email-purchase funnel) surfaces where in the email-to-purchase journey campaigns leak: open to click drop = subject line/preheader; click to product page = landing page; product page to purchase = price/offer. - Row 4 provides context: how big is email as a % of total revenue (Card 1)? And are emails reaching the right lifecycle segments (Card 2)? Emails reaching mostly At Risk customers signal great win-back work; emails reaching mostly New customers signal acquisition-funnel email. Taxonomy notes: - campaign-performance-leaderboard depends on Email sent.campaign_id being reliably populated by the workspace's email integration (Klaviyo, Customer.io, Mailchimp). If campaign_id is sparse, the report degrades to aggregate email performance without per-campaign breakdown. - Attribution from Email clicked to Placed order uses a 7-day window joined via masterID/email matching the Email sent.campaign_id. - For SMS-side analysis, substitute messaged_sms (which has template_id and journey_id): the recipe handles both channels. - All other source recipes use canonical events: Email sent, Email opened, Email clicked, Placed order, View page.
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 /email-sms-campaign-performance-dashboard 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
Intempt TechnologiesDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Intempt TechnologiesPost 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 Intempt TechnologiesReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe
More recipes by Intempt Technologies
Discovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Post 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 Product swap in a sceneReplaces the product in a shot you already have with a different one, keeping the scene, lighting and shadow the same.View recipe
