SmartEmailing webhook

This article gives you knowledge of how webhooks send information from SmartEmailing to Meiro Events.

 

Requirements

You need to follow these key requirements to properly set up the webhook:

1. Username and Password/API token from the account in the partner’s app/website is needed for setup and data collection.

2. Have an external partner’s API endpoint URL

3. The Meiro Events database must be set up for data storage.

 

Learn more about: how to set SmartEmailing webhook in Meiro  

Feature

In SmartEmailing webhook, both the URL address and the message sent are fully customizable. You can set template scripts, attach your own Content-Type, add any headers to the request and HTTP Basic authentication, and use the dynamic fields.

 

​​In SmartEmailing a webhook can contain all available data you store, including e-mail, phone number, name, etc.

 

Besides, ​​in SmartEmailing you can set one trigger to be followed by other triggers.

 

Examples of events in SmartEmailing include:

• Campaign open

• Link click

• Date field (e.g. Birthday field)

• Autoresponder has been sent

• Fixed date

• New contact is created in the database by the webform (and the contact wasn't there before)

• Contact clicks more than a certain number of links in the email

• Contact has been added

 

Examples of actions to perform within events:

• Add contact to another contact list

• Remove contact from the contact list

• Send email campaign

• Move contact between lists

• Send SMS message

 

Example data

Endpoint: Trigger event

This method is used for bulk firing events in automation scenarios:

 

Use cases

Here are practical use cases on how to generate SmartEmailing webhooks with the Meiro Events: 

• Sending a series of welcome emails from Meiro to every new user added to CDP. They can guide them through on how to use the platform as well as any product newsletters that might be blasted out from the product team.

• Sending a POST request when a contact opens your campaign or clicks at a particular link in your campaign. It does not matter if it is sent as a newsletter or set as an autoresponder or even if the campaign is sent by the trigger.

• Sending an automated email notifying a user of the status of an order. For example, once clients land on the “thank you for your order page”, this can be triggered to send them automated emails with their names, items bought, used method of payment, date when a package arrives, etc. Another trigger may finish the email sending when the status of the order is completed.

• Sending an automated message to a customer, who started the checkout process, but left without finishing. Emails can remind your customers that there is an abandoned basket waiting for them. 

• Sending a birthday campaign to your customers and giving them some reward as a gift.