Funnelish helps businesses create sales funnels and checkout experiences. Connect Funnelish to Omnisend to send purchase, checkout, and opt-in activity as custom events and use it in Automation Workflows.
Benefits
Track purchase activity in Omnisend.
Capture checkout attempts, including failed payments.
Send opt-in activity to Omnisend.
Use funnel and checkout data for segmentation and personalized marketing.
How It Works
Funnelish sends data to Omnisend through a webhook block in a Funnelish automation.
Each Funnelish trigger must use the matching Omnisend integration feature and webhook URL. For example, the On Purchase trigger must use the webhook URL generated for Funnelish – On Purchase.
Setup Process
Step 1. In Omnisend, go to Apps → search for Funnelish → click Connect now.
Enable the integration features you want to use:
Funnelish – On Purchase
Funnelish – Purchase Attempt
Funnelish – On Opt-in
Copy the unique webhook URL generated for each feature.
Step 2. In Funnelish, open the automation you want to connect and select the trigger you want to use.
The supported triggers are:
On purchase
Purchase attempt
On opt-in
Step 3. Add a Webhook block to the automation.
Paste the webhook URL that corresponds to the selected trigger:
Funnelish trigger | Omnisend integration feature |
On purchase | Funnelish – On Purchase |
Purchase attempt | Funnelish – Purchase Attempt |
On opt-in | Funnelish – On Opt-in |
Make sure each trigger uses the matching webhook URL. Save or publish the automation after adding the webhook block.
What Data Is Passed
Contact Fields
Funnelish can send the following contact fields to Omnisend:
Field name | Type | Description |
Standard field | The payer’s email address. Synced as non-subscriber | |
Phone | Standard field | The customer’s phone number. |
First Name | Standard field | The customer’s first name. |
Last Name | Standard field | The customer’s last name. |
City | Standard field | The customer’s city. |
Country | Standard field | The customer’s country. |
Postal Code | Standard field | The customer’s postal or ZIP code. |
State | Standard field | The customer’s state or region. |
Custom Events
Funnelish also sends the following custom events to Omnisend:
Custom Event Name | Description |
Funnelish – On Purchase | Triggered when the initial order is paid. |
Funnelish – Purchase Attempt | Triggered when checkout is submitted, even if payment fails. |
Funnelish – On Opt-in | Triggered when a contact submits an opt-in form. |
💬 Learn more: Create and Manage Custom Events in Omnisend.
FAQ
Where do I add the Omnisend webhook URL?
Add the URL to a Webhook block inside the relevant Funnelish automation.
Should each trigger use a different webhook URL?
Yes. Use the webhook URL that matches the selected Omnisend integration feature.
What is the difference between On Purchase and Purchase Attempt?
On Purchase triggers when the initial order is paid. Purchase Attempt triggers when checkout is submitted, even if payment fails.
What should I check if an event doesn’t arrive in Omnisend?
Check that:
The correct integration feature is enabled in Omnisend.
You copied the webhook URL for the matching feature.
The webhook URL was added to the correct Funnelish automation.
The automation is saved and published.
If the issue persists, uninstall and reinstall the integration.
Didn't find the answer to your question? Reach out to our Support team through the in-app chat or at [email protected] – our team is available 24/7.