This hub is for the Blend360 campaign team. Enter the team passphrase to continue.
The campaign microsite is fully instrumented with first-party analytics (PostHog). This page is the marketing team's map to what's being tracked, what the KPIs mean, and where to watch them live.
The campaign's PostHog data, rendered in Blend's own visual language \u2014 toggle the controls on each chart, hover anything for detail. Full drill-down filtering lives in the PostHog dashboard one click below.
Is the campaign pulling people in? Watch this jump on send days.
Of everyone who starts the simulator, how many finish — and convert.
Which sections earn attention — lead the next send with the winner.
Which guest story resonates most.
The "Hi, …" chip experiment: which page version visitors choose.
The three rates that decide campaign ROI.
The newest events streaming off the site, most recent first.
Every white-paper request becomes a lead record: a lead_captured event (email, readiness tier & score, persona view, theme) with the visitor identified in PostHog — and, once Mel/Marcela provide the portal + form IDs, the same submit also creates the contact in HubSpot automatically (Forms API scaffold is live in the site code).
| When | Lead | Readiness | Persona view | Route |
|---|
The "T&H Microsite — Campaign Analytics" dashboard is built around the questions marketing will actually be asked — reach and conversion up top, then depth: journey drop-off, readiness-tier mix, average readiness score, case-study engagement, and lead quality by tier.
How many people the campaign is pulling in, total and per day, across LinkedIn, email, and dark-social shares.
When traffic spikes — so sends and posts can be tied to the response they produced.
Which of the seven sections people actually open. If "The Proof" outperforms "Three Claims," lead with proof in the next send.
Of everyone who starts the interactive guest journey, how many finish it — and how many go on to request the white paper.
Maya (loyalist), Devon (AI-native), or the Riveras (lapsed family): which story resonates tells us which audience is leaning in.
The number that matters: gated-content submissions and clicks toward a working session.
Exactly where visitors stop inside the five-step simulator — the step that loses people is the step to sharpen.
The tier mix and mean score say who the campaign is actually reaching — front-of-the-line brands or window-closing ones.
Which Proof-in-the-wild stories get opened — direct input for the next send and the sales deck.
Not just how many leads — which maturity segment converts. Route front-of-the-line leads straight to Paul.
All events fire client-side into PostHog. The only personal data collected is what a visitor submits in the white-paper form: the submitted email becomes a lead record (lead_captured + identified person) so sales can follow up; all other events carry no personal data.
| Event | Fires when | Properties |
|---|---|---|
microsite_tab_viewed | A visitor opens any of the seven sections | tab |
persona_selected | A guest persona is chosen in the journey simulator | persona, persona_name |
journey_step_viewed | Each of the five journey steps renders | persona, step, step_index |
journey_completed | The final journey step's "Finish" is clicked | persona |
readiness_quiz_started | First answer selected in the readiness check | — |
readiness_quiz_completed | Score revealed | score, tier |
roi_calculated | A visitor adjusts the ROI calculator | members, share |
whitepaper_submitted | White paper form submitted | domain, quiz_tier, quiz_score |
cta_clicked | Any call-to-action button is clicked | cta, to |
lead_captured | White-paper form submitted — the lead record for the pipeline (person identified in PostHog; HubSpot sync when form IDs land) | email, domain, quiz_tier, quiz_score, persona_view, theme |
persona_view_switched | The "Hi, …" chip re-decides the page for a persona (Maya / Devon / the Riveras / neutral) | persona |
case_study_clicked | A "Proof in the wild" case study is opened | case_study_id, title |