You can use Custom events to trigger custom automation workflows through the API. Every custom event can have a list of custom fields for any additional information that could be used in the Automation workflow content.
In this article, we'll explore how to effectively use Custom Events to optimize your marketing strategies and leverage additional data.
Before You Begin
When you integrate your store with Omnisend, we get a set of standard events, including subscribed to marketing, placed order, abandoned cart, etc. If you wish to set up the workflow for a different type of event, a Custom Event should be created.
Custom Events can be added to your account after integrating Omnisend with the 3rd party application or created manually. Some examples of Custom Events created by 3rd party apps include:
AfterShip Info Received — triggering the workflow when the order is shipped. Custom fields include the tracking number and tracking URL.
Intercom Review Created — triggering the workflow when the contact leaves a comment for the support agent's assistance. Custom fields include the rating and review content.
growave-wishlist-back-in-stock — triggering the workflow when the product added to the client's wish list is back in stock. Custom fields include information about the product.
Junip - Review Created — triggering the workflow when a new order is placed in your store. Custom fields include information about the product and the link to the review submission page.
Setup Process
For the Custom event to start working, you will need to add it to your Omnisend account and set it up on the third-party side.
Creating a Custom Event in Omnisend
To start Custom Events setup from the account side, go to Store Settings → Custom events:
1. Navigate to Store Settings → API → Custom events. Click "Create custom event" to get started.
2. You'll be redirected to the API documentation to complete the action. Here, you can create custom events but cannot add custom fields.
3. Copy the API Key from your Store Settings and add it to the Header field.
4. Follow the Body Params wizard and click "Try it."
5. Once created, you'll find the custom event added to the Custom Events tab.
Useful Information
To edit a custom event, delete the current event and create a new one through the API documentation.
Disabling a custom event will stop it from functioning, and any automations with this event as a trigger will be discontinued.
Re-enabling a custom event does not automatically turn on the previously disabled sequence; you must re-enable the workflow manually.
We strongly advise seeking assistance from your developer if you haven't worked with APIs before to set up custom events.
While API docs can help you comprehend the API's functionalities, it is recommended that you seek the assistance of a developer for implementing integrations. By providing the developer with the API documentation, they can understand how to connect to the system effectively. In essence, API docs serve as a guide for developers to establish a connection between third-party applications and the Omnisend API.
Custom Field Details
When adding custom fields to your Custom Event, consider the following:
Custom Field Name: This name is for your account's reference and can be adjusted later.
Custom Field System Name: The system name used when passing data through the API, which cannot be adjusted later.
Custom Field Type: Specifies how data should be interpreted. Choose from field types such as Integer, Float, Boolean, String, Email, URL, Date, and DateTime.
Custom Field is Required: Choose whether this field is essential and should be passed through the API each time.
Custom Field Types
Integer - should be used to pass number values only.
Float - should be used for numbers with a floating point.
Boolean - should be used for true or false values.
String - should be used to pass any string of characters that should only be used as values and not for calculations.
Email - should be used to pass an additional email address. If you don't need a second email address, you don't need to use this field.
URL - should be used to pass links.
Date - should be used to pass date information.
DateTime - should be used to pass time information.
We'd like to encourage you to consult with your website developer or refer to the 3rd party integration to define the appropriate data format.
API setup
Once the account setup is complete, proceed with the API setup. Refer to the API documentation for instructions on creating your custom event.
If Omnisend is integrated with a third-party platform, the custom event will be created automatically, or you can find instructions in the integration guide.
Custom Events in Automations
To create a custom event, go to the Automation tab → click Create workflow → Create from scratch.
The custom events you created can be found in the Automation workflow trigger, along with other standard options.
Once you add the custom event to the Automation trigger, all other settings (Trigger filter, Split block, Personalization menu, etc.) will be populated with the information this event carries.
You can also add this information to the message content (Email, SMS, Push Notification).
You may make your content even more interactive in the email message by adding the tracking link to the button, for example.
Unsubscribing from Custom events
If you are using a custom event for the automation workflow triggering, the footer content block will contain an unsubscribe link for your customers. We encourage you to add this link to all messages, but it is not obligatory if you send a transactional message with information about the order the customer placed.
Note: Automation workflows based on custom events will send messages to unsubscribed contacts. If you don't want to send messages to unsubscribed, make sure to change the Workflow Channel Settings by clicking on the trigger block.
By utilizing additional data through custom fields, you can optimize your marketing efforts and deliver targeted messages to your audience.
For further assistance with custom events, don't hesitate to reach out to [email protected].