Skip to main content

Audience Creation

Build custom AEvent audiences by segmenting registrants on time attended, presence, location, page views, and inbound webhooks for precise event targeting.

For Intermediate Advanced Users

With AEvent Custom Audience abilities, the audience segmentation and targeting ability is endless.

Every Campaign is created with a default set of audiences based on the Delivery Platform selected within that Campaign.

AEvent has further targeting / segmentation abilities based on Time Attended, Present / Not Present, Page Views (and Page View Duration on video campaigns), Geographic Location, Custom Fields, Inbound Webhook, and Keyword.

AEvent handles all equations in an audience segmentation as an IF and then an AND statement.

All conditions in one audience are combined with AND, so a person must meet every condition. To combine groups with OR (or AND), point a single action at more than one audience. An action can target multiple audiences, and you choose how they join.


Time Attended - (Equal, Less Than, Greater Than), This enables you to create an Audience segmentation based upon total time spent (or not spent) on your Event.

Present - (Equal, Less Than, Greater Than), This enables you to create an Audience segmentation based upon your Attendee being present at, before or after an exact minute during your Presentation.

Not Present - (Equal, Less Than, Greater Than), the inverse of Present. This enables you to target an Attendee who is not watching at, before, or after an exact minute during your Presentation.

Location - (Equal, Not Equal), This enables you to create an Audience segmentation based upon your what Country your Attendee was in at time of registration.

Custom Field - (Matches, Does Not Match, Exists, Does Not Exist), This enables you to create an Audience segmentation based upon a registration field value. For example, everyone whose plan field equals "trial", or everyone who has any value in a "company" field.

Page View - (Did Visit, Didn't Visit), This enables you to create an Audience segmentation based upon whether or not your attendee visited a page that you have specified. The URL is matched as a "contains", so the visited page's address just has to include what you enter. (This works in conjunction with our Page Tracking pixel).

Page View Duration - (Equal, Less Than, Greater Than), on video or VSL-style campaigns (a video page instead of a live webinar), this segments by how many minutes of the video the attendee watched. It replaces Time Attended and Present on those campaigns.

Keyword - (Matches, Does Not Match), This enables you to create an Audience segmentation based upon whether or not your attendee typed a specific word or phrase in the webinar chat. It updates live during your Event and works on both Zoom and AStream. (For example, an audience of everyone who typed "pricing".)

Inbound Webhook - (Matches, Does Not Match) This enables you to create an Audience segmentation based upon whether or not an inbound Webhook was received for your attendee. (Purchase Buyer Exclusion, Action, Call Booking, Etc.)

Once you define your Webhook value, the Copy Endpoint button is enabled. This needs to be copied out and into the platform you are sending the Webhook from.

How Page View Matching Works

When you add a Page View condition, AEvent matches the URL you enter as a "contains" match, not an exact match. It looks for any tracked page visit whose address contains the text you typed.

  • A shorter or more general URL automatically covers every page beneath it. If you enter yoursite.com/replay, the condition matches visits to yoursite.com/replay, yoursite.com/replay-2, and yoursite.com/replay-bonus, because each one contains "yoursite.com/replay".

  • You do not need a separate condition for every version of a page. One general URL already captures them all.

  • To match a single page and nothing else, enter the most specific URL that is unique to that page.

Note: Page View conditions only track pages that have the AEvent tracking script installed. See How to Install the Audience Tracking Script.

Troubleshooting: "These conditions contradict each other"

If you see the message "These conditions contradict each other, so no one could ever match this audience," it means the combination you built can never be true for one person at the same time, so AEvent stops you before saving.

Because every condition is combined with AND, all of them must be true for the same person. The highlighted rows show which conditions clash. The most common causes are:

  • Overlapping "Did Not Visit" pages. Since Page View is a "contains" match, Did Not Visit yoursite.com/replay already excludes anyone who visited yoursite.com/replay-2 or yoursite.com/replay-bonus. Adding those longer URLs as their own "Did Not Visit" rows is redundant, and the builder flags the overlap. Fix: keep only the shortest URL and remove the nested ones.

  • Impossible time ranges. For example Time Attended Greater Than 55 AND Time Attended Less Than 55. Adjust the values so a real range exists, such as Greater Than 10 and Less Than 60.

  • Opposite conditions on the same value. For example Location Equal to US AND Location Not Equal to US, or an Inbound Webhook set to both Matches and Does Not Match the same value.

Adjust or remove one of the highlighted conditions and the error clears.

Full Tutorial:

A-Z Guide:

Did this answer your question?