Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Summary / TL:DR: This article will show you how custom and relevant campaign parameters are added to all links that are sent from Blueshift.


Custom Parameter

In the refactored instances of Blueshift a custom parameter will be added to all triggers and therefore all links that get sent out of Blueshift by default. 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

If you would like to add additional custom parameters please submit that request to Global Support.


How it Works

The vid2 variable is comprised of the advantage customer number, list code, email address and delimiters which are then AES-256 encrypted within a single liquid object.

This variable is then decrypted by 14West systems to be used in things such as reporting, unsubscribes, and order form auto-pop.

The decrypted value will look something like the following:

000123456789@@LISTCODE@@emailadress@14west.us


Blueshift Parameters

Blueshift will also automatically include link parameters relevant to the campaign itself. They are as follows:

Parameter

What is it?

bsft_clkid

Unique identifier generated when clicking a link

bsft_uid

Unique identifier assigned to the profile

bsft_mid

Unique message identifier

bsft_utid

Unique identifier assigned to the profile appended to the transaction list code

bsft_mime_type

Indicates the type non-ASCII components of a message

bsft_tv

Template version

bsft_eid

Unique identifier assigned per trigger

bsft_ek

Campaign execution timestamp

bsft_lx

Identifies the instance of the URL when the same URL is used in multiple locations in the template.

The last three parameters of bsft_eid, bsft_ek, and bsft_lx allow orders to be reported on 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 the vid2 custom parameters work and what other parameters are included in Blueshift links.

Still need help?

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

Click here to open a ticket


Cannot find the article you’re looking for?

Suggest a new article here!

  • No labels