Purchasely can send all your transactional events to Braze to enrich your users data. Use these events to trigger automatic campaigns, pushs...
The following events will be sent. You can set the event name of your choice in the console.
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 the user deactivates the renewal of a subscription wether it is in trial period or not.
Sent when the user reactivates
Sent when the subscription actually ends
Sent when a subscription renews
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
There is nothing special to be done to associate Purchasely events to your logged in users in Braze. Just setup Braze SDK as you would normally, and use the
changeUser method to set the user ID in Braze:
[[Appboy sharedInstance] changeUser:@"YOUR_USER_ID"];
If you have anonymous users in your app, you will need to add their Purchasely
anonymous_id as a user alias to Braze:
[[Appboy sharedInstance].user addAlias:[Purchasely anonymousUserId] withLabel:@"purchasely_anonymous_id"];
When the anonymous user later becomes logged in, Purchasely will automatically send following events using the provided
Go to the "External integrations" section, and open the edition form for Braze:
Go to your Braze Developer Console, and click on "Create New API Key"
Give a relevant name to your API Key. In the "User Data" permission area, check
users.track as our servers need this permission to report backend events to Braze.
Click "Save API Key" at the bottom of the page.
Finally, paste the API key Identifier value into Purchasely console.
Refer to Braze API Endpoints table. You can use your Braze Dashboard URL find the correct server. E.g. if your dashboard is accessible at https://dashboard-01.braze.eu, then you should select the
If you want to, you can rename events sent to Braze:
Each event sent to Braze carries a set of properties that you can use to further personalize your campaigns:
Name of the application as set in Purchasely Console, e.g.
Application package ID in the Store, e.g.
Platform of the application, e.g.
Plan Vendor ID, e.g.
Plan name as set in Purchasely Console, e.g.
Store product identifier, e.g.
Type of the plan, e.g.
Product Vendor ID, e.g.
Product name as set in Purchasely Console, e.g.
Store associated with the event, e.g.