This article covers:
What a segment automation does, and how it differs from a dynamic segment
Event-based vs. time-based automations, and which to use
The automation dashboard, history, and how to check performance
Where to go for the step-by-step setup of each type
In short
A segment automation builds a fan segment automatically, either on a schedule or tied to your game schedule, then pushes it to a destination without you rebuilding it each time. There are two types: event-based, which run relative to a game, and time-based, which run on a cadence you set. Once an automation is created, its goal and destination can't be edited, only deleted and recreated.
What a segment automation is
A segment automation replaces the manual work of rebuilding the same segment over and over. Instead of creating a 'single game attendees' segment by hand after every game, you set the criteria once and the automation creates it automatically from then on.
Common use cases:
Sending a reminder to ticket holders before every game
Running a weekly check on fans who haven't attended in the last month
Welcoming first-time attendees within 48 hours of their event
Automations vs. dynamic segments
| Dynamic segment | Segment automation |
Updates | Grows and shrinks as fans qualify and stop qualifying | Fixed once created. Each run is a new snapshot |
Timing | Updated after every data refresh | Runs on a schedule or game trigger |
Use it when | You need an audience that stays current | You want to act on who qualified at a specific point in time |
Event-based vs. time-based
| Event-based | Time-based |
Runs | Relative to each game in your schedule | On a cadence you set: hourly, daily, weekly, or monthly |
Best for | Campaigns tied to a specific game, such as pre-game reminders or post-game follow-up | Ongoing lead flow and recurring checks that are not tied to one game |
Setup walkthrough |
Note: Not sure which to use? If the campaign only makes sense relative to a specific game, use event-based. If it should run on its own clock regardless of the schedule, use time-based. For exactly how each type is timed and evaluated, see How automations run.
Getting set up
From the Segmentation menu, select Automations, then New Automation. From there you choose Event Based or Time Based, then either an Automation Play or Create Custom Automation. For the full walkthrough of each type, see Set up an event-based automation or Set up a time-based automation.
To see which play fits your goal, see Automation plays available today.
Reviewing automations
The automation dashboard
The Segment Automation Dashboard lists every automation you've created, with its type, period, cadence, last and next run, remaining runs, destinations, and status.
Column | What it shows |
Type | Event based or time based |
Period | The start and end dates the automation is active for |
Runs every | The cadence or trigger for the automation |
Last run / Next run | When the automation last generated a segment, and when it will next |
Runs left | Remaining runs within the automation period |
Destinations | Where generated segments are pushed |
Status | Scheduled, Active or Completed |
Automation history
Click into an automation from the dashboard to see its run history: the trigger, segment size, run date, duration, and status. Each run shown here is a child segment. For what a child segment is, why a run can fail, and what each failure category means, see How automations run.
Downloading a segment manually
If you don't have a push destination enabled, you can still get the fan list. From the automation history, click the segment size, select View Fan List in Segment Analyzer, then select Download CSV.
Still need help?
Contact StellarAlgo support and include:
The automation name
The type: event based or time based
The date and time of the run in question