...

The Marketing Email Subscribe event is sent to Blueshift from SignupApp2 when a customer succesfully signs up to a marketing list with their email address. The event has been enhanced to include includes the iris_campaign_name and camapaign_code. This which allows you to send Lead Gen Confirmation email via Blueshift instead of IRIS.

...

IRIS Configuration

...

There are 2 ways to avoid sending Lead Gen confirmation emails out of IRIS. Follow the steps below when creating new signup pages (1) or updating existing signup pages (2).

1. When creating new signup pages for a specific Lead Gen item, this creates a new version. In the version, do not create any confirmation emails.

   1. When creating an effort with this version, a confirmation email will not get filled out and will not get sent to the customer.

2. If you have current signup pages active that have a confirmation email in IRIS set on the effort and there is only one confirmation email set up for that version:

   1. Create a dummy confirmation email for that specific item and version.

   2. Go back to the effort in question and de-select the confirmation email so that it says “Select One”.

   3. Save effort

Info
Co-Reg Keep the 'Co-Reg Confirmation Email' drop-down unselected (see screenshot below)

...

Blueshift Campaign Setup

1. Create an Event Triggered campaign using the Marketing Email Subscribe event

2. Add your Email Trigger(s)

3. Use the following filters

   1. campaign_code

   2. iris_campaign_name

   3. duplicate_signup - Set this to false to avoid sending a confirmation email to users who are already signed up

Unsubs

In order for SUA2 unsubscribes to currently work, an advantage customer number must be present in the vid2 value but the marketing_email_subscribe event does not include it. As a workaround you can replace the vid2 value with the following:

{{ "000000000000" | append: '@@' | append: user_transaction.list_code | append: list_code | append: item_code | append: user_transaction.item_code | append:item_number | append: '@@' | append: user.email | aes256_encrypt_v2: '50655368566D597133743677397A24432646294A404E635266546A576E5A7234', '472B4B6250655368566D597133743677' }}

...

We are hardcoding a dummy advantage customer number which allows the unsubscribe to process. We will look to enhance this process so the default vid2 value can be used for event triggered emails.

...

...