# Control your Extra vendors finely

Our CMP relies on the IAB standard to collect and distribute consent to IAB partners. For other partners, we have integrated a system in the configuration interface and in the CMP so that the user can give consent to these non-IAB partners, also known as extra vendors.

***

## Configuration of an extra vendor in the configuration interface

We assume that you have already created your extra vendor in the configuration interface. On your source, add your extra vendor and associate it with IAB purposes or extra purposes.

<figure><img src="https://4229351976-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkyFlZKFaKP4MUM0zILOg%2Fuploads%2FfOZ0JRe7eHfz4OwTAqNt%2FGTM-extra-vendor-add-in-source.png?alt=media&#x26;token=68c052f3-d221-43a2-91fa-029fc8551325" alt=""><figcaption></figcaption></figure>

Once configured, save your source and associated notices.

## Configuration in GTMs

### Consent recovery for an extra vendor

The CMP sends an event to the **dataLayer** variable in the GCM (Google Consent Mode) protocol for each extra vendor consented by the user. This event takes the following form:&#x20;

<figure><img src="https://4229351976-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkyFlZKFaKP4MUM0zILOg%2Fuploads%2FK7F3jnV4iPH26P5QJdLS%2FGTM1.png?alt=media&#x26;token=df4bc88f-7110-4387-8294-758323b18503" alt=""><figcaption></figcaption></figure>

The name of these events is composed of:

* `acextravendor_granted_`
* and the extra vendor id

In GTM, to trigger the extra vendor code, we'll retrieve each event sent by the CMP and trigger the tag.

### Create a trigger for an extra vendor

To retrieve the event sent by the CMP, you need to create a custom trigger. To do this, you must :

1. Go to GTM and click on the **Triggers** menu in the left-hand side panel
2. Click on the **New** button

<figure><img src="https://4229351976-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkyFlZKFaKP4MUM0zILOg%2Fuploads%2FE8glBVR4FuK6BKEHEULe%2FGTM-extra-vendor-new-trigger.png?alt=media&#x26;token=fbc12229-83e1-42af-a283-93e7811c1b2e" alt=""><figcaption></figcaption></figure>

3. Click on **Trigger configuration**
4. From the list of events in the right-hand side panel, select **Custom event**

<figure><img src="https://4229351976-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkyFlZKFaKP4MUM0zILOg%2Fuploads%2F0ExcrxqlESL1e8LOGTPc%2FGTM-extra-vendor-select-custom-event.png?alt=media&#x26;token=0c02d75a-09f2-4082-b877-e99129a0d0c6" alt=""><figcaption></figcaption></figure>

5. In the AppConsent configuration interface, go to **Extra Vendors**
6. Then click on the "copy" button on the line of the extra vendor you wish to integrate

<figure><img src="https://4229351976-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkyFlZKFaKP4MUM0zILOg%2Fuploads%2F1BAQcYYH9zbsGGlopuRV%2FGTM-extra-vendor-copy-id-vendor.png?alt=media&#x26;token=85e418aa-8394-491c-9375-439d3716d553" alt=""><figcaption></figcaption></figure>

7. Once the partner id has been copied, return to the custom event in GTM
8. In the **Event name** field, enter `acextravendor_granted_` + the partner id

<figure><img src="https://4229351976-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkyFlZKFaKP4MUM0zILOg%2Fuploads%2FwZz5bH88TENG2SpkbE24%2FGTM-extra-vendor-add-id-custom-event.png?alt=media&#x26;token=7935c88b-1b92-4a14-940d-65ad9a7070d7" alt=""><figcaption></figcaption></figure>

9. Name your trigger, then save

{% hint style="danger" %}
**CAUTION**

The **acextravendors\_granted\_id** (in our example **acextravendor\_granted\_rS06k3iu**) must be filled in exactly as shown. You can rename the title (in the top left-hand corner), but never the value in the **Event name** field. Otherwise, you'll lose the link with the tag.
{% endhint %}

### Extra vendor tag creation

1. Click on the **Tags** menu in the left-hand side panel
2. Then click on the **New** button

<figure><img src="https://4229351976-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkyFlZKFaKP4MUM0zILOg%2Fuploads%2F71hfgo5kkL4wKKyaZxPv%2FGTM-extra-vendor-new-tag.png?alt=media&#x26;token=a1d2717d-e9fb-4d5c-9362-8534ccbc2038" alt=""><figcaption></figcaption></figure>

3. Click on tag configuration
4. Then select the **Custom HTML** template

<figure><img src="https://4229351976-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkyFlZKFaKP4MUM0zILOg%2Fuploads%2FvoX3XI2wuQaR7qI0rBD3%2FGTM-extra-vendor-select-custom-html.png?alt=media&#x26;token=2a385553-3cb6-4d0a-9578-b7f653c9a7d2" alt=""><figcaption></figcaption></figure>

5. Put the extra vendor's script in the **HTML** field

6. Then click on the **Trigger** section

7. Then select the custom trigger created earlier

<figure><img src="https://4229351976-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkyFlZKFaKP4MUM0zILOg%2Fuploads%2FwqeINoVVMtLXjaEV80YM%2FGTM-extra-vendor-html.png?alt=media&#x26;token=382db055-3b13-4285-9de1-707254d73751" alt=""><figcaption></figcaption></figure>

8. Name and save your tag

{% hint style="danger" %}
**CAUTION**

In this example, we're using the **Custom HTML** template, but it works with other template types.
{% endhint %}

That's it. Now your tag will be fired only if :

* your extra vendor has been consented to by the user
* AND if at least one of the purposes associated with your partner has been consented

Have a suggestion ? Just drop an email to <support@sfbx.io>
