A campaign is the one container that holds your entire event, start to finish. Registration, the confirmation page, the reminders, the event itself, and the replay all live inside it.

Think of the journey a person takes: they register, land on your confirmation page, receive reminders leading up to the day, attend the event, and afterward can catch the replay. All of that is one campaign.

That is how a single event turns into a complete funnel instead of a bunch of disconnected pieces you have to wire together yourself.

Think of your timeline as a recipe. The actions on it (the emails, the texts, the tags, the reminders) are the steps in that recipe. You write the recipe once.

When you schedule the same campaign again, you are baking a fresh batch from that same recipe. You are not copying your actions, nor are you stacking a second set of steps on top of the first. The recipe remains a single, clean set of instructions.

So what actually fills up your calendar?

The batches, not the steps. Each scheduled event is a new batch, and your recipe runs fresh for each one. Your reminder email does not become ten reminder emails on the timeline just because you scheduled ten events. It is still one step in the recipe, and it runs for each batch.

The nice payoff: change the recipe once, and every future batch uses the new version automatically.

Live and evergreen campaigns run on the same engine underneath. The difference lies in how the event time is set and how your campaign's timeline calendar displays it.

A live timeline points to one fixed date. Everyone is headed toward the same moment on the calendar.

​

An evergreen timeline centers on each event's scheduled run, so the timeline actions occur around each scheduled event's start time.

Same recipe, same actions, just a different way of setting the clock. You can even switch a timeline from one to the other. For the full walkthrough, see Difference Between a Live Timeline, an Evergreen Timeline, and Converting Between The Two.

One honest heads-up so you do not mix two things up: how your event streams (AStream, Zoom, or GoToWebinar) is a separate choice from live vs evergreen. You can run any of those streaming sources as either live or evergreen. They are two different knobs, not one.

An action is one magic moment: sending a text, applying a tag, firing a webhook, or triggering an Encore. If your recipe does something, that something is an action.
​
With our Timeline coupled with our Audience Builder, you can get build very precision-oriented actions targeting defined audiences VS a spray and pray approach.

How usage counts. An action counts each time it actually fires for a real, qualifying person. Setting it up costs nothing, and people it skips are never counted.

Here is a friendly example. Say you have a reminder text aimed at no-shows. 500 people register, and 400 attend, leaving 100 no-shows. That action counts as 100, one for each person it actually reached. It never counts the 400 attendees it skipped, nor the setup. If that registrant doesn't submit a phone number at the time of registration, you are NOT counted against an action. Only those who have provided a working phone number will be added to your 100-count.

We count the execution, not the machinery. Some other tools (like Zapier) burn several "tasks" for the internal steps of a single automation run. AEvent does not work that way. We count the qualifying action that actually fires, and that is it.

There is one friendly exception. An auto-chat message sent to your live audience counts as a single action, no matter how many people are watching. It is one message to the room, not one per viewer.

What each plan includes:

What if you go over? We do not cut you off, and we do not surprise-bill you. If your usage is trending past your allowance, we reach out and help you pick the plan that fits how you are growing.

One last thing to keep separate: texts, MMS, ringless voicemail, or other integration types each carry their own carrier cost on your own connected account (like your Twilio account), on top of counting as an action. That messaging cost is billed by your integration provider, not by us.