Customer.io
Last updated
Last updated
© Purchasely 2020-2023
The minimal version of the Purchasely SDK supporting this integration is //TODO: Kevin. If the Purchasely SDK integrated in your app is under the minimal version, please update it.
The Customer.io SDK also needs to be integrated inside the app.
Customer.io is a leading is an automated messaging platform for tech-savvy marketers who want more control and flexibility to craft and send data-driven emails, push notifications, in-app messages, and SMS.
This integration will allow you to get all the available Purchasely events to Customer.io and get a better and deeper understanding of your subscription business and customer behavior.
Purchasely provides a unified dataset to track the subscription events for all stores. These events are generated by the Purchasely Backend and can be sent to Customer.io.
Subscription events generated by Purchasely will be sent to Customer.io using a server-to-server integration. As a result, you will be able to see all the subscription events in your Customer.io Dashboard and map them with your acquisition campaigns.
The following events are the main ones that can be sent to Customer.io by Purchasely. See the full list here.
| Event | Description |
|---|---|
SUBSCRIPTION_STARTED | Sent when the user purchased a product wether it is the start of a trial or a regular purchase of a consumable product. |
SUBSCRIPTION_RENEWED | Sent when a subscription renews |
SUBSCRIPTION_EXPIRED | Sent when the subscription actually ends |
SUBSCRIPTION_REACTIVATED | Sent when an expired subscription is reactivated. This event is particularly useful for win-back & retargeting campaigns |
SUBSCRIPTION_REFUNDED_REVOKED | Sent when the subscription actually ends |
RENEWAL_DISABLED | Sent when the user deactivates the renewal of a subscription wether it is in trial period or not. |
RENEWAL_ENABLED | Sent when the user reactivates |
TRIAL_STARTED | Sent when a trial starts |
TRIAL_CONVERTED | Sent when a user converts from a free trial to a normal paid-period |
TRIAL_NOT_CONVERTED | Sent when a user finishes it's trial period without renewing to a paid-period |
The names of events sent to Customer.io can be overriden when setting up the integration.
The integration requires ${integration_setup_steps_count} steps:
Associate the user to events by providing the ${integration_sdk_property} to the Purchasely SDK
Activate the Customer.io integration in the Purchasely Console
See the Customer.io Documentation for more information
The activation requires 3 steps:
Retrieving your Customer.io Tracking API Key and Site ID from Customer.io's dashboard
Retrieving your Customer.io Reigon from Customer.io's dashboard
Enabling the Customer.io integration in the Purchasely Console
If necessary, create a new Tracking API key for your app
Write down your API Key and Site ID
Write down your Region
Go in the "External integrations" section, and open the edition form for Customer.io:
2. Enable the integration
3. Set your Customer.io API Key
4. Set your Customer.io Site ID
5. Set your Customer.io Region
6. Enable the events you want to be sent to Customer.io
7. (Optional) Override the names of the events that will be sent to Customer.io
8. Enable the user properties you want to be updated in Customer.io
9. (Optional) Override the names of the events that will be sent to Customer.io
10. Save
To test your integration, you can perform a set of in-app purchases in a Sandbox environment (eg: TestFlight for the App Store) and verify your events are received in the Customer.io dashboard ${integration_dashboard_signin_url}.
Please bear in mind that Customer.io's free plan doesn't offer API access.
