Scribd
Upload
25 views1 page

Google Ads API Internal Tool Overview

The document outlines the design of an internal analytics tool for a mobile game studio that utilizes the Google Ads API to optimize ad campaign performance. The tool will retrieve campaign cost and conversion data to calculate Return on Ad Spend (ROAS) and identify high-value user cohorts for targeted advertising. All data will be securely stored and used internally, with no personal identifiable information (PII) involved.

Uploaded by

Nguyen Van Chung
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
25 views1 page

Google Ads API Internal Tool Overview

The document outlines the design of an internal analytics tool for a mobile game studio that utilizes the Google Ads API to optimize ad campaign performance. The tool will retrieve campaign cost and conversion data to calculate Return on Ad Spend (ROAS) and identify high-value user cohorts for targeted advertising. All data will be securely stored and used internally, with no personal identifiable information (PII) involved.

Uploaded by

Nguyen Van Chung
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Google Ads API - Internal Tool Design Overview

1. Overview

We are a mobile game studio that runs ad campaigns on Google Ads for in-house developed games. To optimize

budget allocation and improve ROAS (Return on Ad Spend), we are building an internal analytics tool to retrieve

campaign cost and conversion data through the Google Ads API.

2. Purpose of API Usage

- Retrieve ad cost (`metrics.cost_micros`)

- Fetch conversions and associated GCLID (`[Link]`, `metrics.conversions_value`)

- Match data with Firebase to calculate ROAS per user

- Identify high-value cohorts to create audiences for targeting

This tool is purely for internal use and will not be exposed to external clients.

3. API Endpoints and Scope

We will primarily use the `searchStream` endpoint to query data from `segments` and `metrics` resources. The main

fields include: `[Link]`, `[Link]`, `[Link]`, `metrics.conversions_value`,

`metrics.cost_micros`, `customer.descriptive_name`.

4. Data Privacy

All data collected via API will be securely stored and used only by internal analytics and UA team members. No user PII

is transmitted or stored.

You might also like