GA4 Playbook
How to Connect Social Posts to Real Conversions With GA4 and AI Agents
Likes tell you a post resonated; they don't tell you it sold anything. The answer to "which post actually converted" lives in GA4 — sessions by source, landing pages, conversions — and almost nobody wires it to their social stack. Do it and every posting decision gets a revenue signal.
What top growth teams do
The habits behind teams that report revenue per post, not impressions per post.
Judge posts by sessions, not hearts
Pull traffic by source/medium for the campaign window and rank posts by the converting sessions they drove.
Why it works: Engagement and revenue often disagree; the posts worth repeating are the ones GA4 says brought buyers.
Read landing pages, not just channels
Break reported traffic down by landing page to tie it back to the specific link each post carried.
Why it works: Channel-level numbers hide which content worked; landing-page rows map one-to-one to posts and campaigns.
Make attribution a scheduled question
Have an agent run the source/medium and top-pages reports weekly and post a digest next to the content calendar.
Why it works: Attribution that requires opening GA4 gets checked quarterly; attribution that arrives in the channel shapes next week's posts.
How this plays out in practice
Generalized examples of the kinds of teams running this play.
Ranked a month of posts by GA4 converting sessions and found their quietest platform drove the most revenue — engagement had been pointing them at the wrong channel.
Shipped clients a weekly 'posts → traffic → conversions' digest joined from Modiva's publishing data and GA4 reports, a report competitors couldn't match from social metrics alone.
The examples above are generalized, illustrative descriptions of common approaches across the industry. They are not based on, attributed to, or affiliated with any specific company or individual, and are provided for educational purposes only.
Steal these templates
Copy-paste starting points. Swap the brackets for your own topic and ship.
WEEKLY: ga4_get_traffic_by_source (last 7 days) → keep social sources JOIN with posts published that week (already in Modiva) ga4_get_top_pages → match landing pages to post links POST digest: top 3 posts by converting sessions, bottom 3 to rethink
Do it with Modiva
Here’s how to run this play for real — connect once, then publish, schedule and automate across every platform from one place.
- 1
Connect Google Analytics 4 to Modiva
Sign in at modiva.ai, open Connections → New connection and pick Google Analytics 4. You authorize on Google Analytics 4's own screen — Modiva stores only a scoped, encrypted token, never your password. The free tier connects your first three accounts at no cost.
💡 Connecting once makes Google Analytics 4 available to every REST API call and MCP key in your workspace — you never wire up OAuth again.
- 2
Find the property and the numbers
List accounts and properties, then run traffic-by-source and top-pages reports for your campaign window. The run-report tool takes any metrics × dimensions if you need a custom cut — use the metadata tool to discover names.
💡 Add UTM parameters to the links in your posts — they make the source/medium rows unambiguous.
- 3
Join it with your posts
Have an MCP-connected agent match GA4's source and landing-page rows to the posts Modiva published, then answer 'which post drove converting traffic' directly — and post the digest to your team channel on a schedule.
- 4
Let an AI agent run the busywork
Create an MCP key and point your AI assistant (Claude, Cursor, or any MCP client) at Modiva. The agent can draft variations, schedule posts, pull engagement and reply to comments through typed tools — across every connected platform at once.
💡 Describe the playbook to your agent in plain language ('repurpose this video into 5 platform-native posts and queue them') and let it call the tools.
FAQ
Can Modiva change my Analytics settings?
No. The GA4 connection is read-only by design (analytics.readonly scope) — it runs reports and reads metadata, nothing else.
Which GA4 properties can the agent read?
Every property the connected Google account can access. The list-accounts and list-properties tools enumerate them; each report call names its property explicitly.
Does this need Google Ads or BigQuery?
No — it reads the GA4 Data API directly. If you later want ad spend joined in, the Google Ads connector covers that side.