AXO for content & media.

Post-click + inbound personalization

Every visitor lands on a page tuned to how they arrived and what they're doing in the first few seconds.

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.

• Anonymous behavioral signals · Data collection
  Click depth, scroll velocity + depth, dwell, hover, pause, tab-switch, cadence — collected without requiring identity.
• Cookieless session reconstruction · Data collection
  Stitches a visitor's session across pages without third-party cookies.
• UTM + referrer + device context · Data collection
  Every event carries the channel, referrer, viewport, and device class for downstream targeting.
• 9 variant types · Site personalization
  copy_swap, hero_swap, overlay, lightbox, banner, badge, product_reco, lead_form, move_object, plus donation_form for fundraising.
• Article + content recommendations · Recommendations
  Same recommender works for articles + categories, not just products.

Behavioral audience discovery

Anonymous clickstream surfaces real shopper cohorts without a CDP team or an audience-builder UI.

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.

• Per-vertical default segment packs · Audience segmentation
  6+ segments seeded per industry — Deliberator / Comparison Shopper / Gifter for retail; Donor Ready / Lapsed for fundraising; etc.
• No-code custom segment builder · Audience segmentation
  Composable predicates: event_occurred, page_viewed, utm_matched, propensity, feature_anomaly, lifecycle, affinity.
• Hidden-persona ML clustering · Audience segmentation
  Surfaces audience cohorts the operator didn't pre-define, with stability + lift validation.

Catalog-aware recommendations

Every recommendation slate comes from your live catalog, in stock and on brand, tuned per segment.

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.

• Article + content recommendations · Recommendations
  Same recommender works for articles + categories, not just products.
• 3 reco strategies · Recommendations
  Curated (operator-pinned), rec_engine (cooccurrence + embeddings), mixed (pin some, fill the rest).
• 4 ranking modes · Recommendations
  session_behavior, bestsellers, new_arrivals, similar — chosen per zone + per segment.
• Catalog auto-import · Recommendations
  Shopify native; custom feed via importer. Reclassification + brand-guideline extraction at ingest.

Journey + message orchestration

Cart-abandonment, browse-abandonment, win-back, lifecycle messages — fire through the ESP / SMS / ad-platform you already use.

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.

• Trigger engine · Journey + message orchestration
  Composable eligibility (segment + UTM + behavior, all_of / any_of) → render an action or fire to a destination.
• Email/SMS destinations · Email + SMS destinations
  Klaviyo, Braze, Customer.io, Resend, SendGrid, Postmark, Mailchimp, Twilio (SMS), Intercom, SFMC, Emarsys.
• Composable eligibility predicates · Journey + message orchestration
  segment_member + utm_matched + event_occurred + visitor_lifecycle + propensity, AND/OR composable.
• Multi-channel dispatch · Journey + message orchestration
  One trigger can fire to email + SMS + ad-CAPI + webhook simultaneously, each with its own template.

Ad-platform retargeting + CAPI measurement

Server-side conversion events for iOS-14-safe attribution. Build retargeting lists from behavior. Suppress converters from spend.

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.

• Ad-platform server-side CAPI · Ad platforms
  Meta, Google Ads, GA4 MP, TikTok, Pinterest, Reddit, LinkedIn — server-side conversion API for iOS-14-safe attribution.
• Behavior → ad-platform audience export · Ad platforms
  Push behaviorally-built segments to Meta Custom Audiences, Google Customer Match, LinkedIn audiences.
• Trigger engine · Journey + message orchestration
  Composable eligibility (segment + UTM + behavior, all_of / any_of) → render an action or fire to a destination.

Holdout-proven incremental lift

A 10% control group runs against every change, always on. Causal attribution, not correlation.

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.

• 10% always-on holdout · Measurement
  Live control group on every change. Real incremental lift, not asserted lift.
• Lift attribution per variant + per segment · Measurement
  Causal attribution scoped to the specific variant + the specific cohort it served — not site-wide proxies.
• AI Scorecard · Measurement
  Plain-language "is the AI working?" verdict for a non-technical reader. Holdout vs. personalized side-by-side.
• Scheduled analytics email digests · Measurement
  Daily / weekly per-site rollups, sent to opted-in recipients. List-unsubscribe-aware.

Agentic creative + ops

Drive AXO from natural language — in-app via the AXO Assistant or externally via Claude / Cursor / ChatGPT / VS Code through MCP.

"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.

• AXO Assistant (in-app) · AI + agentic
  Chat-based agent that drives AXO from natural language. Reads your data, takes actions, asks for confirmation on writes.
• MCP server · AI + agentic
  Connect Claude, Cursor, ChatGPT, VS Code, or any MCP-compatible tool. Same toolset as the in-app assistant.
• AI-drafted variant copy · AI + agentic
  Brand-voice guardrails + active-campaign context baked in. Drafts go through human review before publishing.
• Scheduled analytics email digests · Measurement
  Daily / weekly per-site rollups, sent to opted-in recipients. List-unsubscribe-aware.

First-party data activation

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.

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.

• CDP destinations · Data infrastructure
  Segment, RudderStack, mParticle, Adobe AEP — works alongside existing CDPs without replacing them.
• Warehouse destinations · Data infrastructure
  Snowflake, BigQuery, Amazon S3 — stream profile + event copies to your data plane.
• Signed custom webhook · Data infrastructure
  Generic HMAC-signed POST to any URL you own — escape hatch for anything not in the catalog.