Skip to main content
Drip

How to integrate Drip into AEvent

AEvent avatar
Written by AEvent
Updated over 4 months ago

New leads generated for your AEvent timelines can be sent via API to your Drip account at the time of registration.

Then, through AEvent, you can initiate timeline actions, triggering the right message for the right audience at the right time, with your email sequences fully customized and dynamic, unlocking full evergreen automation potential.

Timeline Actions:

Adding your Drip Account to AEvent

In order to add your Drip Integration, you will need to first navigate to Integrations within AEvent, click Add Integration, and then search / select Drip.

Then name your integration as you see fit, and click 'Add.'

When you click on 'Add,' a pop-up from Drip will appear. Please log in to your Drip account.

Once logged in, you will need to click on Authorize to grant access.

Once your Drip account has been successfully added, you will see its Connected state, and you will be able to click on 'Test'.

A successful connection will yield a positive test result. Congratulations, your Drip account is now successfully connected to AEvent!

Configuring your Drip Integration within a Timeline

In order to utilize your Drip Integration within AEvent, you need to activate it within the timeline you are working with. To do this, open the timeline you are working with.

Then select Integrations, set your Drip Integration as Active, then click on the cogwheel to define your settings.

Within the Integration Settings, we can select either a Campaign, Workflow, or Tag to add the registrants to (when they register).

We HIGHLY RECOMMEND clicking on Custom Fields (Personalization) - Show, and setting up some custom personalization fields.

These are values that include not only email and name (Join Link, Replay Link, Day of Webinar, Day of Week, Time, UTM Tracking Parameters, etc.) and are sent along with the new subscriber information to Drip.

We've made the creation of these fields easy, and by clicking the 'Create System Fields button', AEvent will automatically create within Drip the needed Custom Fields, while selecting those values within AEvent.

You can also use the Create Single Field to create a single Custom Field within Drip. OR you can manually create fields / use pre-created fields. If you manually create a new field within your Drip integration, you will need to click on Refresh for it to appear here.

Once you create your custom fields, you can click out of the pane, as the initial setup of your Drip integration within THIS AEvent timeline is now complete!

Creating a Timeline Action to Add (or Remove) a Drip Tag

Setting up a timeline action to Add or Remove a tag from a contact within Drip is Easy.

Within the timeline builder, start by creating an action and selecting the date and time that you wish the action to occur. Select the audience you are targeting, then select your Drip Integration, and Add (or remove) Tag.

Then, enter the desired tag name to use. (DO keep a note of what you used for your reactive campaign within Drip).

Once you've created or selected the tag in which you want to add, just click on Create.

Your Add Tag (or Remove) Action has now been created, and you can view it on your timeline. Per the example above, 15 minutes prior to the event starting, an action will occur that will add a tag to all registrants registered for the scheduled event.

Creating a Timeline Action to Add to (or Pause or Remove) from a Campaign

Setting up a timeline action to Add, Pause, or Remove From a Campaign is fairly easy.

Within the timeline builder, start by creating an action and selecting the date and time that you wish the action to occur. Select the audience you are targeting, then select your Drip Integration, and Add to Campaign (OR, Pause, OR Remove From).


If you have created the automation since your last integration refresh, you may need to refresh your integration before finding the newly created automation. (you can do this within Integration Drip Settings.

Once you've selected the Drip Campaign that you wish to Add To, Pause, Or Remove From, just click on Create.

Your Drip Campaign Action has now been created, and you can view it on your timeline. At the date/time you selected, the subscribers matching the audience you selected will now be added to this campaign.

Creating a Timeline Action to Start a Workflow (or Remove From Workflow)

In this example, we will add a registrant to a workflow 1 day after the event at 8:00 AM EST. The steps to Remove a registrant from a workflow are essentially the same as outlined below.

First, within the timeline builder, start by creating an action and selecting the date and time that you wish the action to occur. Select the audience you are targeting, then select your Drip Integration and Start Workflow.

After clicking on Create, your action will be created and viewable on your timeline.

When this action occurs, it will now add all registrants that match the Non-Attendee Audience to the AEvent Non-Attendee Workflow. Had I wanted to remove a registrant from a workflow, I would have just selected 'Remove from Workflow.'

Creating a Timeline Action to Delete a Subscriber

If you wish for an automation action to occur that will delete a certain audience at a certain time from your Drip account, these are the steps.

Within the timeline builder, start by creating an action and selecting the date and time that you wish the action to occur. Select the audience you are targeting, then select your Drip Integration and Delete Subscriber.

After clicking on Create, your action will be created and viewable on your timeline.

When this action occurs, it will delete all subscribers matching the audience selection from your Drip Account. DO NOTE: This does not remove the registrants from your AEvent account.

Using AEvent Custom Fields as Personalization values inside your Emails

When registrant information is sent to Drip on registration, any custom fields that you have set up will be sent along as 'Personalized Content' or 'Personalization Tags.' You can use these dynamic tags to not only populate the normal fields like First Name, but you can also use Join URL, Replay URL, Day of Webinar, Time of Webinar, etc.

Below, we are in the Drip email editor, and here, using the Personalize Option, we can search out all of the fields that are being sent at the time of Registration.

You can also use these values within your email editor as hyperlinks (Join US button). If you click on Insert, Drip will paste into your email editor the short-code (the example above would be {{ subscriber.joinURL }}).

Then, we can highlight a word within the email editor and paste

{{ subscriber.joinURL }} as the Web Address.

Clicking insert creates an HTML link for the Join Us HERE text in our email. Now when someone clicks the link, it's their join link, and will take them into the event!

How to reconnect your Drip Integration

If you are encountering issues with your Drip integration, it is possible that the API key issued from Drip has been reset or changed. If you click 'Test' and it is NOT successful, the first step we recommend is reconnecting your integration.

By clicking Re-Connect, you will be prompted to Login to Drip and Authorize App.

Once reauthorized, your integration will show as Connected, and you will be able to click on 'Test'.

A successful connection will yield a positive test result. Congratulations, your Drip account is now successfully Re-connected to AEvent!

How to remove your Drip Integration from AEvent

If you want to remove your Drip integration from AEvent, you need to navigate to Integrations, locate your Drip integration, and click on the trashcan icon.

You then will be prompted to confirm deletion.

(NOTE: Removing this integration will immediately affect its use with any timelines 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 it's configuration to

continue as set within your timelines.

Once you confirm removal, the integration within AEvent no longer exists.


Did this answer your question?