help.salesforce.com Open in urlscan Pro
2a02:26f0:480:24::1726:6257  Public Scan

Submitted URL: http://click.mail.salesforce.com/?qs=ef211828d0563013ad94fe4ccf99ac0d21c21aed1f94df6be83bb46c7d1d1aa1a0f5651f519e5edd7ca37ad5d8d1...
Effective URL: https://help.salesforce.com/s/articleView?language=en_US&id=000983248&type=1&utm_source=techcomms&utm_medium=email&utm_campa...
Submission: On February 23 via api from US — Scanned from DE

Form analysis 1 forms found in the DOM

POST

<form id="fileUploadForm" enctype="multipart/form-data" method="post" target="fileUploadIframe"><input type="file" id="fileSelector" name="file" style="display: none;"><input name="filename" type="hidden"></form>

Text Content

Loading
×Sorry to interrupt
CSS Error

Refresh
Looking for information about Marketing Cloud Growth Edition?Read More
Close
Get Ready for Hyperforce.Read More
Close


NEW GOOGLE CONSENT SETTINGS IN MARKETING CLOUD ADVERTISING STUDIO

Publish Date: Feb 19, 2024
Description

Starting March 6, 2024 Google requires advertisers to provide two consent
settings when uploading data for use with Customer Match. Marketing Cloud
Advertising (Ad Studio) submits data to Customer Match. Ad Studio Customers can
now update these settings within the Ad  Studio UI for new and existing
audiences. 

These settings inform how Google uses data for matching (user data), and for ad
targeting (personalization). Google’s documentation describes these as follows.



For each setting, advertisers may provide a value of Granted, Denied, or
Unspecified. By default, Ad Studio will send a value of Unspecified.

EEA user data sent without an ad_user_data value of “Granted” will not be
processed by Google for matching. EEA user data sent without an
ad_personalization value of “Granted” cannot be used for ad personalization
(targeting). Google makes a determination of whether data pertains to an EEA
user.

 

Resolution

How do I update consent settings? 

These are set in Advertising Studio at an audience level. They can be applied
when creating a new audience, or for existing audiences. Google acts on these
signals at the time user data is provided – not retroactively. 

When creating a new audience:

On the audience configuration page, select a value for “User Data Consent” and a
value for “Personalization Consent.” 



 

For existing audiences:


Consent settings will be processed by Google only when data that is submitted
for matching. For example, if an audience has a refresh schedule, any refresh
jobs with new audience members will send consent status for those users. Google
does not require advertisers to submit consent status retroactively for data
sent prior to March 6th 2024.

 

On the audience configuration page, select a value for “User Data Consent” and a
value for “Personalization Consent.” Click “Save.” 



 

Q&A:

Does this apply to all of my audience data submitted through Ad Studio, or just
the audience data shared to Google?

These changes are a response to Google policies and Ad Studio does not collect
these consent parameters for other ad platforms. 

What if I have questions about Google’s consent policies or how Google is using
my data submitted through Ad Studio? 

Please reach out to your Google account team, as they are in the best position
to explain their policies.

Do I need to add these consent values to my source data, such as add new columns
to my data extensions?

No. Google processes these values at the time Ad Studio submits data for
matching, and applies the provided consent to all members of the audience that
are processed at that time. 

Do I need to go back and make changes to my existing audiences? 

If you anticipate updating the source data for existing audiences, it would be a
best practice to update consent settings for those audiences. Google does not
require this consent information be provided for user data submitted prior to
March 6, 2024. 

Is there a way to bulk-update multiple audiences at the same time? 

No. 

I also send data to Google via Salesforce Data Cloud Ad Audiences, does it work
the same way in Data Cloud?  

Data Cloud has a different implementation to support Google’s consent policies.
Please click here to review Data Clouds new consent settings for Google
activations. 

 

Knowledge Article Number

000983248

Did this article solve your issue?
Let us know so we can improve!
YesNo
 
1-800-667-6389
 * 
 * 
 * 
 * 

SALESFORCE
 * Privacy Statement
 * Security Statement
 * Terms of Use
 * Participation Guidelines
 * Cookie Preference Center
 * Your Privacy Choices

COMMUNITY
 * AppExchange
 * Salesforce Admins
 * Salesforce Developers
 * Trailhead
 * Training
 * Trust

SUPPORT & SERVICES

Need help? Find more resources or connect with an expert.

Get Support

Powered by Experience Cloud

--------------------------------------------------------------------------------

© Copyright 2024 Salesforce, Inc. All rights reserved. Various trademarks held
by their respective owners.
Salesforce, Inc. Salesforce Tower, 415 Mission Street, 3rd Floor, San Francisco,
CA 94105, United States


English
Select Org
 * Select OrgEnglish
 * Français
 * Deutsch
 * Italiano
 * 日本語
 * Español (México)
 * Español
 * 中文(简体)
 * 中文(繁體)
 * 한국어
 * Русский
 * Português (Brasil)
 * Suomi
 * Dansk
 * Svenska
 * Nederlands
 * Norsk

Live chat:Let's Chat


Loading

We use cookies on our website to improve website performance, to analyze website
usage and to tailor content and offers to your interests. Advertising and
functional cookies are only placed with your consent. By clicking “Accept All
Cookies”, you consent to us placing these cookies. By clicking “Do Not Accept”,
you reject the usage of such cookies. We always place required cookies, which
are necessary for the website to work properly. For more information about the
different cookies we are using, read the Privacy Statement. To change your
cookie settings and preferences, click the Cookie Consent Manager button.
Do Not Accept Accept All Cookies
Cookie Consent Manager



COOKIE CONSENT MANAGER




 * GENERAL INFORMATION


 * REQUIRED COOKIES


 * FUNCTIONAL COOKIES


 * ADVERTISING COOKIES

GENERAL INFORMATION

We use three kinds of cookies on our websites: required, functional, and
advertising. You can choose whether functional and advertising cookies apply.
Click on the different cookie categories to find out more about each category
and to change the default settings.
Privacy Statement

REQUIRED COOKIES

Always Active

Required cookies are necessary for basic website functionality. Some examples
include: session cookies needed to transmit the website, authentication cookies,
and security cookies.

Cookies Details‎

FUNCTIONAL COOKIES

Functional Cookies


Functional cookies enhance functions, performance, and services on the website.
Some examples include: cookies used to analyze site traffic, cookies used for
market research, and cookies used to display advertising that is not directed to
a particular individual.

Cookies Details‎

ADVERTISING COOKIES

Advertising Cookies


Advertising cookies track activity across websites in order to understand a
viewer’s interests, and direct them specific marketing. Some examples include:
cookies used for remarketing, or interest-based advertising.

Cookies Details‎
Back Button


COOKIE LIST

Filter Button
Consent Leg.Interest
checkbox label label
checkbox label label
checkbox label label

Clear
checkbox label label
Apply Cancel
Save Settings
Accept All Cookies