← Back to Onboardics Sign in

AI-Defined Audience Segments

Describe who you want to reach. AI builds the segment.

AI-defined audience segments in the Onboardics dashboard

The problem with generic audiences

Broadcasting the same flow to every user is lazy messaging. "Welcome!" shown to your power user on their 40th visit is noise. "Upgrade to Growth!" shown to someone who just signed up five seconds ago is annoying. Good in-app messaging targets specific users in specific states — the ones close to converting, the ones stalling, the ones churning. Most tools make you hand-code those rules. Onboardics asks you to describe them.

How it works

Step 1

Describe your segment

Open the Segments tab in the dashboard sidebar. Give the segment a name and write a description in plain English. “Users who visited pricing 3+ times but haven’t signed up” is a complete spec.

Step 2

AI translates to conditions

Claude reads your project's actual event data — page paths, identify() properties, visit patterns — and maps your description to structured conditions. Preview the rules with confidence scores before saving.

Step 3

Target flows at that segment

In the flow builder, pick the segment from the Audience dropdown. That flow now only fires for users who match. The evaluation happens client-side in our tracking snippet — no server round-trip, no delay.

Real example

You describe

"Users who visited pricing 3 or more times in the last 14 days but haven't signed up yet — and who came from the blog originally."

What AI generates
visit_count.pricing ≥ 3 days_since_first_visit ≤ 14 identify_property.signedup != true pages_visited includes /blog/*

Each condition shows a confidence score. If AI can't map something, it tells you and suggests a rewrite.

What AI understands

Where segments run

Segment evaluation happens client-side in the Onboardics tracking snippet. When a user loads a page, the snippet reads their visit history from localStorage (capped at 200 visits, cleaned every session) and evaluates each saved segment in under a millisecond. Matching segments get cached for the session. No server round-trip means no delay — flows fire the moment they should.

This also means segments work even for unidentified anonymous users. A visitor who lands on pricing three times over a week without signing up can be targeted by a flow, even though Onboardics never learned their email.

Pair segments with flows

Every event the snippet captures is segmentable

Segments aren't limited to page views and clicks. Every event type the tracking snippet emits is a dimension you can build conditions against:

Using custom events

Anything the default event capture misses, you emit yourself with one function call. Custom events flow into the same pipeline as page views and clicks, and are usable in segment conditions immediately.

// After the snippet has loaded:
window.__onboardics.track('invoice_sent', { amount: 4200, plan: 'growth' });

The snippet loads asynchronously, so window.__onboardics may not be defined immediately on page load. Either call track() from an event handler (button click, form submit, etc.) or guard with if (window.__onboardics) window.__onboardics.track(...).

Example segments by product type

SaaS

Marketplace

Content / Media

Pricing

AI-defined audience segments are available on Growth ($199/mo) and above. Free and Starter can target flows by page path and visitor type, but segment definitions require Growth.

Start free →    Try the live demo →