The Vendors triggered prior to consent compliance metric covers the number of vendors that we have observed on the selected properties ahead of a user making a choice on the CMP. The metric details view enables your organization to view data visualizations for the compliance metric against your benchmarks and drill down into scanning results.
Navigate to a detailed view for a specific compliance metric by applying your filters to your dashboard and selecting a compliance metric from the Compliance Metrics table.
Note: You can continue to edit filters to adjust properties, regions, periodization, and benchmark properties while viewing the details for a particular metric.
Overview
The overview section of the metric details page is comprised of 2 graphs that allow you to compare, based on your filters, your relative score and average count for the metric compared to your benchmark property.
Definitions
- Average count: the average number of vendors per scan that fulfilled the criteria of the metric (e.g. non disclosed, triggered before consent, etc...)
- Relative score: a percentile ranking that compares selected properties against your benchmark properties for this particular compliance metric.
Detailed breakdown
The detailed breakdown table lists vendor details that were observed on your properties and who were triggered before an end-user made a choice with a CMP within your selected periodization. Please refer to the table below for definitions for each vendor detail in the table.
| Vendor detail | Description |
| Vendor Name | Name of observed vendor on your property(ies) who was triggered before an end-user performed a consent action. |
| Vendor Status | Click here for more information. |
| Prevalence (My Properties) | The prevalence of the triggered vendor across the selected properties. |
| Registered Legal Bases on IAB TCF | The legal bases used by the vendor that have been registered with the IAB TCF Global Vendor List. Click here for more information on the possible options. |
| First Seen | The first date within your periodization where the triggered vendor was observed on your property(ies). |
| Last Seen | The last date within your periodization where the triggered vendor was observed on your property(ies). |
| Technology categorisation |
Categorisation is provided by Sourcepoint after rigorous and careful research into the vendor's data practices by reviewing the vendor's privacy policy with regards to the particular cookie or technology. If triggered vendor belongs to more than a single technology category, click the number in the cell to view all categories. |
| Information Storage/Access |
The methods used by the triggered vendor to access and/or store data on an end-users device such as cookies and other identifiers. |
| Cookie Name |
The name of cookie(s) dropped by the vendor who is triggered prior to a consent action. If vendor drops more than a single cookie, click the number in the cell to view all cookie names |
| Disclosed Vendor? |
Checks whether the triggered vendor is included on your CMP's vendor list.
|
| Referrer Vendor |
The vendor who owns the last web address accessed by the browser prior to triggering the vendor in question. If triggered vendor is referred to by more than one vendor on your vendor list, click the number in the cell to view all referrer vendors. |
| Vendor Details |
Click here for more information. |
Note: Filter the table by different headers by selecting the filter icon from a vendor detail header and apply filters via the dropdown menu. Click OK to apply the filters.
Registered Legal Bases on IAB TCF glossary
Below are the various options that can be populated in the Registered Legal Bases on IAB TCF column in the vendor details table. These options can also be used to filter the vendor details table.
| Registered Legal Bases | Description |
| No purposes are used | The vendor does not require consent for any purposes, but has registered for TCF Special Features and/or purposes. |
| Purpose 1 is non-applicable, other purposes are used | The vendor does not require consent for purpose 1. This could be considered higher risk as purpose 1 is the definitive purpose for accessing the users device. |
| Personalised ads purposes use Legitimate Interest as legal basis | The vendor requires Legitimate Interest for Personalised ads purposes (purpose 3, 4, 5 and 6). |
| Personalised ads purposes are not used. Legitimate Interest is used for at least one other purpose | The vendor does not require Legitimate Interest for the Personalised ads purposes (purpose 3, 4, 5, and 6). However, Legitimate Interest is required for one or more purposes ( purpose 2, 7, 8, 9, and 10). Some jurisdictions like Germany frown on the use of Legitimate Interest for any purpose. |
| Consent is a possible legal base for all purposes | The vendor has made every purpose flexible - allowing the publisher to choose either User Consent, Legitimate Interest or Not Applicable. |
| Consent is a possible legal base for personalised ads | The vendor has made all Personalised ads purposes (purpose 3, 4, 5, and 6) flexible and the publisher can choose whether these are set to User Consent or Legitimate Interest. |
| Other | This vendor has other types of consent selected for other purposes. |
Vendor details
The vendor details modal allows your organization to view specific information about the vendor. View the vendor details modal by clicking View under the Vendor Details column inline with a specific vendor.
From the modal, you organization can view vendor details such as the technology categorization of the vendor, the vendors privacy policy, and the vendor's IAB Global Vendor List identification number (if applicable).
Select any website from under the Websites header to view the URLs where the vendor was observed.
Expand any Page URL to view the host domains associated with the vendor. Host domains are servers that are making network calls to your website that Sourcepoint has mapped to this vendor.
Note: View even more information, including the full URL path used by the vendor by downloading the vendor detail as a csv file.
Comments
0 comments