Google Ads Competitor Research API: Activity & Titles
Search available advertisers or domains, reuse an exact returned ID, then inspect supported weekly activity, title or image records. The JSON supports evidence-based research without exposing ad spend or conversions.
Find an ID first · Use the action that matches your task
https://api.goanyapi.com/api/v1/ads-statistics?action=advertiserSearchRun a request to see the visual result
The response is organized into metrics, lists and tables that match the JSON on the right.
Run a request to see the response here
Fill in the demo parameters to preview an example response for free. Sign in to send live requests with your own parameters.
Start with an exact advertiser ID
The first request identifies a candidate advertiser. Follow-up statistics actions require the exact returned ID and their own parameters.
GET https://api.goanyapi.com/api/v1/ads-statistics?action=advertiserSearch&keyword=ai
Authorization: Bearer YOUR_API_KEYThe response below is described by paths because real matches vary by query. This request is an example.
Key response paths
data.result[].id- The exact numeric identifier to pass as advertiserId to advertiserStatistics.
data.action- The action executed for this response.
data.costCredits- Credits deducted for this action under the current configuration.
What the data can tell you
Find an ID first · Use the action that matches your task
Find the research subject
Use advertiserSearch or domainSearch to resolve an entity first. A matching result contains the numeric id needed by follow-up statistics actions; do not infer an ID from a brand name or mix advertiser IDs with host IDs.
Inspect weekly activity
Request weekly advertiser or domain activity within the documented date window. Only active weekly rows are returned, so missing periods are not a complete series of zero spend or zero ads.
Explore titles and images
Choose a title or image action for the question at hand. Keyword title search, domain titles, title countries and image records have different prerequisites; preserve the exact title and host ID returned by the preceding step.
From a question to a useful result
A practical workflow using the available data.
Resolve the advertiser or domain
Start with advertiserSearch or domainSearch and inspect data.result[].id. Use the exact matching id as advertiserId or hostId in the corresponding follow-up action.
Choose a focused date range
Set a focused date range for a weekly statistics or title query. For advertiserStatistics and domainStatistics, stay within the documented 48-period limit and narrow any oversized response.
Build a research brief
Build a brief around observable activity and title records, keeping entity IDs, query dates and action names. Treat the output as research evidence rather than a measure of spend, clicks or ROI.
Google Ads Competitor Research API FAQ
Questions about fit, interpretation and integration.
This is a GoAnyAPI competitor-research endpoint. It does not manage your Google Ads account or return Keyword Planner metrics. Use its documented actions to look up advertisers, domains, activity periods and creative records.
Find an advertiser with advertiserSearch or a domain with domainSearch. Reuse its returned id in the corresponding statistics action and provide a start and end date.
titleSearch returns domain summaries for matching titles. googleAdsTitleSearch returns matching title-and-host records. Choose the action based on the result you need.
Use domainTitleCountries with a host ID, dates and the exact title returned by the title workflow. Keep the title and host from the same record rather than mixing identifiers.
Weekly statistics support the documented period and row limits. Narrow oversized ranges. Only active periods are returned; missing rows are not a complete time series of zero activity.
No. The data does not provide spend, CTR, sales or ROI. Use activity and creative patterns as research signals, not performance proof.
Rates depend on the selected action and current configuration. Check the Tester or Docs before each step. Discovery and follow-up queries are separate requests; do not assume one charge covers an entire research workflow.
Use the REST endpoint from Python or Node.js with a GoAnyAPI key and the documented action parameters. An AI assistant can use the GoAnyAPI MCP tool only after it is connected and available. Your workflow must preserve returned IDs, dates and action names when planning follow-up calls.
Find the right advertising workflow
Use discovery before statistics, or open the focused title page.