Privacy Targeting allows publishers to protect their user data from both the Supply and Demand tag level. Privacy Targeting can be found in the ‘privacy’ section of the targeting tab. Users can choose to allow or block targeting based on different values pertaining to privacy targeting types.
...
Privacy Targeting allows publishers the option to set specific privacy values, that if delivered in the supply request, will block an ad request from going to auction.
Different types of Privacy Targeting:
COPPA:
The Children’s online privacy protection act (COPPA) is a federal law that protects the privacy of children under the age of 13. SpringServe relies on the coppa=1/0 flag from incoming supply requests to understand if the user qualifies for COPPA. Publishers could now choose to target COPPA supply by enabling or disabling it in SpringServe..
...
o If you change the setting to ‘Enabled’ then any incoming supply tags with coppa=1 will get blocked before auction.
...
LMT / DNT:
LMT= Limit ad Tracking and DNT = Do not track are device derived user based settings. When a user opts in to either one of these from their device it means they are opting out of the right to use their data in any way, including sharing with partners or adding them to audiences. SpringServe does not have the right to add them to audience based segments or share their data for any purpose. Both LMT and DNT have the same meaning and functionality in SpringServe.
...
· user can specify if parameter is required in order to pass targeting
...
US Privacy:
US Privacy is the parameter used to flag requests under the California Consumer Privacy Act (CCPA).· Current applies only to requests from California
· user specifies if they are using an allow-list
...
· user can specify if parameter is required in order to pass targeting. This is based on the composition of Values must be a valid composition string based off the privacy string instructions found here:
...
GDPR:
General Data Protection Regulation(GDPR) is a regulation that requires businesses to protect the personal data and privacy of EU citizens for transactions that occur within EU member states.
· If users fall under the jurisdiction of the GDPR, they must have it is the publishers responsibility to provide the user with the option to vendor consent to specific uses of data under the GDPR-compliant Privacy Policy.
· The GDPR applies to user if user:
i. Are located in the EU , Canada or
ii. Offer services to individuals located in the EU , Canada or
iii. Monitor the behavior of individuals located in the EU EU or Canada
· targeting enabled → user will specify allowed types of values
...
· user can specify if parameter is required in order to pass targeting
...
GDPR Consent String:
· applies only to requests from EU or Canada
· targeting enabled → user will specify allowed types of values
...
· empty: parameter exists in query string but value is not filled in
...