What is an audience in 100 Rocks?
An audience is a reusable set of visit rules for product-page Serving. Rules can use session activity, page use, scrolling, pointer behavior, hesitation, clicks, sections, or the visitor's local Daily Activities time group.
Audiences describe visit behavior. They do not identify a person or expose raw session recordings.
How do I create an audience?
- Open your project, then Serving.
- Open the Audiences tab.
- Select Create audience.
- Enter a clear name and choose whether the audience is globally active.
- Configure Desktop, Tablet, and Mobile separately.
- Add at least one rule to every active breakpoint.
- Select Save.
How do audience rules work?
Choose Match all when every rule must be true. Choose Match any when one matching rule is enough.
Numeric rules accept a minimum, a maximum, or both. Examples include scroll depth, page views, active time, click frequency, and hesitation frequency. The editor checks valid ranges and prevents the same metric from being added twice to one breakpoint.
Daily Activities uses one named local-time group such as Night owls, Early birds, Lunch timers, or Afterworks. It does not infer the visitor's timezone from an IP address.
Why can an automatic audience appear?
After enough observed sessions, 100 Rocks can create a Daily Activities audience that matches a recurring segment. The audience list labels its source as Automatic.
There is no separate notification yet. Review the rules and active status before using an automatic audience in Serving.
How do I edit, pause, or delete an audience?
Open Audiences and select Edit. You can change the name, global active state, breakpoint state, match mode, and rules.
Turning off the global active state removes the audience from the active Serving lane without deleting its definition.
Deleting an audience also removes its current product-page assignment. The action asks for confirmation.
When can an audience match a storefront visit?
Audience-based product-page assignment requires Preferences consent. Every metric used by the audience must also be available for that visit.
If consent, context, or a required metric is missing, the rule fails closed. The storefront continues with its deterministic baseline or all-traffic route.
When the audience is ready, connect it to a variant with Serving.
