Applicable to SA3.0.4 and above.
This feature is controlled by a separate license. Please contact your account manager if you require it.
If your app is running overseas ads to acquire new users and you want to obtain aggregated ad data (such as impressions, clicks, and sales) from overseas advertising platforms to the Sensors Data platform, you can use this function.
Function Overview
It supports integration with Google Ads, enabling the retrieval of ad-level data such as impressions, clicks, and sales via its open API. The retrieved data is then stored in Sensors Analytics as events, allowing for analysis within the analytics model. It can also be correlated with user behavior data in subsequent stages of the process for further analysis.
|
interface
|
Data granularity
|
Data update frequency
|
Attribution
|
cost
|
exhibit
|
Click
|
Transformation
|
|---|---|---|---|---|---|---|---|
| Reporting API | Aggregated data | Tianliu | ✅ | ✅ | ✅ | ✅ |
Function Entry
Channel Tracking > Third-Party Data Integration > Advertising Ecosystem > Google Ads
Access Instructions
Google Ads Data Explanation
It supports fetching ad data for four ad tiers via the Google Ads API. For details, please refer to the official documentation: Google Ads API Official Documentation
It includes 4 built-in templates, covering commonly used advertising metrics and dimensions.
- Ad Group Ad Template: Ad data at the Ad tier. The original content can be found in the official documentation . The metrics and dimensions obtainable through this template are as follows:
| metrics |
|
| group by |
|
- Campaign Template: This template displays ad data at the Campaign level. The original content can be found in the official documentation . The metrics and dimensions obtainable through this template are as follows:
| metrics |
|
| group by |
|
- Geographic View Template: This template provides advertising data at the Geographic level. The original content can be found in the official documentation . The metrics and dimensions obtainable through this template are as follows:
| metrics |
|
| group by |
|
- Conversion Action Template: An ad template for conversion behavior. The original content can be found in the official documentation . The metrics and dimensions obtainable through this template are as follows:
| metrics |
|
| group by |
|
Preparation before access
You need to complete authorization and authentication with Google Ads before you can obtain advertising data through the Google Ads API. For details, please refer to the official documentation: Google Ads API Official Documentation
To make a Google Ads API call, you should have the following details.
Google Ads Manager account : You need a Google Ads Manager account to apply for the Google Ads API.
Developer Token : This token allows your app to connect to the Google Ads API. Each developer token is assigned an API access level, which controls the number of API calls you can make per day and the environments in which you can make those calls. Obtaining a Developer Token: A developer token is a 22-character alphanumeric string that allows your app to connect to the Google Ads API. After Google assigns you a token, you can view it or create a new one on the API Center page of your Google Ads Manager account.
OAuth 2.0 Credentials (Client & Secret) : The Google API Console project generates OAuth 2.0 credentials for your app. Your app then uses these credentials to authenticate users and obtain their authorization to manage their Google Ads accounts. This authorization is later used by your app to make API calls to the Google Ads accounts. The project also enables the API to accept calls.
Google Ads account (Advertiser account) : This is the account you will be making API calls to. You need to have permissions for the account, such as the ability to retrieve reports or modify campaigns. You also need the 10-digit account number of the account you are making API calls to. In the Google Ads web interface, this value is displayed as 123-456-7890. This account number is passed as a parameter to the Google Ads API call, but without the hyphen: 1234567890.
| step | content | illustrate |
| first step | Create a Google Ads Manager Account | See official documentation for reference. |
| Step 2 | Apply for a Developer Token with your Google Ads Manager account |
Log in to your Google Ads account using your Google Ads Manager account, select Admin in the left navigation pane, and then select API Center. Fill out the form and complete the Developer Token application.
|
| Step 3 | Obtain application credentials, namely Client ID and Secret |
Log in to Google Cloud Platform. 1. Create a project using the Create Project function. Then select API & Services, then select Enable APIs and services. After navigating to the API Library, search for Google Ads and enable it.
2. In the left navigation, go to Credentials, select Create credentials, and choose OAuth client ID from the drop-down menu. You need to configure the Consent Screen first. Click Configure to go to the Branding page, and then click Get started to begin configuration.
3. When creating a Client, select Web application as the Application Type and fill in the Authorized redirect URIs. You can fill in any address here first, and then replace it with the address provided in the Sensors Data product later.
4. Click Audience in the left navigation bar, then click Publish App.
|
| Step 4 | Grant Google Ads API permissions |
After successfully creating the client ID, navigate to Data Access in the left navigation, add the scopes that the client is allowed to access, search for Google Ads API, and add it.
|
| Step 5 | Link your Google Ads Manager account with your Google Ads advertiser account |
Log in to Google Ads with your manager account, select Accounts in the left navigation bar, then select Sub-account settings, click +, select link existing account, fill in the information, and a verification link will be sent to your Google Ads account.
Log in with your Google Ads account, select Admin in the left navigation bar, then select Access and security, then the Managers tab. You will see the verification request sent in the previous step; select Accept. The Manager will then be able to access this ad account.
|
Configure Google Ads integration solution
The configuration mainly includes the following three parts:
1. Basic Information of the Plan
2. Authorization Configuration
The fields entered in this section are primarily used for authentication with Google Ads and to specify the range of ad accounts to be retrieved. Please refer to the "Preparation Before Integration" section in the previous paragraph to obtain the relevant fields from the Google Ads platform.
It supports pulling data from up to 100 Google Ads accounts. If a user has more than 100 Google Ads accounts, multiple pull plans can be created.
Client IDs must be unique across all platforms. If a duplicate message is displayed, check if the same Client ID exists in different projects.
During secondary editing, the Client ID cannot be modified. When modifying other content and saving, the entered content will be validated. For example, if the entered Developer Token does not have permission to access the Customer ID, an error will occur.
3. Data retrieval configuration

After clicking "Confirm Creation," you need to complete the authorization process with Google Ads for the plan to be created successfully. The authorization process includes the three steps shown in the image below.
Clicking the blue "Go to Authorization" button will redirect you to the Google Ads authorization page. Log in to your Google account. (Note that you need to log in with the Google account that created your Google Manager account). Because the authentication process required by Google was not completed when publishing the app in the Google Cloud Console, a warning message will appear indicating that the app is insecure. Click "Advanced" and select "Continue."
After completing the above steps, select "Authorization Completed" in the Sensors Data pop-up window. If the authorization fails, an error message will be displayed via an Error Code.
Once the plan is successfully created, Google Ads data will be retrieved daily according to the template content.


Data backtracking
Google Ads data retrieval solution supports "data backtracking," allowing users to select a time period of up to 180 days to retrieve ad data within that period.
Data import instructions
The retrieved Google Ads and Meta Ads data will be uniformly stored in the database as events. The original fields will be standardized and stored as attributes starting with "sensors_ad".
Note: This data will be included in the cluster's event consumption.
This part of the event will use a fixed value as its user identifier, which can be understood as a virtual user identifier.
The inbound events corresponding to different templates are as follows:
Ad Group Ad Template: google_ads_ad_group_ad
Campaign template: google_ads_campaign
Geographic View template: google_ads_geographic
Conversion Action template: google_ads_conversion_action
The following lists some common raw data and their corresponding database attributes:
| Original field | Input fields |
|---|---|
| customer.id | sensors_ad_customer_id |
| customer.time_zone | sensors_ad_customer_timezone |
| customer.currency_code | sensors_ad_customer_currency |
| media _source | sensors_ad_media_source |
| campaign.id | sensors_ad_campaign_id |
| campaign.name | sensors_ad_campaign_name |
| ad_group.id | sensors_ad_ad_group_id |
| ad_group.name | sensors_ad_ad_group_name |
| ad_group_ad.ad.id | sensors_ad_ad_id |
| ad_group_ad.ad.name | sensors_ad_ad_name |
| segments.date | sensors_ad_segments_date |
| geographic_view.country_name | sensors_ad_country |
| metrics.all_conversions | sensors_ad_metrics_all_conversions |
| metrics.impressions | sensors_ad_metrics_impressions |
| metrics.clicks | sensors_ad_metrics_clicks |
| metrics.cost_micros | sensors_ad_metrics_cost |
Analyze in the analytical model
After storing Google Ads data as events, you can select the corresponding event in Event Analysis to analyze metrics such as Google Ads impressions, clicks, and spending.

Permissions
Administrators have the default privilege to configure Google Ads plans. They can also assign plan configuration and viewing permissions to regular users.