How Triggers Work and How to Use Them to Control App Content

Summary

Triggers control who sees specific pages, events, and Smart Buttons in the app. A trigger defines a group of users based on roles, groups, behaviors, or location, and then applies content visibility rules to that group. This ensures the right content appears to the right users, especially on the Home feed.

Who this is for

• Community managers and administrators configuring app content visibility
  
  
• Teams managing personalized experiences for different user groups
  
  
• Admins responsible for controlling Home feed content, events, and buttons
  
  

Prerequisites

• You have access to the Alosant Admin portal
  
  
• You have permission to create and manage Triggers
  
  
• User Roles, Groups, Pages, Events, or Places already exist in the system
  
  

Steps

Create a trigger

1. In the Admin sidebar, select Triggers.
   
   
2. Click + New Trigger.
   
   
3. Enter a descriptive Name for the trigger.
   
   
4. Configure the trigger conditions that define which users should match.
   
   
5. Enable Run Daily if the trigger should refresh automatically.
   
   
6. Set a Run Time if Run Daily is enabled.
   
   
7. Click Save.
   
   

Configure trigger conditions

1. Select a User Role to match users assigned to that role.
   
   
2. Select a User Group to match users in a specific group.
   
   
3. Select an Interested Event to match users who liked an event.
   
   
4. Select a Reserved Event to match users who reserved an event.
   
   
5. Select a Viewed Event to match users who viewed an event.
   
   
6. Enter Follows User (ID) values to match users following a specific user.
   
   
7. Enable Only Members Located Near Event Location and set a distance if location matters.
   
   
8. Enable Only Members Located Near Custom Location and set an address if needed.
   
   

Edit an existing trigger

1. In the Admin sidebar, select Triggers.
   
   
2. Click the name of the trigger you want to edit.
   
   
3. Update the trigger name if needed.
   
   
4. Adjust the run time or conditions as needed.
   
   
5. Click Save.
   
   

Run a trigger manually

1. In the Admin sidebar, select Triggers.
   
   
2. Click the trigger you want to run.
   
   
3. Click View Expected Results.
   
   
4. Scroll to the bottom of the page.
   
   
5. Select Run Trigger Now to run with location logic applied.
   
   
6. Select Run Trigger Ignoring Location to skip location rules temporarily.
   
   

View expected results for a trigger

1. In the Admin sidebar, select Triggers.
   
   
2. Click the trigger you want to review.
   
   
3. Click View Expected Results.
   
   
4. Review matching users, events, and pages shown on the results screen.
   
   

Use triggers on a page

1. In the Admin sidebar, select Pages.
   
   
2. Edit the Information Page you want to pin.
   
   
3. Select one or more Triggers.
   
   
4. Scroll down and click Save.
   
   

Expected result

• Users matching the trigger conditions see the correct pages, events, and Smart Buttons.
  
  
• Pinned pages appear at the top of the Home feed for matched users.
  
  
• Trigger logic refreshes automatically based on the configured run schedule.
  
  

Troubleshooting

• Content is not appearing for users: Confirm the trigger is set to run daily or has been run manually.
  
  
• Too many users are matching: Add additional conditions to narrow the trigger logic.
  
  
• Location-based rules are not working: Verify distance, address, and user location data.
  
  
• Recent changes are not visible: Wait 5–10 minutes after running or saving a trigger before testing.
  
  

FAQ

What does “Run Daily” do?
It refreshes trigger matching automatically at the scheduled time.

What happens if Run Daily is not enabled?
The trigger will not be used for events or pages and can only be used for Smart Buttons.

Do all trigger conditions need to be met?
Yes. All selected conditions must be true for a user to match a trigger.

How many pinned pages can users see?
Up to five pinned pages per user role for logged-in users and up to three for guest users.

Notes / Escalation

• Important: Trigger logic uses AND conditions, meaning every configured condition must be met.
  
  
• Important: Location-based conditions should only be used when proximity is required.
  
  
• Internal-only note: “Run Trigger Ignoring Location” is commonly used during early app launches when limited location data is available.
  
  
• Escalate to the Alosant internal teams if triggers do not update after multiple runs or if content visibility is inconsistent across users.