PUBLIC

2022-12-15

Integrating SAP Marketing with Google Ads via

SAP Cloud Integration
© 2022 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN  

Content

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 Setting Up Google. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3.1 Setting Up Google Ads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3.2 Creating Your Google OAuth Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

4 Setting Up SAP Marketing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4.1 Configure the Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

5 Setting Up Secured Communications Across the Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . 10

5.1 Setting Up Secured Communication Between SAP Marketing and SAP Cloud Integration. . . . . . . . . . 11

Download Root SSL Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Import Root Certificate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Download SSL Certificate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Set Up the Certificate-to-User Mapping in the SAP Cloud Integration Tenant. . . . . . . . . . . . . . . . 14

5.2 Setting Up Secured Communication Between SAP Cloud Integration and Google. . . . . . . . . . . . . . . 15

Download Certificates from Google Trust Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Import the Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Import the Local KeyStore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

6 Setting Up SAP Cloud Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

6.1 Create an SAP Support Ticket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

6.2 Copy the Integration Package to your Workspace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

6.3 Set Up the OAuth Authorization Code Grant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

6.4 Set Up the Integration Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

7 Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

7.1 Message Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Check iFlow Errors in Attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Check Runtime Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

7.2 FAQs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

7.3 Integration Package Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
2 PUBLIC Content
1 Introduction

Overview of the integration scenario.

 Note

Before you start, make sure you have the required version of this document. You can find the available
versions at the following location: [Link]

The integration with Google Ads enables you to do the following:

• Assign Google Ads campaigns to SAP Marketing campaigns to analyze the performance of these
campaigns in SAP Marketing.
• Send a target group to Google Ads to create a custom audience that can be used for campaign targeting in
Google Ads.

This guide is for administrators responsible for performing the configuration activities required to set up the
integration.

SAP Cloud Integration is used as a middleware between SAP Marketing and Google Ads. It's responsible for
OAuth 2.0 token management and any communication between SAP Marketing and the Google Ads API.

Configuration

To run the SAP Marketing - Google Ads integration scenario, configuration settings are required in the following
systems:

• Google Ads
• SAP Cloud Integration
• SAP Marketing

We've added an FAQ to address frequently asked questions about the integration. Please refer to it before you
contact SAP Support. For more information, see FAQs [page 27].

 Note

In the PDF version of this guide, some links to certain topics may be missing. All links are available in the
HTML version of the guide.

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
Introduction PUBLIC 3
2 Document History

The following table provides an overview of the most important document changes.

Document History
Date Description

2020-10-07 Initial version for the Google Ads integration with SAP Marketing
2020 via SAP Cloud Integration.

2021-04-16 Removed defective and unnecessary link from Step 1 in the fol­
lowing topic: Set Up the OAuth Authorization Code Grant [page
22].

2022-02-18 Updated content to reflect changes introduced by the migration

to the Google Ads API.

Topics changed in this guide are as follows:

• • Setting Up Google Ads [page 5]

• Set Up the Integration Flows [page 24]
• Support [page 25]
• Check iFlow Errors in Attachments [page 25]
• FAQs [page 27]
• Integration Package Updates [page 30]

 Note

If you are updating your integration package,

please see this topic first.

2022-02-28 Updated the version of the integration package from 3.0.0 to

3.0.1. For more information, see Integration Package Updates
[page 30].

2202-10-03 For integration package 3.1.0, updates about the Google OAuth
setup were added because of Google's OAuth out-of-band flow
deprecation. Information about certificate-based authentication
was added.

2022-10-12 Added link to blog entry about integration package updates. For
more information see, Integration Package Updates [page 30].

2022-12-15 Corrected SAP Cloud Integration redirect URI. For more informa­
tion, see Creating Your Google OAuth Client [page 5].

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
4 PUBLIC Document History
3 Setting Up Google

Set up your Google Manager Account and OAuth client for communication with your SAP Cloud Integration
tenant.

3.1 Setting Up Google Ads

Set up your Google Manager Account for integration with SAP Marketing.

Manager Account

Ensure that all of your Google Ads accounts are grouped under a single Manager Account in Google Ads.

To create a Manager Account and to grant access to all other accounts that you want to appear in SAP
Marketing, see Manager Accounts .

 Note

If you want to transfer target groups from SAP Marketing to Google Ads, ensure that your Google Ads
account meets the necessary requirements. For example, your Google Ads account must have a good
history of policy compliance, a good payment history, and more. For more information, see Advertising
Policies Help .

3.2 Creating Your Google OAuth Client

Create your OAuth Client to allow the authentication on the communication between SAP Cloud Integration
and Google services.

Context

Create a Google API Console project and set up the OAuth client. The OAuth client is used for the OAuth token
exchange for the Google Ads API call.

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
Setting Up Google PUBLIC 5
Procedure

1. Log in to Google Cloud with your manager account and create a Google API Console project. For more
information, see Configure a Google API Console Project for the Google Ads API .
2. Enable the Google Ads API.
3. Configure the consent screen.
a. In the OAuth consent screen, choose one of the following user types:
• Internal if you're using the Google Workspace.
• External if you're not using the Google Workspace.

 Note

A Google Cloud Platform project with an OAuth consent screen configured for an external user
type and a publishing status of "Testing" is issued a refresh token that expires in 7 days. To avoid
the limitation of short-lived refresh tokens, your Google App needs to go through a verification
process. For more information about Google's verification process, see OAuth API verification
FAQs . Until the verification is completed, the app is in test mode, can only be used by test users,
and the issued refresh token expires in 7 days. For more information about refresh token expiration,
see Refresh Token Expiration .

b. Edit the app registration.

a. Fill in the mandatory fields under App information and Developer contact information.
b. Add the scopes of the Google Ads API.
c. Only if you chose External as the user type, add the email related to the Google Ads manager account
as a test user.
4. Configure the credentials.
a. Create an OAuth Client ID by choosing Web application as the application type.
b. Add the SAP Cloud Integration tenant redirection URI to Authorized redirect URIs. You can determine
the redirect URI by doing the following:
• Log into SAP Cloud Integration and check your host name in the browser address field. The URL
may look like one of the following examples; [Link] name>/itspaces or https://
<host name>/shell/home.
• Use the <host name> to construct the following redirect URI: [Link]
itspaces/odata/api/v1/OAuthTokenFromCode

You can change the list of authorized redirect URIs when you edit the related OAuth 2.0 Client ID.

Results

You have an OAuth client ID and client secret.

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
6 PUBLIC Setting Up Google
4 Setting Up SAP Marketing

The integration between SAP Marketing and SAP Cloud Integration requires Web Service Logical Port
configuration.

Web Service Logical Port configuration must be done for each service in SAP Marketing to trigger the related
IFlow in your SAP Cloud Integration tenant.

To complete the integration between SAP Marketing and SAP Cloud Integration, you must do the following:

1. Configure the Services [page 7]

Set up the communication between SAP Marketing and SAP Cloud Integration by configuring the Web
Service Logical Port for each service.

4.1 Configure the Services

Set up the communication between SAP Marketing and SAP Cloud Integration by configuring the Web Service
Logical Port for each service.

Context

Configure each of the following services by following the procedure to set up the connection between SAP
Marketing and SAP Cloud Integration:

Service Name Changed Entry Values

ManagedCustomerServiceInterface • Search for

ManagedCustomerServiceInterface
• Set the Path to: /cxf/
[Link]
ice

reportDefinition • Search for reportDefinition

• Set the Path to: /cxf/
[Link]

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
Setting Up SAP Marketing PUBLIC 7
Service Name Changed Entry Values

AdwordsUserListServiceInterface • Search for

AdwordsUserListServiceInterface
• Set the Path to: /cxf/
[Link]
ice

CampaignServiceReadInterface • Search for CampaignServiceReadInterface

• Set the Path to: /cxf/
[Link]

Procedure

1. From your ABAP server, run transaction SOAMANAGER.

2. From the Web UI, select Web Service Configuration.
3. Search for the object name using the service name (see services listed in table above), then choose the
service from the result list.
4. Choose Create and then Manual Configuration to define a new logical port.
5. Enter DEFAULT as Logical Port Name.
6. Select Logical Port Default.

7. Choose Next.

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
8 PUBLIC Setting Up SAP Marketing
 8. In the Authentication Settings section, select X509 SSL Client Certificate.

9. In the X.509 SSL Client PSE section, select SSL Client (Standard).
10. Click Next.
11. Select URL components.
12. Enter the following information:

Field Name Entry Value

Protocol HTTPS

Host Your SAP Cloud Integration tenant iflmap node URL.

Port 443

Path The path value for your service, as identified in the above
table that lists the services to configure.

13. Click Next.

14. Ensure that Message ID Protocol is set to Suppress ID Transfer.
15. Click Finish.

Task overview: Setting Up SAP Marketing [page 7]

Related Information

Setting Up SAP Marketing [page 7]

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
Setting Up SAP Marketing PUBLIC 9
5 Setting Up Secured Communications
Across the Landscape

Certificates are required to securely communicate across the landscape. You must set up the certificates to
allow this communication to occur.

SAP Marketing must contain the root certificate from the SAP Cloud Integration tenant load balancer. The SAP
Cloud Integration tenant must contain the SSL certificate used by the gateway in SAP Marketing .

The SAP Cloud Integration tenant must also contain the root certificates from Google services, which allows
the communication on OAuth 2.0 token exchange.

The following diagram provides an overview of the integration process when using certificates:

To set up the certificates, complete the steps in the following sections of this guide:

• Setting Up Secured Communication Between SAP Marketing and SAP Cloud Integration
• Setting Up Secured Communication Between SAP Cloud Integration and Google

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
10 PUBLIC Setting Up Secured Communications Across the Landscape
5.1 Setting Up Secured Communication Between SAP
Marketing and SAP Cloud Integration

5.1.1  Download Root SSL Certificate

Download the root certificate from the SAP Cloud Integration load balancer.

Context

SAP Marketing needs to trust SAP Cloud Integration as a server. The SAP Cloud Integration tenant worker
node URL has the certificate chain that needs to be imported into the SAP Marketing System Certificate Trust
List.

Procedure

1. Open a web browser and enter the URL of the SAP Cloud Integration tenant worker node that was provided
in the activation email. Then add the path /cxf at the end.
2. In the web browser, click the certificate icon to see the certificate.
3. Under the Certification Path tab, select the root certificate, for example, the Baltimore CyberTrust Root and
click View Certificate.

4. Under the Details tab, click Copy to File... and OK.

5. Select Base-64 encoded X.509 (.CER) and then click Next.
6. Choose the location of the file and click Next.

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
Setting Up Secured Communications Across the Landscape PUBLIC 11
 You'll use this certificate file later on when you import the root certificate.
7. Click Finish.

5.1.2  Import Root Certificate

Add the root certificate to the certificate list in SAP Marketing.

Prerequisites

Verify if your SAP Marketing application has the related root certificate by transaction STRUST. Check the PSE
or PSEs that you have, either SSL client SSL Client (Anonymous) PSE, SSL client SSL Client (Standard)
PSE, or both, to see if the related root certificate is listed under the Certificate List of relevant PSEs. If it isn't
listed there, do the following steps:

Procedure

1. Select the PSE where you would like to add the root certificate. If you have both the Standard and
Anonymous PSE, you must import the certificate into both of them.

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
12 PUBLIC Setting Up Secured Communications Across the Landscape
 2. In the Certificate section, import the root SSL certificate you downloaded in the previous step Download
Root SSL Certificate [page 11].

3. Click Add to Certificate List and save your changes.

5.1.3  Download SSL Certificate

Download SAP Gateway's client server certificate from the SSL Client Standard PSE in SAP Marketing.

Procedure

1. In transaction STRUST, select node SSL client SSL Client (Standard).

2. In the Own Certificate section, select the SSL certificate and export the certificate.
3. Select a location on your machine to download the certificate.
4. Select the Base64 file format, and save the client certificate as crt file.

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
Setting Up Secured Communications Across the Landscape PUBLIC 13
5.1.4  Set Up the Certificate-to-User Mapping in the SAP
Cloud Integration Tenant

Use certificate-to-user mapping to authenticate the request to an iFlow in the SAP Cloud Integration tenant.

Procedure

1. Go to the Web UI of your SAP Cloud Integration tenant.

2. Choose Monitor and choose the Manage Certificate-to-User Mapping tile.
3. Choose Add, then add the following information:
a. User Name: Choose an SAP Cloud Integration user that has the following authorizations assigned:

• Application: <tenantID>iflmap
• Role: ESBMessaging:send
b. Certificate: Choose the SSL certificate you downloaded from SAP Marketing. For more information,
see Download SSL Certificate [page 13].

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
14 PUBLIC Setting Up Secured Communications Across the Landscape
5.2 Setting Up Secured Communication Between SAP
Cloud Integration and Google

5.2.1  Download Certificates from Google Trust Services

Download the certificates from Google to set up a secure connection to Google services.

Procedure

1. Download the following file [Link] .

 Note

You can find the repository of Documentation and Certificates from Google Trust Services in the
following location: [Link] .

For more information, see: [Link]

Google has published their strategy on their Certificate Authority and Certificates in the following blog:
The Foundation of a More Secure Web .

2. Save the file locally.

5.2.2  Import the Certificates

Import the certificates into a local Keystore.

Prerequisites

You have done the following:

• Installed the KeyStore Explorer software.

• Downloaded the pem file from Google Trust Services.

Context

We recommend deploying all of the certificates listed in the [Link] file in your SAP
Cloud Integration tenant.

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
Setting Up Secured Communications Across the Landscape PUBLIC 15
Procedure

1. Open KeyStore Explorer.

2. Create a new local KeyStore and select the JKS type.

3. Choose the Examine Examine File menu option to open the [Link] file that you saved.

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
16 PUBLIC Setting Up Secured Communications Across the Landscape
 A popup titled Certificate Details for file '[Link]' displays all certificates listed in the [Link] file.
4. Add the certificates one at a time by clicking on the certificate name, then click on Import to bring the
certificate into the keystore.

Ensure that each certificate in the hierarchy has a different alias during the import process. Otherwise, the
certificates with the same alias will be overridden and you won't have all of the certificates in the keystore.

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
Setting Up Secured Communications Across the Landscape PUBLIC 17
5. Click OK once you have imported all of the certificates from the certificate hierarchy.
6. Save the keystore with a password. You need this password to import the keystore into your SAP Cloud
Integration tenant.

5.2.3  Import the Local KeyStore

Import the local keystore you created into the tenant keystore.

Procedure

1. Navigate to the Web UI of your SAP Cloud Integration tenant, for example <[Link]
itspaces>.
2. From the left-hand menu, select Monitor.

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
18 PUBLIC Setting Up Secured Communications Across the Landscape
 3. Under Manage Security, you see the Keystore tile, which informs you about the number of keys and
certificates available in the tenant keystore.
4. Click the Keystore tile and then click Add.
5. Select the local keystore you created and enter the password of your local keystore.

 Note

Ensure that the selected action is Add. The Replace and Overwrite actions will overwrite existing
entries.

6. Deploy the keystore.

A confirmation message summarizing the added entries appears.

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
Setting Up Secured Communications Across the Landscape PUBLIC 19
6 Setting Up SAP Cloud Integration

SAP Cloud Integration must be set up in order to establish a connection between SAP Marketing and Google
Ads.

Before configuring your integration, you must have an SAP Cloud Integration tenant and account. For more
information, see the SAP Cloud Integration onboarding guide.

 Caution

Maintain an e-mail in your tenant to receive e-mails about important information and updates.

To set up SAP Cloud Integration, you must do the following:

1. Create an SAP Support Ticket [page 20]

Create an SAP Support ticket to allow your SAP Cloud Integration tenant to send a request to Google
Ads using the SAP central tenant.
2. Copy the Integration Package to your Workspace [page 22]
Copy the integration package to your workspace and deploy its integration flows.
3. Set Up the OAuth Authorization Code Grant [page 22]
Set up OAuth authorization code grant to allow SAP Cloud Integration to manage the Google OAuth
tokens. The tokens are used to authenticate the communication from SAP Cloud Integration to the
Google Ads API.
4. Set Up the Integration Flows [page 24]
Configure the integration flows to manage the mapping on requests and responses between SAP
Marketing services and the Google Ads API.

6.1 Create an SAP Support Ticket

Create an SAP Support ticket to allow your SAP Cloud Integration tenant to send a request to Google Ads using
the SAP central tenant.

Prerequisites

1. You must have an SAP Cloud Integration tenant and account.

2. Choose the SAP Cloud Integration user that you're going to use to connect to the SAP central tenant.
The SAP central tenant uses the default SAP identity provider (IDP) with basic authentication for the
incoming request. If you’re using a custom identity provider (IDP) in your SAP Cloud Integration tenant,
you must choose a user ID from the default SAP IDP for the support ticket.

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
20 PUBLIC Setting Up SAP Cloud Integration
  Note

We recommend using a dedicated user for communicating with the central tenant. For security
reasons, we don't recommend using your developer or admin user for your connection to the SAP
central tenant.

The same user can be used in both your quality and productive tenants. You only need to request
access to the SAP central tenant once for that user.

Procedure

1. Use the following the link to open an incident ticket to SAP Support to grant access to your dedicated user:
Contact SAP Support .
2. Enter the following information:

Field Name Entry Value

Component CEC-MKT-SEM-PSI (Paid Search Integration)

Subject Grant user access to the central tenant

Description Provide the user ID of the SAP Cloud Integration user,

for the connection to the SAP central tenant.

 Note

A user ID starts with the letter P, C, or S, and is fol­

lowed by a number.

No additional information about your SAP Cloud

Integration user or tenant is needed.

Priority Medium

After creating the incident, you can continue to set up the configuration by working through the other
steps. However, before you start testing the integration scenario from the Campaigns application, the
incident should be processed and have the status Solution Provided.

Task overview: Setting Up SAP Cloud Integration [page 20]

Next task: Copy the Integration Package to your Workspace [page 22]

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
Setting Up SAP Cloud Integration PUBLIC 21
6.2 Copy the Integration Package to your Workspace

Copy the integration package to your workspace and deploy its integration flows.

Procedure

1. Go to the SAP Cloud Integration tenant Web UI and search for Google Ads in Discover.
2. Click the Google Ads Integration with SAP Marketing Cloud/SAP Marketing tile.
3. Click Copy.

Task overview: Setting Up SAP Cloud Integration [page 20]

Previous task: Create an SAP Support Ticket [page 20]

Next task: Set Up the OAuth Authorization Code Grant [page 22]

6.3 Set Up the OAuth Authorization Code Grant

Set up OAuth authorization code grant to allow SAP Cloud Integration to manage the Google OAuth tokens.
The tokens are used to authenticate the communication from SAP Cloud Integration to the Google Ads API.

Context

The Google Ads API requires OAuth 2.0 authentication for all incoming requests. Each call to the Google Ads
API from SAP Cloud Integration must contain a valid OAuth token.

 Note

We don’t support Google OAuth token sharing between multiple SAP Cloud Integration tenants. Therefore,
if you're planning to use the same Google Ads Manager Account for the Google Ads integration in your
quality (Q) and production (P) SAP Marketing systems, the OAuth code grant needs to be configured in
each SAP Cloud Integration tenant separately.

For a more information about the options for setting up your landscape, see Setting Up Google Ads [page
5].

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
22 PUBLIC Setting Up SAP Cloud Integration
Procedure

1. Create security material for the OAuth Authorization Code under Manage Security Material.

Field Name Entry

Name GoogleAdsOAuth

Description <add a description >

Provider Generic

Authorization URL [Link]

prompt=consent&access_type=offline

Token Service URL [Link]

Client ID The Client ID you obtained when setting up Google OAuth Client.

Client Secret The Client Secret you obtained when setting up Google OAuth Client.

Scope [Link]

 Note

For Google Cloud Platform projects with the OAuth consent screen configured for user type External,
your refresh token expires in 7 days. You need to reauthorize the OAuth 2.0 authorization code weekly
to keep your OAuth tokens up to date. However, if your app verification is complete, any tokens
issued after the verification don't expire. For more information about app verification, see OAuth API
Verification FAQs .

2. Trigger the Authorize action on the OAuth authorization code.

The Google identity service prompts you with a login screen and requests the user's approval to use the
Google app.
• Use the email address associated with your Google Ads manager account to log in.
• If your Google app is still in test mode with an external user type, you see a message about the app
not being verified by Google. You can ignore the message and continue. For more information, see
Unverified Apps .
• The user gives the approval, and the initial token exchange is handled and stored by the SAP Cloud
Integration tenant.

Task overview: Setting Up SAP Cloud Integration [page 20]

Previous task: Copy the Integration Package to your Workspace [page 22]

Next task: Set Up the Integration Flows [page 24]

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
Setting Up SAP Cloud Integration PUBLIC 23
6.4 Set Up the Integration Flows

Configure the integration flows to manage the mapping on requests and responses between SAP Marketing
services and the Google Ads API.

Procedure

1. Navigate to the Web UI of your SAP Cloud Integration tenant.

2. Go to the Design page and navigate to the Google Ads Integration with SAP Marketing Cloud/SAP Marketing
package.
3. Deploy the Google Ads API Common script collection.
4. Configure and deploy the Read OAuth Token in Cloud Integration iFlow by entering true in the
USE_OWN_GOOGLE_OAUTH_CLIENT parameter.
5. Configure and deploy the following iFlows by entering your 10-digit Google Ads Manager Account ID (MCC)
in the ROOT_MCC_ACCOUNT parameter. The format is: XXX-XXX-XXXX and includes the dashes:
• Create Customer List in Google Ads
• Read Accounts from Google Ads
• Read Campaign Performance Report from Google Ads
• Read Campaigns from Google Ads

Task overview: Setting Up SAP Cloud Integration [page 20]

Previous task: Set Up the OAuth Authorization Code Grant [page 22]

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
24 PUBLIC Setting Up SAP Cloud Integration
7 Support

Once the setup is complete, you can monitor messages. If you run into a problem, you can contact support.

If you suspect a problem with an iFlow, check the message monitoring.

To report a technical problem, go to SAP Support Portal at SAP Support . Use the component CEC-MKT-
SEM-PSI.

Message Monitoring [page 25]

Check iFlow errors or runtime information to investigate issues with iFlows.

FAQs [page 27]

Provides answers to frequently asked questions about the integration between SAP Marketing and
Google Ads.

Integration Package Updates [page 30]

Verify follow-up actions required for specific versions before updating your integration package.

7.1 Message Monitoring

Check iFlow errors or runtime information to investigate issues with iFlows.

You can use the following methods to investigate possible issues you are having with your iFlows:

• Check iFlow Errors in Attachments [page 25]

• Check Runtime Information [page 26]

7.1.1  Check iFlow Errors in Attachments

You can find detailed information about your iFlow execution under Monitor Message Processing in the
Operations View page in your SAP Cloud Integration tenant.

Procedure

Under Monitor Message Processing, choose the message related to the iFlow you're investigating.
If exceptions occur during runtime, the Attachments tab is visible with a detailed log as text files. You can look
for files named XXX_Response_Body and XX_Response_Header for more information.

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
Support PUBLIC 25
Example

The following image shows an example of a completed message that contains a text file named
HTTP_Receiver_Adapter_Response_Body.

Related Information

Check Runtime Information [page 26]

Message Monitoring [page 25]

7.1.2  Check Runtime Information

Collect runtime steps of iFlows under Message Monitoring for debugging purposes.

Procedure

Under Manage Integration Content, set the Log Level to Trace for each iFlow that you want to debug.

Results

All runtime information is collected for the iFlow for 1 hour. Review the runtime information for the iFlows to
identify the errors.

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
26 PUBLIC Support
Example

The following image shows where to set the Log Level to Trace for an iFlow.

Related Information

Check iFlow Errors in Attachments [page 25]

Message Monitoring [page 25]

7.2 FAQs

Provides answers to frequently asked questions about the integration between SAP Marketing and Google Ads.

The following table lists frequently asked questions and their answers.

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
Support PUBLIC 27
FAQs
Question Answer

In my Google Ads campaign in SAP Marketing, There are 2 types of accounts in Google Ads:
why aren't any accounts displayed in the value
help for Google Ads Account? 1. Google Ads manager accounts
The manager accounts are used to view and manage multiple Google
Ads accounts and manager accounts.
2. Google Ads accounts
Google Ads accounts are used for managing Google Ads campaigns.

In SAP Marketing, Google Ads manager accounts aren't displayed in the

value help for Google Ads Account.

Check your account setup in Google Ads to ensure that all of the related
accounts are under the same manager account.

SAP Marketing assumes that all Google Ads accounts that you want to
access in the Campaigns application are managed by a single manager
account in Google Ads. You use this manager account as the root man­
ager account when you configure the integration package in SAP Cloud
Integration.

 Note

Since each customer's needs are different, SAP Marketing support

doesn't provide guidance on how to manage your Google Ads ac­
counts.

Refer to Google support for more information:

• For information about Google Ads manager accounts, see About

Google Ads Manager Accounts .
• For information about how to link an existing Google Ads account
to a manager account, see  Link Accounts to Your Manager Ac­
counts .

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
28 PUBLIC Support
 Question Answer

In my Google Ads campaign in SAP Marketing, Ensure that your Google Ads account is whitelisted by Google Ads.
why isn't my target group transferred to
Google Ads after I release my campaign?
 Note

Since November 2018, your Google Ads account must be whitelisted

before you can upload customer lists. For more information about this
requirement, see Update to Customer Match Requirements .

When you release a campaign, errors can occur when SAP Cloud
Integration communicates with Google Ads. These errors can block the
transfer of the target group. In most cases, the error is because the Google
Ads account isn't whitelisted by Google Ads.

The following steps identify how to confirm the cause of the error:

1. First, in SAP Marketing , check the campaign execution in the

Campaigns app. If Execution shows Error Occurred, check the
execution logs by choosing the View Logs button in the campaign. The
logs identify where the error occurred.
2. Review the message logs for the iFlow Create Customer List in Google
Ads. For more information about how to view the error details, see
Check iFlow Errors in Attachments [page 25].
3. Check the HTTP_Receiver_Adapter_Response_Body files and look for
any API errors.
4. Cross-check any API errors that you find against the UserListErrors on
the Google developer website at [Link]
gle-ads/api/reference/rpc and follow their recommendations.

Otherwise, contact SAP support. For more information, see Support [page
25].

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
Support PUBLIC 29
Question Answer

Why did the integration between SAP If the integration was working and it suddenly stops, it could be an authen­
Marketing and Google Ads stop working when
tication problem.
it was working before?
To confirm if the problem is related to the certificates, do the following:

 Note

If your OAuth consent screen is configured with internal user type,

then the following information isn't applicable. Please find out the er­
ror details and share the information when contact SAP support for
further assistance.

Look for the failed messages of related iFlows in Message Monitoring, and
check if error details contain information similar to “Access token request
via refresh_token grant type for OAuth2 Authorization Code credential
'GoogleAdsOAuth' failed after 5 retries”. If the error is identified, it's likely
that your Google Cloud Platform project with an OAuth consent screen is
configured for an external user type and a publishing status of "Testing".
The issued refresh token expires in 7 days and you need to reauthorize the
OAuth authorization code. To obtain a long-term OAuth token in this case,
your Google app needs to have the publishing status “In production”.

For more information, please refer to Google's support documents about

OAuth token expiration at Refresh Token Expiration and about publish­
ing status at Setting up your OAuth Consent Screen. .

If the problem persists, contact SAP Support. For more information, see
Support [page 25].

7.3 Integration Package Updates

Verify follow-up actions required for specific versions before updating your integration package.

If you're configuring the integration for the first time, ignore this topic and follow the integration setup
procedure in this guide, starting with Setting Up Google Ads [page 5].

If you're already using the Google Ads Integration with SAP Marketing Cloud/SAP Marketing integration
package and plan on updating to a newer version, see the relevant SAP Notes and blog post for information
about which actions to take before and after updating your integration package.

SAP Notes for Package Update Follow-Up Actions

Integration Package Version SAP Note

3.0.1 3128556

3.1.0 3255040

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
30 PUBLIC Support
Blog Post

For more information about how to prepare and complete the integration package update to version 3.1.0, see
the blog post Google Ads Integration with SAP Marketing Cloud or SAP Marketing - Integration package update
to version 3.1.0 .

 Note

The blog post isn't part of the official documentation of SAP Marketing.

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
Support PUBLIC 31
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:

• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using
such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.

Integrating SAP Marketing with Google Ads via SAP Cloud Integration
32 PUBLIC Important Disclaimers and Legal Information
Integrating SAP Marketing with Google Ads via SAP Cloud Integration
Important Disclaimers and Legal Information PUBLIC 33
[Link]/contactsap

© 2022 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see [Link] for

additional trademark information and notices.

THE BEST RUN