# Create custom vendor {% hint style="success" %} **Access Type**: Data Manager - Editor {% endhint %} By default, Didomi pre-populates your organization's account with [IAB, Google ATP, and Global vendors](/data-manager/vendors.md). In addition to these vendors, your organization can configure custom vendors for partners that you work with but are not reflected in these lists. In this article, we will cover how to create and configure a new custom vendor via the Data Manager. Click **Data Manager** in the left-hand panel and select the **Vendors** tab on the subsequent page.

Click **Add vendor +**.

Use the provided fields on the subsequent page to configure the following attributes for the custom vendor:

Field	Description
Vendor name	Name of the vendor.
Vendor type	If the vendor being registered as a custom vendor is owned by your organization, select the Declare the vendor as your own property toggle. A custom vendor with this setting will not be included in the Partners section of your consent ntoice.
Privacy policy	URL to the custom vendor's privacy policy
Opt-in purposes	Use the provided field to select purposes where the vendor utilizes explicit consent as a legal basis. Note: If the custom vendor needs a custom purpose to be required, your organization can map the purpose to whichever legal basis you wish and set the requirement when configuring your consent notice. Click here for more information.
Opt-out purposes	Use the provided field to select purposes where the vendor utilizes legitimate interest or explicit opt-out as a legal basis. Note: If the custom vendor needs a custom purpose to be required, your organization can map the purpose to whichever legal basis you wish and set the requirement when configuring your consent notice. Click here for more information.
Domains owned by the vendor	In order to improve the accuracy of your organization's compliance reports, it is important to add all domains from which the custom vendor could drop trackers or call other vendors. Use the provided field to add any domains owned by the custom vendor

{% hint style="info" %} A custom vendor requires at least one purpose (either opt-in or opt-out) in order to appear in any consent notice to which it is added. {% endhint %}

In addition to the data above, your organization can include the following information for the custom vendor by expanding the appropriate accordion and using the provided steps to add details for the custom vendor. Select the tabs below for more information on each accordion. {% tabs %} {% tab title="Storage" %} Expand the **Storage** accordion and use the provided fields to inform the end-user about: * Maximum cookie duration * Additional storage methods used by the custom vendor

Provide details for each storage item droppped/used by the custom vendor by clicking **+ Add a new storage**. From the modal, use the **Type of storage** dropdown menu to select a storage type and fill in the appropriate details in the subsequent fields.

Click **Add** when finished. Repeat as necessary for other storage methods used by the custom vendor. Any added storage methods will be listed in the accordion and can be edited or deleted by clicking the appropriate icon inline with the storage method .

{% endtab %} {% tab title="Contact" %} Expand the **Contact** accordion and click **Add address** to provide an email address and/or physical mailing address for the custom vendor.

From the modal, use the **Language** dropdown menu to select a language and fill in the appropriate details in the subsequent fields. Click **Add** when finished.

Repeat as necessary for other addresses used by the custom vendor. Any added addresses will be listed in the accordion and can be edited or deleted by clicking the appropriate icon.

{% endtab %} {% tab title="Advanced" %} Expand the **Advanced** accordion and use the provided fields to input/select any of the following details for the custom vendor:

Field	Description
Custom SDK ID	Enables your organization to configure a Custom SDK ID for the custom vendor which is a configurable ID used solely for migrating existing consent notices from JSON configurations. Once configured, Didomi will force set the SDK ID of the vendor to an ID in your JSON configuration
Protection	A protection for a vendor refers to a legal mechanism that allows the transfer of personal data from the EU/EEA to a third country (like the US) in compliance with GDPR Article 46 or similar data protection frameworks. If necessary, select the protection from the pre-populated list.
Country	The country where the main headquarters is located for the custom vendor
Provider	Select what kind of provider the custom vendor is for your organization from the pre-populated list
Service provider category	Select the service provided by the custom vendor from the pre-populated list

{% endtab %} {% tab title="Other links" %} Expand the **Other links** accordion and use the provided fields to add any relevant links to the custom vendor. These links include: * Website * Opt-out link * Terms and conditions link * Data processing agreement link * Applicable protection link * Subprocessors link

{% endtab %} {% endtabs %} Click **Save** when finished. The custom vendor will be added to your organization's Didomi account and can be navigated to by using the vendor filter.

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.didomi.io/data-manager/vendors/create-custom-vendor.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.