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
Describe your segment
Open Settings → Define Audience Segments. 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.
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.
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
"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."
Each condition shows a confidence score. If AI can't map something, it tells you and suggests a rewrite.
What AI understands
- Visit count: how many times a user has hit a page or triggered an event. "Visited pricing 3+ times" →
visit_count.pricing ≥ 3 - Time windows: recency of first or latest visit. "New users in the last 7 days" →
days_since_first_visit ≤ 7 - Pages visited: specific paths or patterns. "Has visited the blog" →
pages_visited includes /blog/* - Identify properties: whatever you pass to
identify()— plan, signup date, role, any custom trait. - Boolean logic: AND, OR, NOT combinations. "Enterprise users OR anyone on a trial" translates to a top-level OR group.
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
- Pricing stallers: 3+ pricing visits, no signup → tooltip on pricing CTA: "Still comparing? Book a 15-min demo."
- Trial day 5: signed up 5 days ago, no activation milestone → modal: "You haven't created your first form yet. Want a walkthrough?"
- Power users: 20+ sessions, created 5+ forms → banner: "Invite your team — up to 3 members on Growth."
- Churn risk: no visit in 14 days, was previously active → email via your existing platform using the event webhook as a trigger.
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.