Blueshift Subscription Auto Renewal Email
Summary / TL:DR: This article will introduce you to Auto Renewal Emails for an Subscription in Blueshift.
3 min read
Table of contents
Capability
Send a notification email through Blueshift when a customer qualifies for a 30-day auto renewal notification.
Description
When a customer is due for the automatic renewal of a subscription, the order is updated in Advantage. Spine workflow captures the update and generates an event to inform Blueshift about the action. This event then triggers a campaign in Blueshift to send a notice to the customer informing about the charge to be expected on their payment method (credit card or Direct Debit).
Blueshift Event Name
subscription_renewal
Event Payload Parameters
Parameter | Description |
---|---|
billing_currency | Currency type associated with the transaction |
card_number | Credit card number used for subscription transaction |
card_type | Credit card type used for subscription transaction |
customer_firstname | First name of bill-to customer |
customer_lastname | Last name of bill-to customer |
Email address of bill-to customer | |
event | Name of triggering event |
issues_per_year | Number of times this magazine will be mailed in a calendar year |
last_renewal_date | Date the latest renewal notice was sent. |
next_rate | The amount the customer will be charged for the next term. |
next_term | The number of issues in the next term. |
publication_code | Code that identifies the publication |
publication_title | Title of the publication associated with the subscription |
renewal_key | The auto-generated promo code that writes to the customer’s account when the CIR340 process is run. |
renewalkey_end | Last four characters of the renewal key |
retailer_customer_id | Concatenation of [Advantage billTo customer number]-[Advantage billTo emailId] |
subscription_reference | A unique identifier for each subscription |
billing_currency | Currency type associated with the transaction |
card_number | Credit card number used for subscription transaction |
Sample Payload
{
"billing_currency": "us$”,
"card_number": "xxxxxxxxxxx3737",
"card_type": "Visa",
"retailer_customer_id": "000121314285-000089668829",
"customer_firstname": "Tim",
"customer_lastname": "Dodge",
"email": "email@14west.us",
"event": "subscription_renewal",
"last_renewal_date": "2020-01-01T05:00:00Z",
"next_rate": 25.00,
"next_term": 12,
"publication_title": "straight line profits",
"publication_code": "slp",
"renewal_key": "R15CMM1M",
“renewalkey_end”: “MM1M”,
“issues_per_year”: 8,
“subscription_reference”: “000051050605”
}
Setting up a Campaign
Create a triggered campaign using the event ‘subscription_renewal’.
Add a condition with renewalkey_end equal to value designated for your auto-renewal.
Set the condition “Skip Global Inclusion Segment Check” to “Yes”.
Select the associated template for your campaign.
If one campaign is used for setting up mailing for multiple publications, set the condition “User can be in the campaign journey” to “Multiple times concurrently”. This will allow you to send an email to a customer who cancels multiple subscriptions.
Reporting
The publication code in the payload is whitelisted to be passed in the mailing activity events. This will be available in the reporting platform as the list code. In addition, event name is also available to be filtered on.
Things to Consider When Planning your Migration and/or Setup
Please follow the Transition Guidelines shared by the MarTech team during your Migration Planning workshop.
If you have an existing Message Central Auto Delivery (BCL) Cancellation workflow on Advantage, your new Blueshift workflow has already been set up on Advantage and is ready to send events.
If you never had an Auto Delivery Cancellation workflow on Advantage, there is no longer a need to share the new campaign ID with the Advantage team during initial set up. The same event category can be used for multiple campaigns, segments, etc. without Advantage configuration support.
The Auto Delivery Cancellation workflow will account for all owning orgs associated with your Blueshift instance. Please note: additions of new owning orgs must be reported to the MarTech team so it can be added to your Blueshift instance.
Wrap up
You should now have a better understanding of Auto Renewal Emails for an Subscription in Blueshift.
Still need help?
We know this can be frustrating. To get further help please open a Support ticket.
Related Content
Level up with a Masterclass