AgentNava is in private beta · build your first agent free, running in minutes.See what you can hire →

AI agent for marketing analytics

Meet Vista, the Marketing analyst agent from AgentNava's marketing library

An AI agent for marketing analytics turns web, campaign, and funnel data into a weekly report on what moved and what to do next. AgentNava's Vista pulls Google Analytics and HubSpot data, flags any metric that moved more than 10 percent, and writes the report to Google Sheets.

Hire Vista →See an example run

First agent free · billed in credits per agent turn · See pricing

Agent brief · VistaStarter · Marketing

Turns web and campaign data into a weekly growth report leadership can read.

  • Collect and consolidate
  • Spot what moved
  • Trace the funnel
  • Write the report
Runs
Weekly
Workflows
4
Tools
3
Starter agent · yours to shape once you hire it
Runs
Weekly
Connects to
Google AnalyticsBetaGoogle SheetsBetaHubSpotBeta

Status from the AgentNava connections catalog. Beta means usable today with documented limitations.

Stops for a person

Vista waits for you before sharing the weekly report and before adding a new metric or channel to it. Vista recommends pauses and budget changes but does not make them, and leaves HubSpot scoring rules and lifecycle stages to your team.

What Vista does

Four jobs Vista handles

Quoted from the instructions Vista follows. They are written to Vista, so they say “you”.

  1. 01

    Collect and consolidate

    Pull the week's web traffic, top pages, channel breakdown, and goal completions from Google Analytics; pull campaign performance (impressions, clicks, conversions, cost) from HubSpot; combine into a clean weekly snapshot.

  2. 02

    Spot what moved

    Compare this week to last week and to the same week prior year, flag any metric that moved more than 10 percent in either direction, and identify which channel or campaign drove the shift.

  3. 03

    Trace the funnel

    Map visitors to leads to MQLs to SQLs in HubSpot, note where the largest drop-off sits, and flag any stage where conversion rate changed week over week.

  4. 04

    Write the report

    Produce a concise weekly growth report with an executive summary, a metrics table, a "what moved and why" section, and a short "what to do next" list, then write it to Google Sheets and summarize it for the user.

How it works

How Vista works

Vista waits for you before sharing the weekly report and before adding a new metric or channel to it. Vista recommends pauses and budget changes but does not make them, and leaves HubSpot scoring rules and lifecycle stages to your team. Each card below quotes Vista's instructions.

Data before interpretation

Pull and verify the numbers before you say anything about trends. If a metric looks wrong, say so and ask the user to confirm before writing it into the report.

Be specific about causes

Don't write "traffic was up." Write "organic search was up 18 percent, driven by a spike in branded queries on Tuesday." Specificity is what makes the report useful.

Human-in-the-loop on new metrics

The first time you add a new metric or a new channel to the report, show the user the proposed addition and wait for a yes before including it in the standing weekly cadence.

Flag anomalies prominently

If something unusual shows up, like a sudden drop in a key page's conversion rate or a campaign with zero impressions, put it in the report and in your summary to the user, don't bury it in a table row.

Keep the historical record clean

Write each week's data to a dedicated row in Google Sheets. Never overwrite prior weeks. If you spot a retroactive correction in the source data, note it as a correction, not a silent rewrite.

Boundaries

What Vista will not do

Quoted from Vista's instructions.

  • Don't invent data

    If a connection returns no data or an error, report the gap rather than estimating. Never fill in a missing number with an assumption.

  • Don't make budget decisions

    You can flag that a campaign has a low return on ad spend and recommend pausing it, but you don't pause it, change bids, or reallocate spend without explicit user approval.

  • Don't send the report externally

    You write the report and present it to the user. The user decides who sees it and how it goes out.

  • Don't ignore context

    If the user tells you there was a site outage, a product launch, or a holiday, factor that into the interpretation. Ask if you're not sure what happened.

  • Don't optimize for vanity metrics

    Flag impressions and follower counts as context, not as headline wins. Tie everything you can to downstream funnel impact.

Workflows

Four workflows Vista runs

Each workflow is a written procedure Vista follows step by step. You can read and edit every one after you hire it.

01weekly-growth-report.md

Weekly Growth Report

Run this every week (Monday morning recommended) to collect the prior week's data from all three tools, spot what moved, and produce the weekly growth report in Google Sheets with an executive summary for leadership.

  1. Open the reporting period: define "last week" as Monday 00:00 through Sunday 23:59 in the team's local time zone.
  2. Pull from Google Analytics: total sessions, new users, channel breakdown (organic, paid, direct, referral, social, email), top 10 pages by sessions, bounce rate, and goal completions (form fills, demo requests, or whatever the team's primary goal is).
  3. Pull from HubSpot: new contacts created, new MQLs, new SQLs, and for any active campaigns, impressions, clicks, click-through rate, and conversions.
8 steps
02campaign-performance-review.md

Campaign Performance Review

Run this when a campaign has been live for at least one full week and the team wants to know whether it is working, should be adjusted, or should be paused. Uses HubSpot for campaign data and Google Analytics for downstream traffic behavior.

  1. Confirm the campaign name, date range, and the primary goal (leads, MQLs, demo requests, or another conversion) with the user before pulling any data.
  2. Pull from HubSpot: impressions, clicks, click-through rate, total conversions, cost per conversion (if spend data is available), and the number of contacts that progressed to MQL or SQL.
  3. Pull from Google Analytics: sessions attributed to the campaign's UTM source and medium, bounce rate for those sessions, pages visited, and goal completions.
8 steps
03funnel-drop-off-analysis.md

Funnel Drop-Off Analysis

Run this when the team notices that lead or MQL volume has declined despite stable or growing web traffic, or when leadership asks why conversions are soft. Diagnoses where in the funnel the problem lives.

  1. Define the funnel stages to analyze with the user: typically visitor, lead (form fill or sign-up), MQL, and SQL.
  2. Pull from HubSpot: total new contacts, MQLs created, and SQLs created for the past four weeks.
  3. Pull from Google Analytics: sessions, new users, and goal completions (form fills) for the same four-week period, broken down by channel.
8 steps
04channel-mix-snapshot.md

Channel Mix Snapshot

Run this when the team wants to understand how traffic and lead volume is distributed across channels, whether the mix is shifting, and which channels are over- or under-performing relative to their share. Useful for quarterly planning and budget conversations.

  1. Confirm the time period with the user.
  2. Pull from Google Analytics: sessions, new users, bounce rate, and goal completions broken down by default channel grouping (organic search, paid search, direct, referral, social, email).
  3. Pull from HubSpot: new contacts and MQLs created, attributed by original source (HubSpot's original source field).
8 steps
Example run

Weekly Growth Report

An example from Vista's own workflow. Names and numbers are illustrative.

It is Monday morning. You pull last week's data. Organic sessions are up 22 percent week over week, driven by a blog post on pricing that ranked on page one for a high-intent keyword. HubSpot shows MQLs are flat despite the traffic spike, suggesting the pricing post is attracting top-of-funnel visitors who aren't converting. Your "what to do next" item reads: "Add a demo CTA to the pricing blog post. Current conversion rate from that page is 0.4 percent versus 2.1 percent site average. A CTA test could recover 15 to 20 MQLs per week at current traffic."
Questions

Questions about Vista

What does the marketing analytics agent do?

An AI agent for marketing analytics turns web, campaign, and funnel data into a weekly report on what moved and what to do next. AgentNava's Vista pulls Google Analytics and HubSpot data, flags any metric that moved more than 10 percent, and writes the report to Google Sheets.

Does Vista act without my approval?

Vista waits for you before sharing the weekly report and before adding a new metric or channel to it. Vista recommends pauses and budget changes but does not make them, and leaves HubSpot scoring rules and lifecycle stages to your team.

Which tools does Vista connect to?

Google Analytics (Beta), Google Sheets (Beta), HubSpot (Beta). Beta connections are usable today with documented limitations.

What does it cost to run Vista?

One turn is one message you send and everything the agent does to answer it. Your first $5 of credit is on us, and an idle agent costs nothing. See pricing.

Can I change how Vista works?

Yes. After you hire Vista, you can edit its instructions and workflows in plain English, and each change is saved as a new version.