# Compare tea and coffee search interest in the US

**Use case:** 

Compare tea and coffee on a shared Google Trends timeline for the United States. Use the same 12-month comparison group to compare relative scores.

## Input

```json
{
  "mode": "compare",
  "keywords": [
    "coffee"
  ],
  "comparisonGroups": [
    {
      "label": "Tea and coffee",
      "keywords": [
        "tea",
        "coffee"
      ]
    }
  ],
  "geographies": [
    "US"
  ],
  "timeWindows": [
    "today 12-m"
  ],
  "surfaces": [
    "timeline"
  ],
  "category": 0,
  "property": "web",
  "language": "en-US",
  "timezoneOffsetMinutes": 0,
  "maxAnalyses": 6,
  "maxRunSeconds": 180,
  "concurrency": 1,
  "requestDelayMillis": 1000,
  "maxRetries": 2,
  "requestTimeoutSeconds": 30,
  "reviewRelatedQueries": false,
  "planOnly": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

## Output

```json
{
  "keyword": {
    "label": "Keyword"
  },
  "geography": {
    "label": "Country / region"
  },
  "time": {
    "label": "Requested period"
  },
  "effectiveTime": {
    "label": "Effective timeline period"
  },
  "analysisStatus": {
    "label": "Extraction"
  },
  "qualityState": {
    "label": "Timeline quality"
  },
  "latestCompleteInterest": {
    "label": "Latest complete index",
    "format": "number"
  },
  "latestCompleteDate": {
    "label": "Latest interval start (UTC)",
    "format": "date"
  },
  "recentChangePercent": {
    "label": "Descriptive change (%)",
    "format": "number"
  },
  "changeLabel": {
    "label": "Change period"
  },
  "coverageLabel": {
    "label": "Returned interval coverage"
  },
  "regionMetricLabel": {
    "label": "Regional metric"
  },
  "topRegionsText": {
    "label": "Regional highlights"
  },
  "risingQueriesText": {
    "label": "Rising leads for review"
  },
  "queryReviewEnabled": {
    "label": "Lexical review enabled",
    "format": "boolean"
  },
  "risingReviewFlagsText": {
    "label": "Literal query-review facts"
  },
  "qualityNotesText": {
    "label": "Quality notes"
  },
  "metricNotesText": {
    "label": "Metric notes"
  },
  "analysisId": {
    "label": "Analysis / comparison identifier"
  },
  "keywords": {
    "label": "Terms in this analysis"
  },
  "captureScope": {
    "label": "Timeline scale scope"
  },
  "sourceUrl": {
    "label": "Timeline source context",
    "format": "link"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The Google Trends API: Bulk Keyword Trends Export Actor is ready to run with the inputs already set for "Compare tea and coffee search interest in the US". [Sign up or log in](https://console.apify.com/create-task-from-example/IiOPfygoUgFn3cYRa) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Compare tea and coffee search interest in the US" task

The Google Trends API: Bulk Keyword Trends Export Actor will start running based on the input automatically. You can also change all the input fields, like research mode, keywords or google topic ids, and more, to match your specific use case.

### 3. Receive the "Compare tea and coffee search interest in the US" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as keyword, country / region, requested period, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Compare tea and coffee search interest in the US" task via API](https://apify.com/whoareyouanas/google-trends-batch-research.md).

## About this Actor

This example demonstrates how to use [Google Trends API: Bulk Keyword Trends Export](https://apify.com/whoareyouanas/google-trends-batch-research.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/whoareyouanas/google-trends-batch-research.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/whoareyouanas/google-trends-batch-research.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).
