Within an AEvent Timeline you can define an audience and add a qualifier segment using an Inbound Webhook. (Think, 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 using them, with your CRM/API/Zapier flows.

To setup an inbound webhook, first you need to create an audience that involves the inbound webhook in the equation. TO get to audiences, I will edit the Timeline that I want to work on, and open Settings -> Audiences. Then I'll click on 'Create a new audience'.

In the example below I want to create an audience that will exclude anyone that has purchased. I'm going to create an inbound webhook, and add the tag of 'Buyer'.

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

Above is the example code I 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 I've created an outbound webhook in the Zapier flow. When someone purchases my product, I've instructed Zapier to send this value to AEvent thru a webhook.

(Notice, I opted to use the email= version, as my 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 my product, since I 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, I used a simple audience set. However, there is no restrictions to adding and or using the API audience endpoint to any degree!