...

Tracking Scripts

...

Since these events are firing from all promotion, order, and confirmation/cross-sell/upsell pages, we need a way to identify how all these events are related to the promotionpromo. In this example we are using an identifier within the URL that the journey name from the IRIS-WMC connection. This will be passed through the entire journey and will only match an event which contains that identifier journey name within the IRLURL.

In these types of campaigns we always select the option to Skip Global Inclusion Segment Check. The re-qualify period and time delay of the trigger can be determined by the client.

...

Blueshift’s preference center will be used to manage opt-ins and optouts from these abandon emails. Blueshift documentation on the preference center can be found here. One single form will be used in conjunction with a custom sp (sticky parameter) value that will be passed in the creative. For example the liquid script to be used for the unsubscribe link would look like {{ unsubscribe_link }}?sp=pub_abandon_optin. This link takes you to the preference center and depending on what the sp value is we can dynamically change out the logo and item name. When a customer chooses to no longer receive these emails a custom attribute will be written to their profile that would look like pub_abandon_optin=false. In the above campaigns you can see that users who have this flag set the to false are being filtered out. Customers that are currently opted out of these abandon emails from other systems will have to have this reflected in Blueshift by setting the relevant custom attribute on their profile to false.

...

...