Retention email template

Data export check-in email

When a user exports their data it's sometimes routine reporting and sometimes the first step toward leaving. A light check-in email offers help without assuming the worst.

Trigger type

Event-based, sent the moment it happens

How often

Each time it happens

The email template

This is the starter email Atlis fills in when you add the Data Exported trigger.

Subject

Your {{productName}} export is ready to use

Hi {{displayName}},

We noticed you exported your data from {{productName}}. We hope it has everything you need.

If you were looking for something we don't offer yet, or if anything is frustrating you, reply to this email. We'd genuinely like to know.

Back to {{productName}}

Best,
The {{productName}} team

Variables like {{displayName}} are filled in for each person. {{ctaLink}} is your App URL.

When it sends in Atlis

You track data_exported.

Goal: Catch a possible churn signal early and offer help.

Tips for this email

  • Don't accuse. Assume the export was for a good reason and offer help with it.
  • Mention reporting or integration features that might remove the need to export.
  • Watch for exports followed by a cancellation-page visit. That combination is a strong risk signal.

Send it automatically in three steps

  1. 1

    Connect your app

    Install the Atlis snippet or send users and events with the Server API.

  2. 2

    Add the Data Exported trigger

    In Workflows, add the Data Exported trigger. The email below is filled in for you.

  3. 3

    Edit and switch it on

    Adjust the wording, optionally add up to 4 follow-ups, and switch the workflow on.

Start free 14-day trial with Growth features, then a free plan for up to 250 tracked users.

Questions

How do I track exports?

Track data_exported from your app when an export finishes. Atlis also counts it as a churn signal when working out who needs attention.

Will users get it every time?

It can send each time the event arrives. If you only want some exports, send a custom event name for those and use a custom trigger.