Skip to main content
All CollectionsTimelinesAudience
Audience Segmentation via Inbound API Webhook
Audience Segmentation via Inbound API Webhook

Want to create your audience segments using inbound webhooks in addition to pixel and attendance data?

AEvent avatar
Written by AEvent
Updated over a week ago

Within an AEvent Timeline, you can define an audience and add a qualifier segment using an Inbound Webhook.

(Think if someone buys LIVE from the webinar, an Inbound Webhook from your CRM can immediately pluck them from any follow-ups in the timeline).

Webhooks can also be more reliable than IP or Cookie based tracking, and at times it can be easier to use them with your CRM/API/Zapier flows.

To set up an inbound Webhook, first, you need to create an audience that involves the inbound Webhook in the equation.

Step-By-Step Tutorial:

How To Get To Audience Tab

Go to the timeline that you are going to use

  • Then, on the left menu, select the Audience Tab

  • Then Click on 'Create New Audience'

For this example, we want to create an audience that will exclude anyone who has purchased. We're going to create an inbound Webhooks and add the tag 'Buyer'.

Once you create this audience type, make sure to copy the endpoint (via button) to place within your Zapier Flow / Webhook Entry, etc. or email=X

Above is the example code we received when clicking the copy endpoint button. Notice how it says r=X or email=X ? I'm going to use the email address here, so I will remove the r=X as well as the X from email=X and save it like this:

Next, within your tool of choice (we're using Zapier, for example), we will send that data to AEvent when someone makes a purchase of our product.

In the example below, we've created an outbound webhook in the Zapier flow. When someone purchases my product, we've instructed Zapier to send this value to AEvent through a webhook.

⚠️Notice ⚠️

We opted to use the email= version,

as our CRM has their email address and they just purchased.

Now, in certain situations, you can also utilize their Unique Registrant ID

and pass this using the r=X value. (Usually obtained as a custom field on-registration)

AND that's IT! Now when someone purchases a product, since we have Zapier tied in, it will send AEvent a notification advising that they are now a buyer and therefore a part of this audience.

In this audience example, we used a simple audience set. However, there is no restrictions to adding and or using the API audience endpoint to any degree!

Extra Segmentation: Let's say we want to make an audience that is all NON-Buyers, so after the event, only those who didn't make a purchase will receive any follow-ups from AEvent.

Here's How To Create It: AEvent can target anyone that didn't make a purchase (and exclude those that did):

Did this answer your question?