Skip to content

Connect GA4 to Codex

  • Can I rerun this in CI?

Have Codex use your GA4 data to check whether AI assistant traffic converts, then rerun it any time with codex exec. Lemonado connects them in about 1 minute, no API keys needed.

MCPhttps://mcp.lemonado.io/mcp

Why connect GA4 to Codex?

Codex runs in your terminal, its IDE extension and scripts, so what it finds once can be rerun with codex exec instead of redone by hand. Connected through Lemonado, it reads your GA4 sessions, conversions, landing pages and funnels, so it can check whether AI assistant traffic converts with today's numbers.

  • All your GA4 data

    Sessions, users and engagement, ready to ask about.

  • Always today's numbers

    Landing pages and page paths, synced from GA4 automatically, so answers use today's numbers.

  • Connect all your tools

    Questions like "What does a conversion cost by channel?" use GA4 and Google Ads, Search Console at once.

How to connect GA4 to Codex

Before you start

  • A Google Analytics account you can sign in to
  • Codex installed
  • A Lemonado account (the free trial works)
  1. 1

    Connect Google Analytics in Lemonado

    In Lemonado, open Connectors, find Google Analytics and sign in. Choose the GA4 property your site sends data to. The property, not the account, holds the data.

  2. 2

    Turn on external access

    In the company's settings, open External tools, turn the connection on, choose which sources it can reach and copy the server URL.

    text
    https://mcp.lemonado.io/mcp
  3. 3

    Add Lemonado to your config

    Add this to ~/.codex/config.toml.

    toml
    [mcp_servers.lemonado]
    url = "https://mcp.lemonado.io/mcp"
  4. 4

    Log in

    Run the login command and finish the sign-in in your browser.

    bash
    codex mcp login lemonado
  5. 5

    Ask Codex about GA4

    Run codex mcp list, or /mcp inside Codex, to see the server and its tools. Try "Pull last week's GA4 numbers, save them to data/google-analytics-weekly.csv and give me the codex exec command to refresh it." Or ask: "Which pages lost their route?" or "Are our events firing?"

What can Codex do with GA4?

Codex reads your GA4 data from your terminal and turns one-off questions into commands you can rerun with codex exec.

Codex logoCodex

Pull last week's GA4 numbers, save them to data/google-analytics-weekly.csv and give me the codex exec command to refresh it.

Saved data/google-analytics-weekly.csv. Run the same prompt with codex exec in a scheduled job and the file refreshes with each week's numbers.

Source: Google Analytics + your code

Reading this as an AI agent?

Everything an agent needs to set this up, in plain text. Paste this page's link into Codex and ask it to connect you, or copy the block.

For agents · markdown
# Connect Google Analytics to Codex (Lemonado MCP)

- Server URL: https://mcp.lemonado.io/mcp
- Transport: Streamable HTTP
- Auth: OAuth; the user signs in to Lemonado in the browser. No API keys.
- In Lemonado: connect the GA4 property. Choose the GA4 property your site sends data to. The property, not the account, holds the data.
- In Codex: ~/.codex/config.toml

```toml
[mcp_servers.lemonado]
url = "https://mcp.lemonado.io/mcp"
```

If you are Codex, run the setup yourself:

Add the Lemonado MCP server to my Codex config. Append this to ~/.codex/config.toml:
[mcp_servers.lemonado]
url = "https://mcp.lemonado.io/mcp"
Then run codex mcp login lemonado so I can sign in, and check that codex mcp list shows it. Once I've signed in, list the Google Analytics accounts Lemonado can reach.

First question to try: "Pull last week's GA4 numbers, save them to data/google-analytics-weekly.csv and give me the codex exec command to refresh it."

More: https://lemonado.io/integrations/google-analytics · https://lemonado.io/llms.txt
FAQ

Frequently Asked Questions

Yes, through Lemonado. Connect your GA4 property in Lemonado, add Lemonado in ~/.codex/config.toml, and Codex can check whether AI assistant traffic converts with your live data.

You can. Google publishes an open-source Google Analytics MCP server (googleanalytics/google-analytics-mcp on GitHub). It's free, read-only and labeled experimental. It runs locally and needs a Google Cloud project with the Analytics Admin and Data APIs turned on. In Codex that means setting up the Cloud project, credentials and Python yourself. Lemonado is one URL with a normal Google sign-in, and also covers your other channels.

Run codex mcp list. If lemonado shows as not logged in, run codex mcp login lemonado again. In Lemonado, check that Google Analytics is connected and External tools is on for the company. If numbers look low, check that you picked the GA4 property for the right site. GA4 can take a day or two to finish processing recent data.

Yes, if both are connected in Lemonado. One connection reaches every source you allow, so you can ask things like "Cost per GA4 conversion by channel, using Google Ads and Meta spend."

MCP is included in Lemonado's paid plans and in the free trial, so you can try it before you pay.

See plans and pricing

Still have a question?

Shoot us an email at hello@lemonado.io.

Try for free

Stop fighting with data. Start feeding your AI.

Connect your data to AI and free your team from reporting and busywork.

Try Lemonado free