Pairing AEvent with an Outbound-Webhook can get you the data you want, where and when you want, and gives you total control over HOW that happens.
You can set up Outbound Webhooks to trigger both On-Registration and a timeline action (say all Cart-Abandoners).
It's easy to set these up; every piece of data you could want is formatted and sent in the outbound webhook call.
|
Timeline Actions:
 |
Adding a new Webhook as an AEvent Integration
To set up a Webhook, add it as an Integration. To do that, navigate to Integrations within AEvent, click Add Integration, and then select Webhook.
Then, name your integration as you see fit and click 'Add.' (With Webhooks, we recommend an easy identifier, as you may end up adding several Webhook integrations).
Now define the URL Endpoint of your Webhook, as well as Type, Format, Encryption and Structure.
(In general, POST, JSON, and Encryption OFF work best)
Need to include a dynamic value IN the webhook endpoint? IE Name, Email, et? You can use our personalization menu to dynamically define that value:
Our webhooks also support custom payloads, so you can design the outbound webhook call, format it, and formulate it as your endpoint is expecting to receive.
TO enable use, slide Custom Payload to On.
(NOTE: Custom Payloads require advanced developer knowledge and aren't something we can directly support when troubleshooting.)
Once your new Webhook integration has been successfully added, you will see its Connected state, and you can click on 'Test.'
A successful connection will yield a positive test result AND send a payload test packet to that endpoint. Congratulations, your Webhook is now connected to AEvent and can be set up within a campaign!
Configuring your Webhook Integration within a Campaign
In order to utilize your Webhook within AEvent, you need to activate it within the campaign you are working with. To do this, open the campaign you are working on.
Then, select Integrations, set your Webhook as Active, and click on the cogwheel.
If you do not (by default), this will send an outbound webhook with each new registration. If you want to use this within the campaign as Audience qualification, you need to disable this from occurring on registration.
And that's it. All new registrations to this campaign will make an outbound call to this Webhook Integration if set as active.
Creating a Timeline Action to Send a Webhook Action.
Within our timeline builder, you can set a Webhook action to occur at any point before, during, or after your event.
Our best practice recommendation would be to utilize Webhook timeline actions for precise audience targeting after your event.
It could be something as simple as an outbound Webhook for all attendees or non-attendees of the event. But you could go several layers deeper utilizing our Audience Segmentation options. In this tutorial, we will build a timeline action targeting Cart Abandoners.
Per the example above, at 8 AM the day after the Event a outbound Webhook action would trigger for anyone that was a Cart Abandoner from our event.
In this instance, I have elected to send the information Per Registrant. By selecting this, the system will send an individual Webhook call per registrant. The information would have been sent as a single payload packet if I hadn't selected this. (Generally, you want to check this unless you're a super-whiz)
After clicking Create, this action is now visible on the timeline.
How to remove your Webhook from AEvent
If you want to remove your Slybroadcast integration from AEvent, navigate to Integrations, locate your Slybroadcast integration, and click on the trashcan icon.
You will then be prompted to confirm the deletion.
(NOTE: Removing this integration will immediately affect its use with any campaigns that it is active in.)
If you are experiencing issues with this integration but do not desire to REMOVE it, we recommend reconnecting it instead. This will allow its configuration to
continue as set within your campaigns.
Once you confirm removal, the integration within AEvent no longer exists.
Layout of our Webhook payload (Per Registrant, customfields on the end)
{
"subscriber": {
"uuid": "registrant uid",
"firstname": "First Name",
"lastname": "Last Name",
"email": "Email",
"phone": "Phone Number",
"ipaddress": "IP Address",
"registrationdatetime": "Registration Date Time",
"joinurl": "https://joinevent.link/tenantid/registrantuid",
"customGroups": "Attendee, GroupName",
"timezone": "Timezone",
"country": "Country"
},
"webinar": {
"webinarID": "Gotowebinar True Webinar ID",
"timeZone": "America/Denver",
"timeStamp": "Webinar Start time",
"dayofweek": "Day of the week",
"dayofmonth": "Day and Month",
"day": "Day",
"month": "Month",
"year": "Year",
"esttime": "Time in Eastern Timezone",
"pasttime": "Time in PST Timezone"
},
"replay": {
"webinarID": "Gotowebinar True Webinar ID",
"timeZone": "America/Denver",
"timeStamp": "Webinar Start time",
"dayofweek": "Day of the week",
"dayofmonth": "Day and Month",
"day": "Day",
"month": "Month",
"year": "Year",
"esttime": "Time in Eastern Timezone",
"pasttime": "Time in PST Timezone",
"replayURL": "Replay URL"
},
"customfields": {}
}