The minimal version of the Purchasely SDK supporting this integration is v3.2.0. If the Purchasely SDK integrated in your app is under the minimal version, please update it.
The OneSignal SDK also needs to be integrated inside the app.
OneSignal is one of the leading customer engagement solutions for Push Notifications, Email, SMS & In-App.
This integration will allow you to get all Purchasely subscription events to OneSignal making you able to trigger automated communication based on those events, messages that could be linked to a Purchasely powered paywall to engage, upsell, retain customers.
Purchasely provides a unified dataset to track the subscription events for all stores. These events are generated by the Purchasely Backend and your OneSignal users' can be updated accordingly.
Subscription events generated by Purchasely will be sent to OneSignal using a server-to-server integration. As a result, you will be able to see all the subscription events in your OneSignal Dashboard and map them with your acquisition campaigns.
The following events are the main ones that will trigger an udpate of your OneSignal users by Purchasely. See the full list here.
Sent when the user purchased a product wether it is the start of a trial or a regular purchase of a consumable product.
Sent when a subscription renews
Sent when the subscription actually ends
Sent when an expired subscription is reactivated. This event is particularly useful for win-back & retargeting campaigns
Sent when the subscription actually ends
Sent when the user deactivates the renewal of a subscription wether it is in trial period or not.
Sent when the user reactivates
Sent when a trial starts
Sent when a user converts from a free trial to a normal paid-period
Sent when a user finishes it's trial period without renewing to a paid-period
The following properties are the main ones this integration can set and update in your OneSignal users as tags:
Contains the user_id that holds the purchase.
Contains the Plan id that was bought.
Filled for events that regards a subscription.
Possible Values :
Contains the name of the Store through which the purchase was made.
Contains the store country where the purchase was made.
Contains the date of the last transaction (original purchase or renewal).
Contains the next automatic renewal date**.**
Contains the current offer the subscription is under.
NONE: the user is paying the normal price, no offer associated
Contains the date when the grace period will end.
Name of the last event received for that subscription
Contains true or false depending on if the user has access to the subscription thanks to family sharing.
Contains the promo code used at the time of the purchase.
Contains the date of the first transaction.
The properties' names set in OneSignal can be overriden when setting up the integration.
Integrating Purchasely with OneSignal
The integration requires 2 steps:
Associate the user to events by providing the OneSignal Player ID to the Purchasely SDK
Activate the OneSignal integration in the Purchasely Console
5. Your app’s app id is beneath the OneSignal App ID title
6. Your app's API key is beneath the Rest API Key title
b. Enabling the OneSignal integration in the Purchasely Console
Go in the "External integrations" section, and open the edition form for OneSignal:
2. Enable the integration
3. Set your OneSignal app id
4. Set your OneSignal app API key
5. Enable the properties you want to be set and updated as OneSignal tags for your users
6. (Optional) Override the property names that will be used when updating your users' OneSignal tags
Testing your integration
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 user's tags are properly updated in the OneSignal dashboard (https://app.onesignal.com/login).
If testing using Automated Messages, bear in mind that OneSignal automated messages are sent roughly every 4-6 hours if you are on a free plan, and within a few minutes if you are on a paid plan.