How to send transactional messages
Automate transactional messages for timely and relevant user communication
Last updated
Automate transactional messages for timely and relevant user communication
Last updated
Transactional messages, such as order confirmations, subscription renewals, password resets, shipping updates, or payment notifications, are essential for providing users with timely, relevant information based on specific actions. Pushwoosh allows you to automate these messages using the Customer Journey Builder tool.
Before setting up transactional messages, ensure that:
The Pushwoosh SDK is integrated into your mobile app or website.
The events you want to use in transactional campaigns are created, set up, and tracked. Learn more about creating events
Below are examples of common transactional messages and the steps to configure them using Customer Journey Builder.
To automatically send personalized order confirmation messages when a purchase event occurs, follow these steps:
In your Pushwoosh account, go to Campaigns > Customer Journey Builder and click Create campaign to start building the transactional message flow.
In the Customer Journey Builder, add the Trigger-based entry element to the canvas and select the PW_InAppPurchase event (a default event). Ensure the event is properly configured. Learn more
If a custom event is required for your app, create and set it up in advance. Learn more about creating events.
Add a push notification element to the canvas. Create the message content, and use placeholders like {{order_id}} to personalize the message.
Title: "Order Confirmation"
Message: "Thank you for your order #{{order_id}}! Your items will be shipped shortly."
To make sure that the message is delivered regardless of any message limits, select Ignore Global frequency capping in the message settings.
Finalize and launch the Journey. Configure the message, and any optional segmentation or wait steps. Add the Exit element and click Launch to start the journey. The transactional message will now be sent automatically when the trigger conditions are met.
By using third-party subscription management services such as Adapty, Apphud, etc., you can automatically send renewal notifications or emails to users when their subscription expires, prompting them to renew. For this, do the following:
First, configure the integration of the service with Pushwoosh. Learn more about available integrations
Next, set up the Subscription_expired event in your chosen subscription management service. When a user's subscription expires, the service will send a Subscription_expired event to Pushwoosh.
Once you’ve set up the event, in the Customer Journey Builder, click Create campaign and add the Trigger-based entry element to the canvas.
Select the Subscription_expired event sent from the third-party service.
Add the email element to the canvas and select the email content you’ve created in advance.
Subject: "Your subscription has expired – renew now to stay connected!"
Body:
Hi,
We noticed that your subscription has expired, and we don’t want you to miss out on all the great benefits! Renew your subscription today to continue enjoying uninterrupted access to our services.
[Renew My Subscription]
Thank you for being a valued customer. We look forward to having you back!
Best,
To make sure that is delivered regardless of any message limits, select Ignore Global frequency capping in the message settings.
Complete the Journey configuration and click Launch campaign. Once launched, the subscription renewal notifications will be sent automatically when Subscription_expired event is triggered by the third-party service.
To send a password reset email, you’ll need to set up the password reset event, configure the password reset link on your end, and then build a Customer Journey to send the email.
Follow the steps below to complete the setup:
When a user requests a password change, you trigger an event, such as password change requested. You need to set up this event in advance.
Navigate to Events in Pushwoosh and click Create event.
Name the event, for example, Password reset request.
Add the following attributes to the event:
| Attribute name | Type | Description | Example value |
|---|---|---|---|
reset_link | String | The unique password reset link. | https://yourapp.com/reset-password?token=abc |
user_name | String | The user’s name for personalization. | John |
token_durability | Integer | Token validity in seconds (e.g., 24 hours). | 86400 |
date | Date | The date and time of the reset request. | 2024-11-18T10:00:00Z |
These attributes act as placeholders, receiving dynamic data from your system when the event is triggered.
In the attributes of the event, you must pass a unique password reset link that you generate on your side, or a unique key that needs to be included in the link for it to work. This link must contain a unique token that is personalized for each user and embedded in the URL through an event attribute sent from your system. The token should have an expiration period (e.g., 24 hours) to ensure security, allowing users to reset their password only within the specified timeframe.
Make sure to set up the event in your app. Learn more about setting up custom events
When a user requests a password reset (e.g., by clicking "Forgot Password"), you’ll need to:
Generate a secure, randomly generated unique token for the user. For example, 12345-abcde-67890.
Combine the token with your password reset URL. For example, https://yourapp.com/reset-password?token=12345-abcde-67890.
Save the token in your database, linked to the user's account, and set an expiration time (e.g., 24 hours).
Include the reset link in the reset_link event attribute when triggering the Password reset request event.
Navigate to Email content in Pushwoosh and create new email content.
Add placeholders for dynamic content:
{{reset_link}} for the password reset link.
{{user_name}} for the user’s name.
{{token_durability}} for the link expiration time.
Learn more about creating email content
Navigate to the Customer Journey section in Pushwoosh and click Create campaign.
Drag and drop a Trigger-based entry element onto the canvas. Select the Password reset request event.
Add an email element to the canvas and link it to the Trigger-based entry element.
Select the previously created email content with placeholders for the reset link and user details.
To make sure that is delivered regardless of any message limits, select Ignore Global frequency capping in the message settings.
After adding the message content, ensure all steps in the journey are configured correctly. Add the Exit element and click Launch campaign to start the journey.
Once the campaign is activated, the password reset message will automatically be sent when a user requests to reset their password, providing a seamless and secure experience.
