Document toolboxDocument toolbox

Post Purchase Email

Summary / TL:DR: This article will introduce you to Post Purchase emails purchase in Blueshift.

3 min read


Table of contents


Capability

Send an email to a customer when their credit card has been charged for an order.


Description

When a customer's credit card has been charged for an order, the charge information is sent to Decisions. The Decisions workflow captures the update and generates an event to inform Blueshift about the action. This event then triggers a campaign in Blueshift.


Blueshift Event Name

post_purchase


Event Payload Parameters

Parameter

Description

Parameter

Description

event

Name of triggering event

owning_org

Code for the legal entity associated with this transaction

email

Email address of the billTo customer

customer_firstname

First name of the billTo customer

customer_lastname

Last name of the billTo customer

retailer_customer_id

Concatenation of [Advantage billTo customer number]-[Advantage billTo emailId]

transaction_number

Unique identifier for this transaction

payment_type

The type of payment used for this transaction.

cc_last_digit

Last four digits of credit card number used for transaction

order_number

Unique identifier of the order in the system

currency

Currency type associated with the transaction

charge_date

Date charge for transaction was processed

charge_amount

Total amount of transaction

line_item

List of items included in product order

item_quantity

Description of stock item

item_code

Inventory item number used to identify the item (publication or product etc.)

item_description

Description of purchased item


Sample Payload

 

{ "event":"post_purchase", "owning_org":"304", "email":"email@14west.us", "customer_firstname":"SEJAL", "customer_lastname":"PATEL", "retailer_customer_id":"000106061830-000089668824", "transaction_number":"819905568277133885", "payment_type":"Mastercard", "order_number":"SK127597", "cc_last_digit":"1564", "currency":"US$", "charge_date":"2020-09-01", "charge_amount":"89.00", "line_item": [ { "item_quantity":1, "item_code":"MMR", "item_description":"Money Map Report" }, { "item_quantity":2, "item_code":"MMR", "item_description":"Money Map Report" } ] }

Setting up a Campaign

  1. Create an event triggered campaign using the event ‘post_purchase’.

  2. Set the condition “Skip Global Inclusion Segment Check” to “Yes”.

  3. Select the associated template for your campaign. A sample email called ' FOR_COPY_SAMPLE_post_purchase Confirmation test'  is available in your Blueshift Production instance.


Reporting

The event name in the payload will be passed in the mailing activity events. This will be available in the reporting platform for filters.


Things to Consider When Planning your Migration and/or Setup

  1. Please follow the Transition Guidelines shared by the MarTech team during your Migration Planning workshop.

  2. 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.

  3. 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.

  4. 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 Post Purchase emails purchase in Blueshift.

Still need help?

We know this can be frustrating. To get further help please open a Support ticket.

Click here to open a ticket


Related Content


Level up with a Masterclass

Evolve course title

Get started!

Evolve course title

Get started!


 

com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'html-macro' is unknown.