Google Ads API Use at Global Signal

PRODUCT AND PURPOSE

Evidence for a decision—not a substitute for one

This proposed integration is intended to help merchants and marketing teams define the products or services they may advertise, identify relevant keyword themes, and prepare evidence-based planning for a future Google Search campaign.

If Basic Access is approved, Google Ads API data would be used only in the intended production workflow to help merchants research keywords and prepare prospective Google Search campaigns. The merchant would independently review the results and decide whether and how to create a campaign in Google Ads.

DATA REQUESTED

Limited to Google Ads keyword-planning metrics

• Keyword ideas related to a prospective Google Search campaign
• Historical search volume for the United States and English language
• Competition levels
• Bid estimates

Results are labeled with the relevant product or category, keyword or keyword group, geographic and language market, metric type, and collection or verification time. Missing fields remain visibly unavailable.

RESEARCH WORKFLOW

How the intended signal would fit into Global Signal

1. DefineIdentify the product or service and United States audience for a prospective Google Search campaign.
2. SeedPrepare relevant keyword themes from the merchant's advertising offer.
3. PlanRequest keyword ideas, historical metrics, competition levels, and bid estimates.
4. ReviewLet the merchant independently review keyword-planning results and other available evidence.
5. DecideThe merchant would decide whether and how to create a future campaign in Google Ads.

SECURITY AND ACCESS

Credentials remain server-side

If Basic Access is approved, credentials for the intended production workflow would be stored as server-side environment secrets. Developer tokens, OAuth credentials, and other API credentials would never be exposed to users or third parties, embedded in client-side code, or included in public reports.

Operational scope

For this proposed integration, only authorized Global Signal staff would be able to initiate server-side Google Ads API requests for the intended production workflow. External users and third parties would not be able to connect their own Google Ads accounts, access the developer token or OAuth credentials, or manage third-party Google Ads accounts.

Administrative collection functions would be access-restricted. Operational logs would be designed not to record access tokens, developer tokens, client secrets, or personal information.