Privacy Targeting

Privacy Targeting can be found in the ‘privacy’ section of the targeting tab. 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   The default selection for ‘Block COPPA Supply’ is ‘Disabled’ which will allow incoming supply tags with coppa=1 through.

Open

o   If you change the setting to ‘Enabled’ then any incoming supply tags with coppa=1 will get blocked before auction.

Open

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 add their data to audience based segments.

Additionally Springserve will:

• Will not set or track user cookies

• Usersync is disabled

• Users will not be added to segments

• True IP and Device ID will be passed to SSP’s and DSP’s along with the flag DNT:1 and LMT:1 so that they can apply the appropriate logic.

Both LMT and DNT share the same functionality in SpringServe.

·       targeting enabled → SpringServe users can specify allowed values

·       true: parameter value is true or 1

·       false: parameter value is false or 0

·       empty: parameter exists in query string but value is not filled in i.e., macro still is there or there is no value at all

·       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).

·       user specifies if they are using an allow-list

·       user provides list of allowed / blocked values

·       user can specify if parameter is required in order to pass targeting. Values must be a valid composition string based off the privacy string instructions found here:

USPrivacy/CCPA/US Privacy String.md at master · InteractiveAdvertisingBureau/USPrivacy

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, it is the publishers responsibility to provide the user with the option to consent to specific uses of data under the GDPR.

·       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 or Canada  

·       targeting enabled → user will specify allowed types of values

·       true: parameter value is true or 1

·       false: parameter value is false or 0

·       empty: parameter exists in query string but value is not filled in i.e., macro still is there or there is no value at all

·       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

·  valid: parameter value is a valid GDPR consent string

·  invalid: parameter is not a valid GDPR consent string

·  empty: parameter exists in query string but value is not filled in