Summary / TL:DR: This article will show you how list unsubscribes function in the refactored instance of Blueshift.
Trigger Level Custom Parameters
In the refactored instances of Blueshift a custom query parameter will be added to all links by default. This query parameter is defined at the trigger level and so it eliminates the need to manually add the necessary query parameters at the template level in order for list unsubscribes to work. Below shows the key-value pair:
key = vid2
value = {{ user_transaction.advantage_customer_number | append: '@@' | append: user_transaction.list_code | append: '@@' | append: user.email | aes256_encrypt_v2: '50655368566D597133743677397A24432646294A404E635266546A576E5A7234', '472B4B6250655368566D597133743677' }}
Blueshift Feature Documentation
Blueshift Parameters
Outside of the custom parameter that is defined above, Blueshift will also automatically include link parameters relevant to the campaign itself. They are as follows:
Parameter | What is it? |
|---|---|
bsft_eid | Unique identifier for the trigger |
bsft_ek | Campaign execution time |
bsft_lx | Identifies the instance of the URL when the same URL is used in multiple locations in the template. |
These parameters allow orders to be reported in Thoughtspot and so again, there is no need to manually add any query parameters to promotion links within the template
Wrap up
You should now know how list unsubscribes and promo links will work in the refactored instance of Blueshift.
Still need help?
We know this can be frustrating. To get further help please open a Support ticket.
Cannot find the article you’re looking for?
Suggest a new article here!