Targeting recipes

A field guide to the segments that pay off most. Each recipe is copy-pasteable into the segment builder.

Power users

Heavy weekly usage, on a paid plan. Best audience for advocacy surveys and beta invites.

{
  "all": [
    { "property": "user.plan", "op": "in", "value": ["pro", "enterprise"] },
    { "event": "session_started", "count": { "gte": 5, "window": "7d" } }
  ]
}

Trial day 3

Users 72 hours into their trial — past initial setup, before the activation deadline. Best for an in-app nudge or a personal email.

{
  "all": [
    { "event": "trial_started", "count": { "gte": 1, "window": "all" } },
    { "event": "trial_started", "days_since": { "eq": 3 } }
  ]
}

Churn risk

Paying users who've gone quiet for two weeks. The right audience for a "did we miss anything?" survey.

{
  "all": [
    { "property": "user.plan", "op": "in", "value": ["pro", "enterprise"] },
    { "event": "session_started", "count": { "lte": 1, "window": "14d" } },
    { "event": "subscription_canceled", "count": { "eq": 0, "window": "all" } }
  ]
}

Post-purchase

Just completed a checkout. The honeymoon period — best for CSAT.

{
  "all": [
    { "event": "checkout_completed", "days_since": { "lte": 1 } }
  ]
}

High-error session

User has hit 3+ errors in the last hour. Exclude this segment from surveys; consider it for a hand-raise prompt to support.

{
  "all": [
    { "event": "error_seen", "count": { "gte": 3, "window": "1h" } }
  ]
}

New install

First-week users, before their habits form. Right for onboarding surveys.

{
  "all": [
    { "event": "app_installed", "days_since": { "lte": 7 } }
  ]
}

Re-engaged

Returned after a week of silence. Right for a "welcome back" in-app message — or a feature-discovery survey.

{
  "all": [
    { "event": "session_started", "count": { "eq": 1, "window": "1d" } },
    { "event": "session_started", "count": { "eq": 0, "window": "8d" } }
  ]
}

Pro feature curious

On a trial plan, but clicked a Pro-only feature in the last 3 days. Right for a paywall in-app message.

{
  "all": [
    { "property": "user.plan", "op": "eq", "value": "trial" },
    { "event": "pro_feature_clicked", "count": { "gte": 1, "window": "3d" } }
  ]
}

Combining recipes

Recipes compose. Power users in the EU who haven't given us NPS yet:

{
  "all": [
    { "property": "user.plan", "op": "in", "value": ["pro", "enterprise"] },
    { "event": "session_started", "count": { "gte": 5, "window": "7d" } },
    { "property": "user.region", "op": "eq", "value": "EU" },
    { "event": "nps_responded", "count": { "eq": 0, "window": "180d" } }
  ]
}

What's next

• Features → Segments
• Guides → Run an NPS survey
• Features → Events

Web delivery and page targeting

App platform setup and campaign targeting are separate: enable Web and allow your exact origins in SDK setup, then include Web in each campaign's Target step. Existing campaigns keep their native reach. Browser visitors are not automatically registered; your integration explicitly identifies users or opts into anonymous participation.

Use setPageContext({ screenName: 'account' }) for the current page, and track('checkout_completed', properties) for a configured event trigger. The SDK does not automatically track URLs or page views. These methods need an active participant; event ingestion needs analytics consent and display needs the experience's consent.

For campaigns combining native and Web delivery, upgrade API/workers and native SDKs to coordinated delivery first. Campaign limits apply to the same identified user across platforms. See the Web SDK guide for setup and troubleshooting.