Omnisend
How to connect Omnisend and Churn Solution:
You can connect your Churn Solution account with your Omnisend store through our Integration Page. Once connected, every cancellation session is exported to Omnisend as a custom event on the matching contact.
Once you click Connect Omnisend, you'll be prompted to authorize Churn Solution to access your Omnisend account.
Churn Solution can now create and update events on your Omnisend contacts. No code or tag installation is required on your side.
Sync Settings
After connecting, you can choose how your customers are matched to Omnisend contacts, and what the event is called on their timeline.
- Identifier type: how Churn Solution finds the right contact in Omnisend. We sync it on the Email to match your customer's email address to an existing Omnisend contact.
- Event name: the label that appears on the contact's timeline and in your Omnisend automation triggers. The default is Cancellation Session Completed, and you can rename it to anything that fits your naming conventions.
Click Save Settings to apply your changes. New settings apply to all sessions exported after saving.
Cancellation Session Events
Whenever one of your customers goes through your cancellation flow, Churn Solution sends the completed session to Omnisend as a custom event on the matched contact. You can open any event on the contact timeline to view the full details:
The properties of each event depend on how the session ended. Below are some examples of possible outcomes.
Coupon accepted
{
"accepted_offer": "COUPON",
"cancel_reason": "Budget",
"flow_name": "test",
"offers_shown": "PAUSE;COUPON",
"outcome": "COUPON",
"plan": "$100.0/year",
"session_id": "3000854",
"subscription_id": "sub_1UA5PRCKwqHtcT31jtNErQna",
"subscription_status": "ACTIVE"
}
Abandoned
{
"cancel_reason": "No Longer Needed",
"flow_name": "Primary Cancellation",
"offers_shown": "PAUSE",
"outcome": "ABANDONED",
"plan": "$900.0/month",
"session_id": "3175439",
"subscription_id": "sub_1UBWHmA9K5AU7MO2RasT2wtv",
"subscription_status": "TRIALING"
}
Cancelled
{
"cancel_reason": "Technical Issues",
"flow_name": "test",
"offers_shown": "PAUSE",
"outcome": "CANCELLED",
"plan": "$100.0/3 month",
"session_id": "3000868",
"subscription_id": "sub_1UA5PRCKwqHtcT31jtNErQna",
"subscription_status": "ACTIVE"
}
Event Properties
| Property | Description |
|---|---|
accepted_offer |
The offer the customer accepted:
PAUSE,
COUPON,
TRIAL_EXTENSION,
PLAN_SWITCH,
PLAN_SWITCH_WITH_COUPON,
CONTACT, or
SEND_TO_PAGE. Not included when
the customer cancelled or abandoned the session.
|
cancel_reason |
The reason the customer selected in your exit survey, for
example
Budget,
No Longer Needed, or
Technical Issues. Not included
when no reason was submitted.
|
flow_name |
The name of the cancellation flow the customer went through. |
offers_shown |
All offers presented during the session, separated by a
semicolon, for example
PAUSE;COUPON;TRIAL_EXTENSION.
|
outcome |
How the session ended:
PAUSE,
COUPON,
TRIAL_EXTENSION,
SWITCH_PLAN,
SWITCH_PLAN_WITH_COUPON,
CONTACT,
SEND_TO_PAGE,
CANCELLED, or
ABANDONED.
|
plan |
The customer's plan and billing interval at the time of the
session, for example
$100.0/year.
|
session_id |
The unique Churn Solution ID of the cancellation session. |
subscription_id |
The subscription ID from your payment gateway. |
subscription_status |
The subscription status at the time of the session, for example
ACTIVE or
TRIALING.
|
Because each session lands on the contact timeline as a custom event with its own properties, you can use it anywhere in Omnisend:
-
Trigger an automation when the event is received, and branch on
outcometo send a different message to saved and cancelled customers. -
Build segments from event properties, such as everyone whose
cancel_reasonis a specific value, or everyone who paused instead of cancelling. - Personalize your emails and SMS with the plan, offer, or reason from the session.
- Feed cancelled customers into your win-back campaigns automatically, without exporting lists by hand.