Permission: Vendor List - U.S. Multi-State
Opt out hooks allow you to set up custom actions for a vendor or privacy choice within a vendor list. An opt out hook is eligible to be fired if the vendor or privacy choice has been opted out of by the end-user. In this article, we will cover the following in regards to opt out hooks:
Note: The following applies to all U.S. Multi-State Privacy vendor list frameworks (National or Standard)
To start, navigate to a U.S. Multi-State Privacy vendor list by selecting Vendor Management from the left-hand rail and clicking U.S. Multi-State Privacy from the menu.
Select a U.S. Multi-State Privacy vendor list on the subsequent page.
Navigate to the Opt In/Opt Out Hooks tab and select whether to configure a hook for a Vendor or a Privacy Choice from the page.
Overview
In this section we will review the key aspects of opt out hooks that can be configured for a vendor and/or privacy choice.
| Field | Description |
| Geolocation |
Utilize the provided logic statement to target to or away from specific geographic regions. Examples • To only fire the opt out hook in Utah, you would set the action to fire IN Utah. |
| User has changed state |
Prevents the hook from being triggered on the default state of the user. When checked, the opt out hook will only trigger when the end-user has changed their state on the vendor or privacy choice (i.e. from opted out to opted in). |
| Custom JS |
One of four implementation types that can be used when creating a opt out hook. Use the provided field to fire any input code.The code can reference any globally scoped function or variable that exists on the site's page. These functions and variables will likely need to be referenced from the window object. |
| Google Tag Manager |
One of four implementation types that can be used when creating a opt out hook. Allows you to trigger a custom event that has been configured in Google Tag Manager upon the end-user opting out of the vendor or privacy choice. Click here for more information. |
| Inline URL |
One of four implementation types that can be used when creating a opt out hook. Allows you to fire a pixel when an end-user opts out of a vendor or privacy choice. In cases where a SSP or DSP pixel should only be fired based upon an end-user's opt out state, the pixel can be trafficked here and fired. |
| Cookies |
One of four implementation types that can be used when creating a opt out hook. Allows you to set cookies (including the name, value, domain, and expiration) |
Add opt out hook
Click + Add Hook.
Select a vendor or privacy choice from the provided dropdown menu in the subsequent modal.
Select the Opt Out Hooks tab and configure the hook. Click Apply changes when finished.
The hook will be added to your vendor list and added to the table on the Vendor or Privacy Choice tab.
Click Save in the vendor list builder to confirm the addition.
Imported opt out hooks
When configuring the vendors on your U.S. Multi-State Privacy vendor list, your organization is given an option to import vendors from an existing vendor list. In addition those imported vendors, you can also import any reject actions configured for those vendors as opt out hooks for your U.S. Multi-State Privacy vendor list.
If your organization decides to import reject actions alongside vendors from another vendor list, the reject actions will automatically appear in the table for Vendors in the Opt In/Opt Out Hooks tab.
Once imported, your organization can edit or delete the opt out hook from the U.S. Multi-State Privacy vendor list builder.
Comments
0 comments