Beacon Targeting
Beacon targeting controls which users see a beacon and on which pages it appears.
Audience Targeting
Assign an audience segment to restrict the beacon to specific user groups. You can target by:
- User attributes -- Role, department, plan type, signup date, or custom properties passed via the SDK.
- Behavioral criteria -- Pages visited, flows completed, or actions performed.
- Predefined segments -- Reusable audience definitions from the Audiences section.
If no audience is assigned, the beacon is shown to all users.
Page Matching via Trigger
Use the URL Match trigger (configured under the Trigger tab) to control which pages a beacon appears on:
| Match Type | Behavior |
|---|---|
| Contains | The beacon appears on any page whose URL contains the specified string. |
| Exact | The beacon appears only on pages with an exact URL match. |
| Starts with | The beacon appears on pages whose URL starts with the specified prefix. |
| Regex | The beacon appears on pages whose URL matches a regular expression pattern. |
Element Visibility
Beacons only render when their target element is present in the DOM. If the target element is removed or hidden (e.g., behind a collapsed section or a dynamic route change), the beacon hides automatically and reappears when the element becomes visible again.