Customer outcomes

Track a shared customer or account outcome

Configure a cohort once, enroll eligible customers, and follow progress across the whole population.

Shared outcomes are for repeatable programs such as trial activation. Configure the goal once, then track each eligible customer or account against the same milestones.

Connect real product facts

Automatic population tracking needs a trusted server-side feed of product facts and an explicit mapping to OutcomeArc customers or accounts. Support conversations and widget custom properties alone do not enroll your product population.

Have your integration developer connect the product’s current facts—such as plan, connected, and launched—to the configured goal. The server integration uses ingest_outcome_facts, not the read-only Conversation API. If you need help setting up this feed for your account, contact our team.

Send complete current snapshots with stable product identities, unique event IDs, and increasing revisions. Missing facts remain unknown; they aren’t treated as failed milestones.

Configure and enroll

  1. Open Outcomes → Configure shared outcome.
  2. Choose the shared goal and whether to track individual customers or accounts/workspaces. Account tracking counts a workspace once, not once per seat.
  3. Add 1–10 cohort conditions, such as plan equals trial. All conditions must match.
  4. Save paused and open Preview backfill to inspect eligible, enrolled, and untracked identities.
  5. Choose Enable enrollment, preview again, then Backfill this registered population.

Backfill works through the registered population in the background. Watch its progress and errors. After setup, new eligible fact snapshots can enroll customers automatically. Enabling enrollment does not enable customer outreach.

Read the population view

Filter by membership, segment, owner, current milestone, or customer/product identity. Summary cards and funnels cover the whole filtered population, not just the visible page.

Conversion is completed divided by enrolled. Time to milestone starts when tracking actually begins; it isn’t backdated to an imported product event. The selected date range applies to movement, while the funnel shows cumulative progress.

Unknown means there is missing evidence for unfinished milestones. Open a customer to see their evidence, health, milestones, and next actions.

Pause, recover, or exclude

Pause enrollment to stop processing new work while keeping existing progress. Run a new backfill after resuming to catch updates processed while paused. Use Retry from checkpoint for a failed backfill after resolving its cause.

Exclude an identity with a reason when it should no longer participate. History is retained, including people who are no longer eligible. Changes to the goal, cohort, or tracking unit require a deliberately configured new goal version rather than moving old progress automatically.

Browse all topics →

Still need a hand? Ask our team.