Audience
Start with the basics: show a guide to everyone, only your signed-in users, or only anonymous visitors. The simplest lever for making sure the right people see the right thing.
All, logged-in, or anonymous
Choose the broad audience for each guide in a single click.
Match the message
Onboard signed-in users, or welcome anonymous visitors differently.
Layer on more
Combine with traits and segments for finer control.
Live in three steps.
Open targeting
In any guide, open who-sees-it.
Pick an audience
All, logged-in, or anonymous.
Publish
Only the right people see it.
Three audiences, three different welcomes.
The audience switch — everyone, logged-in, anonymous — sounds trivial until you use all three deliberately. A docs-plus-app product is the clean example.
Anonymous visitors
On public docs pages, a slideout for anonymous visitors only: "Reading about the API? Get a key in two minutes." Logged-in users never see it — they have keys.
Logged-in users
Inside the app, the activation tour targets logged-in users. Anonymous traffic that stumbles onto a shared link gets nothing — a tour of an app you cannot use is noise.
Everyone, sparingly
The maintenance banner targets everyone: it is true for all humans on the site. "Everyone" is the right choice exactly when the message is.
Then narrow with rules
Each audience accepts further trait rules or a saved segment — logged-in AND plan equals trial is where targeting starts to compound.
What to expect: Nobody sees a guide that assumes a state they are not in — the quiet baseline of respectable targeting. Reports per guide confirm reach matches the population you expected.
When not to use audience.
No pattern fits every job. Here’s where we’d point you at something else — sometimes ours, sometimes not.
As your only filter
"Logged-in users" is a coarse bucket. If the guide is for admins on trial in week two, stopping at the audience switch shows it to twenty times the right population — add trait rules or a segment.
Trait targeting for anonymous visitors
Anonymous visitors carry no traits — there is nothing to match. If a rule must apply, the user must be identified first; for visitors, page-URL scoping is the lever you actually have.
Splitting tests by audience
Do not fake an A/B test by aiming variants at different audiences — the groups differ by definition. Use the built-in experiments, which split randomly inside one audience.
How does Wakeline know who is logged in?
Your app calls identify() after login with the user's ID (and any traits). From then on the visitor is a known user; before that they are anonymous. The audience switch reads exactly that state.
What do anonymous visitors get?
Guides aimed at everyone or at anonymous visitors, scoped by page URL and triggers. No traits exist yet, so trait-based segments cannot match — by design, not limitation.
Can one guide serve both signed-in and signed-out users?
Yes — audience "everyone". Use it only when the content is truly universal (maintenance, incidents). If the copy says "your dashboard", it is not universal.
Where do I set this?
In the flow's Configuration tab, next to trigger and frequency — audience first, then optional segment or attribute rules narrow further. The audience is evaluated fresh at view time, so a user who logs in mid-session flips buckets immediately.
Can I preview who a guide will reach before publishing?
The audience and rules read back in plain terms on the Configuration tab, and your user list shows the traits targeting will evaluate. Publish-time discipline is simpler than it sounds: read the rule aloud, check a known user's profile against it, and the reach question answers itself.
See it on your own app.
Ship your first guide in minutes. Free to start — no credit card.