Skip to content
AppDues
Log in
Contact salesSign up

Send a trial cancellation survey email without server code

When someone leaves during a free trial, a short feedback request can reveal why conversion stalled. This guide shows a no-server-code workflow: store contact and personalization attributes in the app, listen for cancellation webhooks in an automation tool, filter to genuine trial unsubscribes, send a survey link, and optionally record that the survey was sent.

Why ask at trial cancellation?

Feedback collected at the moment of cancellation is more useful than a later generic survey because the reason is still fresh. The workflow in this guide is deliberately narrow: it targets people who unsubscribe during a free trial, not every cancellation. That focus helps you look for trial-specific friction, such as onboarding confusion, pricing surprise, or a feature gap, rather than mixing in billing failures.

1. Save contact and personalization attributes

Start inside the app. If email is already used for sign-in, store it as a subscriber attribute using protected module code0001. Also store one useful personalization detail, for example a favourite workout captured during onboarding, using protected module code0002. That extra attribute lets you tailor the subject line, which can make the message feel like a personal note rather than a bulk blast. If your app does not collect email, adapt the same pattern to phone numbers or push notifications, as long as the channel is saved as an attribute first.

2. Connect webhooks to the automation tool

Create a new automation with a webhook catch-hook trigger. The automation tool will give you a custom webhook URL. Paste that URL into the subscription dashboard's webhook settings, then use the dashboard's test-event option to confirm events arrive. The authorization header value is optional for this listening step and is omitted in this simplified setup.

3. Filter to genuine trial unsubscribes

Once connected, every subscription status event will flow into the automation, so add a filter step before any email is sent. Use the four conditions in the table below. The key distinction is between an unsubscribe and a billing problem: the former gets a feedback survey, while the latter may need a card-update reminder instead. Also require a stored email attribute, otherwise the send step has nowhere to deliver the message.

4. Send a short, personalized survey email

After filtering, send the message. The recipient field should use the stored email attribute. Personalize the subject with the saved favourite-workout attribute. Keep the body plain and short, with a clear survey link, so it reads like a personal note. Responses can be collected in a form tool that writes answers to a spreadsheet and notifies you per response. For higher volume, an external email provider can replace the automation tool's built-in email app.

5. Optional: record that the survey was sent

For measurement, add an optional tracking step after the email. Post to the subscriber attributes endpoint, using the app user ID from the original webhook event, with protected module code0003 defining the payload. Set the payload type to JSON, use the automation tool's timestamp variable as the value, and authenticate with a Bearer API key plus a JSON content-type header. The flattened field format is attributes__cancel_survey_sent__value with the timestamp variable as its value. Once enabled, you can later check the dashboard, API, or webhook data to see who received the survey.

Pre-launch checklist

Before enabling, run this checklist: email is saved in the app, the personalization attribute is saved, the webhook test event arrives, all four filters pass only for trial unsubscribes, billing cancellations are excluded, the survey link opens, and the optional sent-timestamp attribute appears for a test user. The same attribute pattern can later be reused at other lifecycle moments, such as after purchase or before renewal.

Webhook filter conditions for the cancellation survey
Filter conditionValue to requireWhy it matters
Event Period TypeTRIALLimits the survey to free-trial cancellations, where conversion insight is the goal.
Event TypeCANCELLATIONEnsures the survey follows an actual cancellation.
Event Cancel ReasonUNSUBSCRIBEExcludes billing issues, which may need a payment reminder instead.
Email attribute existsPresentPrevents failed sends when no address was stored.

Apply all four conditions together; do not send on cancellation alone.

Frequently asked questions

What must be captured in the app before a cancellation email can work?

Save the address as a subscriber attribute inside the app, using the protected email-saving module code0001. Without a stored address, the later filter cannot send the message.

Which cancellations should trigger the survey?

Only trial-period cancellations where the reason is an unsubscribe and an email attribute exists. Billing-related cancellations are excluded so they can receive a payment-update reminder instead.

Can you record who received the survey?

Yes, optionally. After sending, post a timestamped attribute through the REST API using protected module code0003, so you can later identify who received the survey in the dashboard, API, or webhook data.

What if the app does not collect email addresses?

If no email is collected, the same pattern can be adapted to phone numbers or push notifications, provided that contact channel is stored as an attribute first.

{
	"attributes" : {
		"cancel_survey_sent" : {
			"value" : {{zap_meta_timestamp}} 
		}
	}
}