Analyze your marketing data with Adzviser in Claude

After you connect Adzviser to Claude, you can ask Claude to retrieve reporting data from your Adzviser workspaces and turn it into summaries, comparisons, tables, and recommendations.

Before you start

Make sure the data sources you want to analyze are connected to an Adzviser workspace.
Open a Claude conversation, select the + button, open Connectors, and make sure Adzviser is enabled for that conversation.
If Claude repeatedly asks before using Adzviser, review the tool-permission setup.

Claude's Tool access mode controls which connectors are loaded into a conversation. Auto is a good default. If you want Adzviser available immediately in every turn of a specific conversation, choose Always available from + → Connectors → Tool access.

Start by choosing the right workspace

If you have more than one Adzviser workspace or account, begin with:

Use Adzviser to list my available workspaces and the data sources connected to each one. If more than one workspace contains the source I need, ask me which workspace to use before retrieving data.

Naming the workspace prevents Claude from choosing the wrong client, store, or ad account.

Write a complete reporting prompt

For the most reliable result, include:

Workspace and source — for example, your agency workspace and Meta Ads
Date range — use exact dates or ask Claude to confirm the dates for a relative period
Metrics — such as spend, clicks, conversions, ROAS, net sales, or sessions
Breakdowns — such as campaign, day, product, country, or source/medium
Comparison — previous period, target, or another channel
Output — table, executive summary, chart-ready data, or recommendations

Use this template:

Use Adzviser to analyze [data source] in the [workspace name] workspace for [start date] through [end date]. Retrieve [metrics] broken down by [dimensions]. Compare the result with [comparison period or source]. Return [output format], explain the largest changes, and state any data limitations or assumptions.

Example prompts

Paid media performance

Use Adzviser to analyze Meta Ads for the previous complete calendar month. First confirm the exact dates and workspace. Retrieve spend, impressions, clicks, CTR, CPC, conversions, CPA, and ROAS by campaign. Compare the results with the month before, flag changes greater than 20%, and return a concise performance table with recommended next steps.

Google Ads keyword analysis

Use Adzviser to find the best- and worst-performing Google Ads search keywords over the last 30 complete days. Include cost, clicks, conversions, conversion rate, CPA, and ROAS. Exclude rows with no spend, sort by cost, and explain the criteria used to classify performance.

Shopify sales trend

Use Adzviser to compare Shopify net sales, orders, and average order value for the previous complete week with the week before. Show a daily table, calculate the percentage change for each metric, and highlight the dates that contributed most to the difference.

Cross-channel comparison

Use Adzviser to compare Google Ads and Meta Ads for the same date range. Show each source separately with spend, impressions, clicks, conversions, CPA, and ROAS. Do not combine metrics that use different attribution definitions. Call out any comparison limitations before recommending budget changes.

Google Analytics acquisition

Use Adzviser to retrieve Google Analytics sessions, total users, engaged sessions, and conversions by session source/medium for the previous complete month. Return the top 15 rows, compare them with the prior month, and summarize the largest gains and declines.

Explore all supported Adzviser data sources.

What Claude does behind the scenes

For a reporting request, Claude typically:

Checks your available Adzviser workspaces and connected sources.
Looks up the exact metrics and breakdowns supported by the requested source.
Retrieves the requested reporting data.
Analyzes the returned rows and formats the answer.

▼ Example

Adzviser provides read-only reporting access. Claude can retrieve and analyze reporting data, but it cannot create, edit, pause, or delete campaigns or account settings through Adzviser.

Verify important results

Reporting data is requested from the connected source on demand, but the latest available date can still depend on that platform's processing delays, attribution rules, permissions, and reporting definitions.

For decisions involving budgets or executive reporting:

Start with a small date range and a few metrics.
Confirm the workspace, source account, currency, time zone, and date boundaries.
Compare the result with the same report in the source platform.
Expand the request only after the initial figures match your expectations.

Troubleshooting

Claude does not use Adzviser: Enable Adzviser from + → Connectors in the current conversation and mention "Use Adzviser" in your prompt.
Claude asks for approval every time: Review the Adzviser tool permissions.
The expected workspace or source is missing: Confirm that the source is connected to the correct Adzviser workspace, then ask Claude to list workspaces again.
A metric is unavailable: Ask Claude to list the supported metrics and breakdowns for that source instead of guessing a field name.
The numbers look different: Check dates, currency, time zone, filters, attribution settings, and the source platform's processing delay.

If the issue continues, visit the troubleshooting guide.

MCP Integration Guide Intro