How to create Segment?
Last updated
Last updated
About Segmentation and its options
Segments : Segmentations are defined based on application requirements and function as rules with various conditions such as
to determine "who should see" the beacon features ( such as Modal , Product Tour etc ) and "who should not."
to determine "where to show" the beacon features ( such as Modal , Product Tour etc ) and "where not to show".
The user interface is designed to be intuitive, with additional information provided through image references included in this document where needed.
A segment can be used for any feature within a beacon, and the feature will behave according to the segment connected to it.
Steps to Access Segments
Verify Access Permissions Ensure you are an admin or a user with access to the Beacon Dashboard for your application. Note: If you do not have access, request the admin to add you as a member by navigating to: Beacon Dashboard > Settings > Team > Add Member.
Log In to the Beacon Platform Visit and log in using your email ID. An OTP will be sent to the provided email for verification (if access has been granted).
Navigate to the “Segments” on ‘side nav bar’ Section
Go to Beacon Dashboard > Segments
This will take you to the “Segments List” page.
Click on the “New Segment” button, located in the top-right corner.
This action will open a side panel on the right side of the page.
A variety of options are available for defining these segments, as detailed below, with some specifically designed for the Beacon team.
The Page URL option lets you define rules based on specific page endpoints (URLs) that users visit. This is useful for targeting or filtering users based on their interaction with particular pages.
Example of Using Segments: Refer to the video by clicking on it ,
For instance, if you want to display a ‘modal’ named "Template 1" only on the page URL https://www.orangehrm.com/en/company/about-us, you can use a segment to achieve this. Page URL other Example: If you want to target users visiting pages related to "products," you can set a rule like include: "products" or starts with: https://example.com/products.
Options for filtering:
is:
Matches a URL exactly as specified.
Example: https://example.com/home matches only this exact URL.
is not:
Excludes a specific URL.
Example: Rule excludes https://example.com/home.
include:
Matches URLs that contain a specific string.
Example: If the string "products" is specified, URLs like https://example.com/products/shoes are matched.
not include:
Excludes URLs containing the specified string.
Example: URLs with "cart" in them (e.g., https://example.com/cart) are excluded.
starts with:
Matches URLs that begin with a specific string.
Example: https://example.com/shop matches all URLs like https://example.com/shop/shoes and https://example.com/shop/accessories.
ends with:
Matches URLs that end with a specific string.
Example: /checkout matches URLs like https://example.com/cart/checkout.
regex (regular expressions):
Provides advanced matching using regex patterns for flexibility.
Example: A regex like ^https:\/\/example\.com\/(blog|news) matches both https://example.com/blog and https://example.com/news.
in:
Matches any URL from a predefined list.
Example: https://example.com/page1, https://example.com/page2 match only these specific URLs.
The Domain option lets you create rules for different domains associated with your clients. This is helpful when dealing with multiple domains and needing tailored segmentation.
Options for filtering:
is:
Matches an exact domain name.
Example: example.com matches only this domain.
is not:
Excludes a specific domain name.
Example: Exclude example.com from the segment.
include:
Matches domains containing a specific string.
Example: The string "shop" matches domains like shop.example.com or myshop.com.
not include:
Excludes domains containing the specified string.
Example: Domains with "blog" (e.g., blog.example.com) are excluded.
starts with:
Matches domains that start with a specific string.
Example: support matches domains like support.example.com.
ends with:
Matches domains that end with a specific string.
Example: .org matches domains like example.org or nonprofit.org.
regex (regular expressions):
Provides advanced matching using regex patterns for domains.
Example: A regex like .*\.example\.com$ matches any subdomain under example.com (e.g., shop.example.com, blog.example.com).
in:
Matches any domain from a predefined list.
Example: example.com, shop.example.com match only these specific domains.
The DOM Element option allows rules to be defined based on elements within a webpage's Document Object Model (DOM).
For example:
Use DOM Element rules to target users interacting with a specific button.
Options for filtering:
ID:
Matches an element with a specific id.
Example: Rule targeting an element with id="login-button" matches <button id="login-button">Login</button>.
Class Name:
Matches elements with a specific CSS class name.
Example: Rule targeting class="product-card" matches <div class="product-card"></div>.
XPath:
Matches an element using its XPath.
Example: If the XPath is /html/body/div/header, it matches the <header> element at the specified location.
The Device option lets you filter users based on the type of device they are using.
For example:
Use Device rules to target mobile users for app-specific campaigns.
Options for filtering:
is:
Matches a specific device type.
Example: is: mobile targets users on mobile devices only.
is not:
Excludes a specific device type.
Example: is not: tablet excludes users on tablets.
in:
Matches any device from a predefined list.
Example: in: [mobile, desktop] targets users on either mobile or desktop devices.
Dropdown Options:
Mobile: Targets smartphones.
Desktop: Targets users on desktops or laptops.
Tablet: Targets users on tablets.
The Events option is used to create rules based on specific user actions or events.
For example:
Use Events to identify users who haven't completed a desired action.
Options for filtering:
Occurred after:
Matches events occurring after a specific timestamp.
Example: If set to "2023-12-01 10:00:00," it targets events logged after this time.
Occurred before:
Matches events occurring before a specific timestamp.
Example: If set to "2023-12-01 10:00:00," it targets events logged before this time.
Occurred time more than:
Matches events occurring more than a specified number of times.
Example: Rule with "more than 5 times" matches users triggering the event 6 or more times.
Occurred time less than:
Matches events occurring less than a specified number of times.
Example: Rule with "less than 3 times" matches users triggering the event 2 or fewer times.
Has occurred:
Matches if the event has occurred at least once.
Example: Rule matches users who have logged into the platform.
Has not occurred:
Matches if the event has never occurred.
Example: Rule matches users who have never made a purchase.
Occurred count greater than:
Matches if the event occurred more than a specified number of times.
Example: "Count > 10" matches users clicking a button more than 10 times.
Occurred count less than:
Matches if the event occurred fewer than a specified number of times.
Example: "Count < 5" matches users visiting a page fewer than 5 times.
The User Metadata option allows rules to be based on user-specific attributes (e.g., profile data).
To access metadata, open the browser console where your application is running and enter BeaconBar.User.metadata. Make sure the Beacon Bar is enabled for your application beforehand.
Let's create a segment for the “Zone” key as illustrated above (Zone: “Corporate”). The configuration will appear as shown in the image below.
For example:
Use User Metadata to target users based on their demographics or subscription status.
Options for filtering:
1. is / is not
Description: Matches or excludes an exact metadata value.
Examples:
is: "Premium"
Targets users with a subscription type explicitly set to "Premium."
Use case: Send promotional offers to Premium users only.
is not: "Guest"
Excludes users with a role marked as "Guest."
Use case: Exclude non-registered users from email campaigns.
Description: Compares numerical metadata values.
Examples:
greater than: 30 (Age)
Matches users older than 30 years.
Use case: Target an age-specific group for senior-friendly product advertisements.
less than: 50 (Orders)
Matches users who have placed fewer than 50 orders.
Use case: Encourage less active customers to order more with special incentives.
Description: Matches numerical metadata with inclusive conditions.
Examples:
greater than or equal: 100 (Reward Points)
Targets users with 100 or more reward points.
Use case: Notify eligible users about redeemable rewards.
less than or equal: 3 (Subscription Duration in Months)
Matches users who have been subscribed for 3 months or less.
Use case: Send onboarding tips to new users.
Description: Checks if metadata includes or excludes specific values (useful for lists).
Examples:
include: "sports" (Interests)
Matches users whose interests include "sports."
Use case: Promote sports-related content or products.
not include: "politics" (Preferences)
Excludes users with "politics" in their preferences.
Use case: Filter out users who might not engage with general news updates.
Description: Matches metadata that begins or ends with a specific string.
Examples:
starts with: "John" (Name)
Targets users whose names begin with "John."
Use case: Personalize greetings in email campaigns for specific user subsets.
ends with: "@gmail.com" (Email Address)
Matches users with Gmail addresses.
Use case: Provide Gmail-specific instructions for service configuration.
Description: Matches metadata using regular expressions for advanced filtering.
Examples:
regex: "^A[a-z]+" (Name)
Matches users whose names start with "A" followed by lowercase letters.
Use case: Create fun, name-based campaigns targeting specific groups.
regex: "\\d{4}-\\d{2}-\\d{2}" (Signup Date)
Matches users with a valid date format in their signup metadata.
Use case: Ensure proper formatting for date-related operations.
Description: Matches metadata from a predefined list.
Examples:
in: [USA, Canada, UK] (Country)
Matches users from any of these countries.
Use case: Promote localized offers for North American and UK markets.
in: [Gold, Silver, Platinum] (Membership Tier)
Matches users with specific membership levels.
Use case: Create tier-specific loyalty programs.
Description: Matches metadata explicitly set to true or false.
Examples:
true: "is_subscribed"
Matches users with an active subscription.
Use case: Send content updates to paying customers only.
false: "has_unread_notifications"
Matches users without any unread notifications.
Use case: Notify users who are up-to-date with their notifications.
Description: Matches dates relative to a specified value.
Examples:
is before: 2023-12-01 (Signup Date)
Targets users who signed up before December 1, 2023.
Use case: Send thank-you messages to long-term users.
is after: 2023-01-01 (Last Login Date)
Matches users who logged in after January 1, 2023.
Use case: Focus retention campaigns on recently active users.
Description: Matches metadata that evaluates as true, does not exist, or exists.
Examples:
truthy: "has_profile_picture"
Matches users who have uploaded a profile picture.
Use case: Highlight these users in user showcases.
not defined: "phone_number"
Matches users without a phone number on file.
Use case: Prompt users to update their contact details.
This feature helps track and segment users based on their interactions within the app or platform. After selecting an Analytics Event, you can further filter it using conditions like occurred after, occurred before, occurred time more than, or occurred time less than.
Description: Tracks the first time a user opened the app.
Examples:
Occurred after: "2023-01-01"
Targets users who first visited the app after January 1, 2023.
Use case: Welcome new users who joined recently.
Occurred time less than: "7 days"
Matches users whose first visit was less than 7 days ago.
Use case: Send onboarding tips to new users.
Description: Tracks the most recent time a user accessed the app.
Examples:
Occurred before: "2023-12-01"
Targets users who haven't visited since December 1, 2023.
Use case: Run re-engagement campaigns for inactive users.
Occurred time more than: "30 days"
Matches users who haven’t visited the app in over 30 days.
Use case: Offer incentives to bring them back.
Description: Tracks the first time a user invoked a feature or service in the app.
Examples:
Occurred after: "2023-06-01"
Targets users who started using a feature after June 1, 2023.
Use case: Identify users interested in a new feature rollout.
Occurred time less than: "7 days"
Matches users who invoked a feature for the first time within the last 7 days.
Use case: Provide tutorials to first-time users.
Description: Tracks the most recent time a user invoked a feature or service.
Examples:
Occurred before: "2023-12-15"
Targets users who last used a feature before December 15, 2023.
Use case: Encourage re-use of dormant features.
Occurred time more than: "14 days"
Matches users who haven’t invoked a feature in over 14 days.
Use case: Send feature updates or reminders.
Description: Tracks the number of times users executed commands in the app.
Examples:
Occurred time more than: "10 times"
Matches users who executed commands more than 10 times.
Use case: Offer advanced tips to frequent users.
Occurred time less than: "3 times"
Matches users who executed commands fewer than 3 times.
Use case: Prompt inactive users to explore app features.
Description: Tracks the number of times users accessed help documentation.
Examples:
Occurred after: "2023-01-01"
Targets users who opened help docs after January 1, 2023.
Use case: Analyze engagement with newly updated documentation.
Occurred time less than: "5 times"
Matches users who accessed help docs fewer than 5 times.
Use case: Offer personalized help for users needing more assistance.
Description: Tracks users who have completed a guided journey in the app.
Examples:
Occurred before: "2023-12-01"
Targets users who completed journeys before December 1, 2023.
Use case: Introduce them to advanced journeys.
Occurred time more than: "3 times"
Matches users who completed journeys more than 3 times.
Use case: Reward loyal users for active participation.
Description: Tracks users who have viewed but not necessarily completed a guided journey.
Examples:
Occurred after: "2023-11-15"
Targets users who viewed journeys after November 15, 2023.
Use case: Send reminders to complete the journey.
Occurred time less than: "2 times"
Matches users who viewed fewer than 2 journeys.
Use case: Encourage users to explore more journeys.
Each Analytics Event can be further filtered using the following conditions:
Occurred after: Filters events that happened after a specific date or time.
Example: Occurred after: "2023-01-01" targets events starting January 1, 2023.
Occurred before: Filters events that happened before a specific date or time.
Example: Occurred before: "2023-12-31" excludes events after December 31, 2023.
Occurred time more than: Filters events occurring more than a specified number of times.
Example: Occurred time more than: 5 targets users who performed the action more than 5 times.
Occurred time less than: Filters events occurring fewer than a specified number of times.
Example: Occurred time less than: 3 targets users who performed the action fewer than 3 times.
These Analytics options and filters help you segment users based on behavior patterns, enabling precise targeting for personalized messaging, re-engagement campaigns, and feature adoption strategies.
Note: If you have any questions, please don't hesitate to reach out to us at Support@beacon.li
