Search Terms

When to use this node

Use the Search Terms node for tasks such as:

Audit cross-channel search coverage: find queries you're paying for in paid search that you already win in AI answers, and the reverse
Identify negative keyword opportunities: flag high-cost, low-CVR queries that look off-intent
Build automated weekly paid search digests: pull the last seven days of search term performance and highlight movers
Complement Profound AEO data: layer paid query intent on top of AI visibility data in a single workflow

Node configuration

Google Integration (required)

Select a previously connected Google account, or click + Add integration and follow the prompts to connect one. This is a one-time setup. Once you add an integration, it's available in all future sessions until you remove it in Account Settings > Integrations.

Google Ads Account (required)

Select the Google Ads customer account from the dropdown. The picker handles both Manager accounts and sub-account selection.

Campaigns

Select the ad campaigns from the dropdown. To include every active campaign, leave the field empty.

Ad Groups

Select the ad groups from the dropdown. To include every ad group within selected campaigns, leave the field empty. To see the ad group options in the dropdown, select at least one campaign in the Campaigns field.

Date Range (required)

Select the date range to pull search term performance over. Choose from available presets (today, yesterday, last 7 days, and others) or set a custom range.

Output Fields

Select the fields to include in the output. The options include metrics and campaign details, such as Impressions, Clicks, Conversions, Campaign Type, and Bid Strategy Type. To return output unfiltered, leave this field empty.

Output Label

Enter a descriptive label for this step's output, for example search_term_data or paid_search_last_7_days. The label becomes the variable name you reference in later nodes.

Output

The node outputs JSON data containing real search terms paired other data, such as the search query text, performance metrics (CTR, CPC, CPA, and so on), campaign and ad group details.

Pass the output to:

📄 Prompt LLM for AI analysis: negative keyword suggestions, intent categorization, budget reallocation recommendations, or cross-channel gap analysis
📄 Slack integration to push a weekly paid search summary to a channel
Google Sheets (Write Row) node to log performance data for ongoing tracking
Code node to write custom logic, extract variables, and pass results to a Conditional node for further branching

Example usage: Weekly paid search digest

Set up an Agent for your team to get a weekly performance summary report in Slack every Monday. Here is the example structure:

1. Search Terms node

Select your Google Integration and set Google Ads Account to your Google Ads account
Set Date Range to Last 7 days
Set Output label to search_term_data
Set Campaign, Ad Groups, Output Fields filters as needed

2. 📄 Prompt LLM node

Enter the prompt:

You are a paid search analyst. Review this week's {{search term data}}.

In plain English, summarize:
- Top 5 best-performing terms (high CVR, low CPA)
- Top 5 worst-performing terms (high spend, low CVR)
- 3 terms to consider adding as negatives

Keep the summary short and actionable.

Set Output label to weekly_summary

Check out our prompt best practices guide for the Prompt LLM node.

3. 📄 Slack integration - Slack Message node

Select the Slack workspace and channel to receive updates
Input the message text and use the weekly_summary variable in the Message field

Schedule the Agent to run weekly, for example every Monday at 9 AM.

Best practices

Scope by campaign and ad group

Pulling all search terms data from all campaigns and ad groups at once can return an unmanageably large dataset. Use the built-in campaign and ad group filtering to scope results before passing them to subsequent nodes.

Use 📄 List Campaigns node to discover the active campaign set first, map campaign names to IDs, or fan out the workflow across every campaign dynamically.

Pair with Profound data

Search Terms node is useful on its own, but combined with Profound data nodes, such as 📄 Visibility Score node, it becomes a cross-channel strategy tool. There's no clear way to tell which of your paid search terms are also surfacing in AI answers without connecting both data sources.

Use Agent Assistant

Working with both search term data and Profound AI visibility data can have a learning curve. Use Agent Assistant to build a working Agent faster, and then edit the Agent as needed to better match your use case.