update to brilliant set up

| No Action | default starting position for all records |  | No |

| Downloaded | Downloaded content | Yes | Yes |

#### Direct Mail

#### Direct Mail (Brilliant Optimized)

This is when a package or piece of mail is sent out. Current procedure requires use of Brilliant Gifts and Qualified. To utilize shipping program statuses and alerts, a Marketing team member must send an order form email out to the recipient via the Brilliant interface and change program statuses manually in either Marketo or SFDC. If the recipient is given the option to select their gift, use `Send a Gift -> Campaign or Quick Send` inside of Brilliant. If the gift is chosen by the Marketing or Sales team, utilize `Send a Gift -> Surprise Send`. The `Meeting Booked` status is updated via Qualified and `Meeting Attended` must be updated manually by Sales or Marketing after a successful meeting. `Meeting No Show` is to be updated by Sales/Sales Dev via a Qualified automated email

This is when a package or piece of mail is sent out. Current procedure requires use of Brilliant Gifts and Qualified. To utilize shipping program statuses and alerts, a Marketing team member must send an order form email out to the recipient via the Brilliant interface and change program statuses manually in either Marketo or SFDC. If the recipient is given the option to select their gift, use `Send a Gift -> Campaign or Quick Send` inside of Brilliant. If the gift is chosen by the Marketing or Sales team, utilize `Send a Gift -> Surprise Send`. The `Meeting Booked` status is updated via Qualified and `Meeting Attended` must be updated manually by Sales or Marketing after a successful meeting. `Meeting No Show` is to be updated by Sales/Sales Dev via a Qualified automated email. 

Brilliant can now sync shipping statuses over to Marketo and SFDC via program status updates but they will only work with [Direct_Mail_eGift_Global - Brilliant connected](https://experience.adobe.com/#/@gitlab/so:194-VVC-221/marketo-engage/classic/PG28387A1) and all Brilliant webhook calls **must** be made with the primary smart campaign: [Send to Brilliant webhook (do not alter)](https://experience.adobe.com/#/@gitlab/so:194-VVC-221/marketo-engage/classic/SC77009A1ZN19). Only this program and smart campaign can successfully call Brilliant. Note: there are a few statuses used by Brilliant within the program type that we do not necessarily use but those help track shipping statuses

**Bizible:** This is tracked as an _offline_ channel. Touchpoints for offline channels are created through our AMM (formerly known as Bizible) campaign sync rules that can be found in this [spreadsheet](https://docs.google.com/spreadsheets/d/1xR2Q7YKskfNaxclnfGOkK8Vi739zdKypQ6GgF9MLG58/edit#gid=92970564).

| Member Status | Definition | Success | Triggers gift webhook?|

| ------------- | ---------- | ------- | ------------ |

| No Action | Default starting position for all records |  |  |

| **Created** | | | |

| Nominated | Leads are added to the program with this status indicating they will receive a meeting invite |  |  |

| Invite Sent | Indicating an email invite for a meeting has been sent |  |  |

| Email Opened | Not currently utilized within the program type | | |

| Gift Accepted | Recipient filled out the gift request form | | |

| Gift Ordered | The gift has been manually ordered in Brilliant and program status manually changed to inform Sales | | |

| Gift Shipped | The gift has been shipped and program status manually changed to inform Sales | | |

| Gift Delivered | The gift has been delivered and program status manually changed to inform Sales | | |

| Clicked | Not currently utilized within the program type | | |

| **Gift Requested** | | | |

| Claimed | Recipient filled out the gift request form | | |

| **Pending** | | | |

| In Fulfillment | The gift has been ordered in Brilliant  | | |

| Partially Shipped <br> Externally Shipped <br> Shipped | The gift has been shipped and program status automatically changed by Brilliant to inform Sales | | |

| Out for Delivery <br> Partially Delivered <br> Delivered | The gift has been delivered and program status automatically changed by Brilliant to inform Sales | | |

| Meeting Booked | Recipient of meeting invite has scheduled a meeting via Qualified | Yes | |

| Meeting Attended | Recipient was not labeled as a No Show to the scheduled meeting | Yes | Yes |

|Cancelled | Person has cancelled prior to the scheduled meeting  | | |

### Step 1: Create the Marketo program and Salesforce campaign

- Clone the [#TEMPLATE - FY00_Q0_Brilliant Gifts Direct Mail TEMPLATE](https://experience.adobe.com/#/@gitlab/so:194-VVC-221/marketo-engage/classic/PG24060A1) into the appropriate folder and rename the program. If the intention is to run in ONE region, clone once. If the intention is to run in multiple regions, clone a "parent" program and enough programs for all regions (e.g. AMER, APJ, EMEA) and place in their own folder. Keep the naming convention similar for the regional/child programs but add a region tag at the end of the program name (e.g. `FY00_Q0_Campaign_AMER`). For the parent program, add `_Parent` to the end of the program name to prevent redundant Touchpoints on the SFDC campaign

- If one program was cloned, sync it to SFDC. If there were multiple programs created, sync them ALL of them to SFDC.

  - DO NOT anchor the regional SFDC campaigns under the parent campaign. The parent campaign is there to sync with Qualified, but once the campaign is _fully_ completed all members of the parent can be removed from the campaign and parent linked to the child campaigns. The parent cannot contain members while having child campaigns

- Clone the [#TEMPLATE - FY00_Q0_Brilliant Gifts Direct Mail TEMPLATE](https://experience.adobe.com/#/@gitlab/so:194-VVC-221/marketo-engage/classic/PG24060A1) into the appropriate folder and rename the program. If the intention is to run in ONE region, clone once. If the intention is to run in multiple regions and there's desire for tracking each region individually, clone enough programs for all regions (e.g. AMER, APJ, EMEA) and place in their own `FYXX_QX` folder under the primary [Brilliant Gifts program's folder](https://experience.adobe.com/#/@gitlab/so:194-VVC-221/marketo-engage/classic/PG28387A1). Keep the naming convention similar for the regional/child programs but add a region tag at the end of the program name (e.g. `FY00_Q0_Campaign_AMER`). 

- Sync ALL programs to SFDC 

- Note a few aspects of the template: The [01 - Processing](https://experience.adobe.com/#/@gitlab/so:194-VVC-221/marketo-engage/classic/SC63769A1ZN19) smart campaign only fires on certain program statuses and [ONLY IF THE LEAD APPEARS IN THE TARGET LIST](https://experience.adobe.com/#/@gitlab/so:194-VVC-221/marketo-engage/classic/SL53588098A1LA1). The target list can be swapped, if needed, but the processing smart campaign MUST be updated. In the flow, only the `Meeting Attended` status will send a lead to the primary Brilliant program's static list. A new static list will need to be created under the [primary Brilliant program](https://experience.adobe.com/#/@gitlab/so:194-VVC-221/marketo-engage/classic/PG28387A1) under the appropriate `FYXX_QX` folder and added to flow step 6 for each cloned program. Flow step 4 will add the lead to the primary Brilliant program under `Invite Sent` status, but the static list will be used for longterm tracking and cleaning within the primary program

### Step 2: Set up the Marketo programs

- Fill out the required program tokens. A token unique to this program type is the `my.qualifiedlink` token, which appears in the `Sales Nominated Invite` email. The Qualified link will be shared by the Qualified technical owner when it is ready (more on that below)

- The smart campaigns folder has many flows and which ones used will depend on whether the direct mail campaign is for a single region, whether the program is the "parent" program that communicates with Qualified (Qualified syncs with the SFDC campaign) or whether the program is a regional "child" program

- If the campaign is to take place in a single region and there is only one program, review `01 Processing - Single region campaign` and make sure all fields being updated in the flow steps are up to date with the proper program name

- If the campaign is taking place in multiple regions, on the `parent` program activate all the regional processing smart campaigns for the involved regions, e.g. `00 Processing - Parent - AMER` and `00 Processing - Parent - EMEA` if there are programs for EMEA and AMER. On each of the regional child programs, activate the `00 Processiong - Child` smart campaign

  - The parent program processes inputs from Qualified, calls the webhook to Brilliant to send the gift redemption email (only if the program status is `Meeting Attended`) and it also relays program status updates to the regional child programs

- Within the processing smart campaigns, be sure to change the program the smart campaign references to the correct regional child program in the first `if` flow step. If the smart campaign is named `AMER`, the flow step should call to the `AMER` program.

- Note that this template has been set up for use with multiple regions, so if there are extraneous parts of logic it is okay to remove those pieces to avoid logic errors

- The program receives `Meeting Booked` and `Meeting Attended` inputs from Qualified and the Processing smart campaign calls the webhook to Brilliant to send the gift redemption email (only if the program status is `Meeting Attended`) 

- Activate `03 Change to No Show` on the single or parent program to register `no show` activities * Feature is experimental at the moment

### Step 3: Target lists and loading nominated leads

The program template contains multiple target list assets, both static and smart lists, for each region. It is recommended to consult with MktgOps for this stage.

The program template contains a target list smart list asset. It is recommended to consult with MktgOps for this stage.

- To plan the target list(s), use `target list w/leads (global)`. For multi-region campaigns, either recreate the smart list in the pre-made region smart lists or clone the global and swap assets in the smart campaign

- If there is only one program, proceed with using smart campaign `Load static list and parent program from target list` to load the target list into the static list and the program

- If there are multiple regional programs, proceed with using smart campaign `Load static lists and child programs from target list` to load the target lists into the appropriate regional static list and the regional child programs

  - Leads loaded into the program(s) should have `Nominated` status once loaded

- To plan the target list(s), use `Target List NEW`. If there is another smart list being used for the target list, update where needed in the processing smart campaign(s)

- It is recommended to add all of the target list to the cloned program under the status `Nominated`

### Step 4: Emailing target list

- Is the Brilliant storefront established and adequate for this campaign's needs?

- What backend assets in Brilliant need to be updated? e.g., branded gift redemption emails

The Brilliant team also needs to verify the Marketo webhook is reaching their backend

The Brilliant team also needs to verify the Marketo program and webhook are reaching their backend

Note: MktgOps will need to verify the webhook is working by utilizing `Call to Brilliant TEST` and `Call to Brilliant TEST trigger` found in the program template. There are two smart campaigns because calling a webook needs a trigger campaign

Note: MktgOps will need to verify the webhook is working by utilizing [Call to Brilliant TEST](https://experience.adobe.com/#/@gitlab/so:194-VVC-221/marketo-engage/classic/SC76999A1ZN19) found in the main program. There are two smart campaigns involved because a smart campaign requesting a webhook needs to be a trigger based smart campaign, not a batch smart campaign. The TEST smart campaign links to the only smart campaign capable of calling to Brilliant's webhook: [Send to Brilliant webhook do not alter](https://experience.adobe.com/#/@gitlab/so:194-VVC-221/marketo-engage/classic/SC77009A1ZN19)

### Step 6: Qualified-powered meeting booking set up

This next step will require the help of the Qualified tech owner. Supply them with the SFDC campaign being used as the single or parent campaign. From there, a Qualified link will be created and shared by the tech owner to the requester. The link will be used during prospect outreach as the method needed for nominated prospects to book a meeting with Sales Dev

This next step will require the help of the Qualified tech owner. Supply them with the SFDC campaign being used for the campaign (the cloned one, not the primary Brilliant program). From there, a Qualified link will be created and shared by the tech owner to the requester. The link will be used during prospect outreach as the method needed for nominated prospects to book a meeting with Sales Dev

- Qualified will change program status to `Meeting Booked` when a prospect books a meeting

- A reminder email will be sent about the meeting 1 hour before the time

### Step 7: Campaign completion

At the end of the campaign, request the Qualified logic be taken down. Updates to Brilliant storefronts and preferred campaigns TBD. For multi-region campaigns, leads can be removed from the parent SFDC campaign/Marketo program. As long the leads have been removed from the parent campaign, the regional campaigns can be added as child campaigns to the parent campaign in SFDC

At the end of the campaign, request the Qualified logic be taken down. Updates to Brilliant storefronts and preferred campaigns TBD, but each new campaign will require checking in with Brilliant to update e-gift value and the confirmation email

## Steps to Setup LinkedIn Lead Gen Form