Eight use cases across the platform. Pick your industry to see how each one shows up for your storefront, publisher, patient funnel, or donor site — plus the specific AXO features that power it.
Every visitor lands on a page tuned to how they arrived and what they're doing in the first few seconds.
A Comparison Shopper arriving from Google CPC sees a price-anchored hero with reviews above the fold; a Surfer from social sees lifestyle imagery and a low-friction "browse the collection" CTA — same page, different shopper.
Why it matters: The brand spent money to get them here. Default "same homepage for everyone" wastes that spend.
A pricing-page visitor from a sales email sees an enterprise comparison + customer logos in their tier; a docs-page visitor from organic sees "talk to an engineer" instead of "talk to sales."
Why it matters: Buying committees touch your site differently than evaluators. Same page should react.
A first-time reader from social sees an article-trail "if you liked this, try this"; a returning subscriber sees Continue Reading where they left off.
Why it matters: Conversion = engagement + repeat visits. Tailoring the first 5 seconds drives both.
A patient inquiry from paid search sees insurance-friendly proof + an appointment CTA; a returning patient sees their service line and a portal link.
Why it matters: Inquiry-to-appointment is the conversion that matters. Reduce friction without storing PHI.
A Major-Gift Researcher sees the impact-stats hero + annual-report CTA; a first-time mobile-impulse donor sees match-doubled framing and a $25 anchor.
Why it matters: Donor cohorts respond to different framing. A single homepage leaves money on the table.
Anonymous clickstream surfaces real shopper cohorts without a CDP team or an audience-builder UI.
Day one of collection: the dashboard surfaces Deliberators, Surfers, Converters, Comparison Shoppers, Gifters, and Engaged Paid Arrivals — named with sample sessions you can click into.
Why it matters: Most retail brands either lack a CDP or have one their marketing team can't operate. AXO replaces "audience building" as a job.
AXO surfaces Pricing Dwellers, Docs Divers, Champion Researchers — addressable in the variant editor next to whatever segments your CDP already maintains.
Why it matters: B2B audiences are small and high-value. Misclassifying a champion as a tire-kicker is expensive.
Engaged Readers, Skim-and-Bounce, Returning Subscribers, Paywall-Hit Browsers — each addressable for its own subscription nudge.
Why it matters: Subscription conversion turns on knowing who's 80% there vs. who's never coming back.
Symptom Researcher, Insurance Checker, Returning Patient — surfaced from behavior alone, without form values ever reaching AXO.
Why it matters: PHI-safe by construction: the segment exists from session shape, not from form contents.
11 donor-lifecycle segments: Donor Ready, Researcher, Supporter, Lapsed (×2), High Capacity Uncontacted, Recurring Card Declined, Year-End Returning, Advocacy Engaged Non-Donor, plus Volunteer Candidate.
Why it matters: Donor-CRM-led tools key off who already gave. AXO segments off who's about to give — the higher-leverage signal.
Every recommendation slate comes from your live catalog, in stock and on brand, tuned per segment.
PDP "you may also like" surfaces 4 items: 2 cooccurrence-driven from your catalog, 1 bestseller from the same category, 1 new-arrival — all in stock, all in the brand voice you uploaded.
Why it matters: Recommendations are the moment of truth in any ecom session. Generic carousels miss; segment-aware in-stock recs convert.
End-of-article "continue reading" trails serve different recs per reader cohort — Engaged Readers see depth, Skim-and-Bounce sees punchy headlines.
Why it matters: The next-article click is what builds session depth and subscription conversion.
Cart-abandonment, browse-abandonment, win-back, lifecycle messages — fire through the ESP / SMS / ad-platform you already use.
Cart abandoned → 1-hour-delay Klaviyo email scoped to Comparison Shoppers (with a value prop) vs. Deliberators (with social proof); if no purchase in 24h, fire a Meta retargeting audience push via CAPI.
Why it matters: Abandonment recovery is the highest-ROI lifecycle motion in retail. AXO routes the logic through your existing Klaviyo, not a competing platform.
Demo form started but not finished → 24h Customer.io email tuned to whether they hit the enterprise tier; pricing-page visit + no demo in 7d → LinkedIn audience for paid retargeting.
Why it matters: Long sales cycles need many nudges. Eligibility-gated triggers prevent the spam-cannon failure mode.
Paywall-hit + bounced → 48h Mailchimp "your free articles are waiting" email; subscriber inactive 30 days → win-back via SendGrid scoped to their last-read topic.
Why it matters: Subscription churn is invisible until it's expensive. Lifecycle triggers catch it before the renewal date.
Appointment-request form started but not submitted → 4-hour-delay Postmark email pointing back to the form, with insurance-FAQ snippet — never carries PHI in the payload.
Why it matters: Patient acquisition is high-stakes and tightly regulated. Triggers that respect PHI by default are not optional.
Recurring card declined → save-flow email from the donor's last designation; lapsed monthly donor visits the site → reactivation email with their previous gift amount pre-anchored.
Why it matters: Recurring donor retention is the wedge vs. CRM-led tools that fire only at scheduled cadences.
Server-side conversion events for iOS-14-safe attribution. Build retargeting lists from behavior. Suppress converters from spend.
Purchase event fires server-side to Meta + Google + TikTok via CAPI — survives iOS 14.5+ tracking limits. Cart abandoners flow into a Meta Custom Audience automatically. Converters get suppressed from acquisition campaigns within minutes.
Why it matters: iOS attribution loss has hammered ecom ROAS. Server-side CAPI + behavior-built audiences restore measurement and cut wasted impressions.
Pricing-page dwellers + docs-page returners flow into a LinkedIn audience for ABM retargeting; demo-requesters get suppressed from acquisition spend; demo-completers flow to Google for lookalike modeling.
Why it matters: B2B CACs are high. Spending an extra impression on someone already in your pipeline is wasted budget.
Suppress subscribers from acquisition campaigns; build retargeting audiences from paywall-hit + non-bouncer sessions; feed Google Ads with subscription events server-side for smart bidding.
Why it matters: Subscriber acquisition cost is the budget killer; suppression alone can pay for AXO.
Patient-inquiry conversion fires to TikTok + Meta via CAPI — server-side, no on-page pixel that could capture form values. Audiences built from behavior, not from any data that would trigger HIPAA scope.
Why it matters: Health advertisers have spent a year being de-platformed for on-page pixel exposure. Server-side CAPI is the safer path.
Donation_completed fires server-side to Meta for fundraising-event ROI tracking; advocacy-action takers flow into retargeting audiences for the next ask. ActBlue + WinRed donations feed back via webhook for closed-loop attribution.
Why it matters: Most donor-marketing tools don't do CAPI. The ones that do don't do behavioral audience building. AXO does both.
A 10% control group runs against every change, always on. Causal attribution, not correlation.
Every variant ships to 90% of matching shoppers; 10% stay in control. The Scorecard reads "Comparison Shopper hero variant: +4.2% conversion lift over holdout, p<0.05, +$18.3k incremental revenue last 30 days."
Why it matters: Every personalization vendor claims uplift. Only the ones holding out a control group can prove it. Critical for CMOs reporting to a board.
Pricing-page variant tested against an always-on holdout reads "+11.4% demo-request rate from Champion Researchers, n=2,847, 87% confidence."
Why it matters: B2B sample sizes are small. A real control group beats a year-later attribution argument.
Subscription-wall variant attributed to holdout-incremental conversion rate, not site-wide rate that drifts with traffic mix.
Why it matters: Publisher revenue is too low-margin to spend on changes you can't prove caused lift.
Appointment-request CTA variant tested against holdout reads "+8.1% submission rate on the Insurance Checker cohort, p<0.05." Reports your compliance team can review.
Why it matters: Health marketing is regulated. Provable attribution + auditable history is table stakes.
Recurring upgrade ask tested against holdout reads "+3.2% conversion to recurring among Year-End Returning donors, +$4.7k attributable monthly recurring revenue." Numbers the board can read.
Why it matters: Donor relationships are sacred. You don't guess; you prove.
Drive AXO from natural language — in-app via the AXO Assistant or externally via Claude / Cursor / ChatGPT / VS Code through MCP.
"Draft three Comparison Shopper hero variants for Pawnest's PDP — price-anchored, reviews-led, and shipping-led." Agent reads your brand voice + active campaign brief, generates with provenance, queues for human review.
Why it matters: Marketing teams don't have engineers. The agentic surface is what gets non-technical operators from "could do this" to "did this today."
"Audit our pricing-page variants for compliance copy — flag anything that mentions guaranteed outcomes." Claude pulls the variants via MCP, runs the audit, posts findings back into the AXO dashboard.
Why it matters: B2B copy review is high-stakes (legal/compliance). The audit trail is non-optional.
"Show me which subscriber cohorts are at risk of churn this week + draft a re-engagement variant for each." Agent pulls Pulse data + Scorecard, drafts, requests approval.
Why it matters: Editorial teams ship daily; the agentic loop matches that cadence in a way manual variant authoring doesn't.
"Configure the appointment-request form variant for our Spanish-language patients — PHI-safe field set, insurance check before submit." Agent runs the configuration, surfaces it for clinical-marketing approval.
Why it matters: Health marketing needs both speed AND audit trail. Agentic ops with provenance gives both.
"Help me set up donor segments and a recurring-decline save flow for our new monthly giving campaign." Agent provisions the segments, drafts the email sequence, wires the trigger, surfaces ladders.
Why it matters: Nonprofit ops teams are small; agentic workflows turn what would be a multi-day project into a one-conversation setup.
Profile + event data flows to the CDP, warehouse and CRM you already run — Segment, Snowflake, BigQuery, Salesforce, HubSpot. AXO feeds your stack, doesn't replace it.
Behavioral cohort assignments stream to Segment + Snowflake for downstream BI; purchase events sync to Klaviyo + Salesforce CRM in real time; cart-value distributions land in BigQuery for finance.
Why it matters: Brands invested in a data stack don't want a new island. AXO sits on top, feeds the stack, doesn't compete with it.
Pulse-resolved profile updates push to Salesforce + HubSpot; behavioral score deltas stream to mParticle; account-level events land in Snowflake for revenue ops.
Why it matters: Account-based motions require the same profile to be coherent across CRM + CDP + warehouse + AXO.
Subscription events flow to Stripe via webhook; cohort assignments stream to Segment; reading-affinity profiles land in BigQuery for the editorial team.
Why it matters: Publisher data tools are fragmented; AXO's job is to be the connecting tissue, not yet-another-silo.
PHI-safe profile + event data streams to your warehouse for downstream reporting; CRM updates push to Salesforce Health Cloud; no protected fields ever cross the AXO boundary.
Why it matters: Health data infra is regulated. Flowing AXO's aggregate signal in without bringing PHI back out is the right posture.
Donor profile updates flow to NPSP / VAN / Bonterra; advocacy actions land in your CRM; lifetime giving aggregates land in BigQuery for development-team forecasting.
Why it matters: Donor-CRMs are the system of record. AXO's behavioral signal makes them smarter without forcing a migration.
The 5 verticals above are where we\'ve invested the deepest product surface. AXO runs on any site with a script tag — talk to us about yours.
Talk to us →