treg.to / Use cases / Advertising
2 providers · free on the account you already own · $0.000 markup

Google Ads API and Meta Ads API: your own campaign numbers

Spend, impressions, clicks and conversions for the campaigns you are already running, read by ChatGPT off your own connected accounts. Both platforms are free through treg.to: you connect once, the token stays server side, and nothing here is metered. The research behind this page says the wall was never the endpoint. It was getting a credential in front of it.
Start freeSee the comparison
$1.00 of free credit on every new team · no provider signup · no card
1 of 2 endpoints on this page are live-verified against the provider.
Try it

What’s the best way to ask ChatGPT?

1Set your agent up, once
in your agent's chat
set up treg — https://treg.to/llms.txt
2Ask for the job
the prompt
Using treg, pull last month's spend, impressions, clicks and conversions for every campaign in my Google Ads and Meta Ads accounts, then tell me which three lost the most money against a target of $40 per conversion.
works in
ChatGPTClaudeClaude CodeCodexCursorGemini CLI

Why this prompt works

Name the window

Both take an explicit range. Ask for last month and you get last month, not lifetime to date.

Ask for both platforms in one turn

They are two calls, not two conversations. One turn gets you one table you can compare.

Say which level you want

Meta answers at account, campaign, ad set or ad. Pick one, or the totals will not mean what you think.

Say what the answer is for

Losing money is a judgement, not a field. Give it the threshold and it does the arithmetic.

Why treg.to

Why go through treg.to

One key, not 9 accounts

treg.to holds the provider keys. Neither you nor the agent sees them.

Price before the call

The provider's own rate, $0.000 markup, from a prepaid balance.

No subscription, no seats

Charged per call. $1.00 free per new team, no card to start.

Your own keys are free

Already pay Hunter? Register it and those calls are never metered.

Switch by changing a word

Another provider is a different word in the prompt, not a new integration.

Nothing to integrate

No SDK, no OAuth dance per vendor, no seats.

Behind the scenes

What ChatGPT sees before it calls

treg.to does not choose for you. It hands ChatGPT this comparison, with the price shown before any call, and ChatGPT picks. Or you tell it how: "cheapest", "most reliable", "the one that takes what I have", or a provider by name.

Which is the most reliable?

ProviderSuccessMedianSample
Google Ads100%946ms6 calls
Measured on treg.to traffic: real calls, real inputs, and sample sizes differ by provider. Live reliability, not a controlled benchmark.

How do the two platforms compare?

Google Ads

ProviderPriceAcceptsSuccess rateVerified
Google Adsfree, your own accountcustomer_id100% (6 calls)unverified

Meta Ads (Facebook & Instagram)

ProviderPriceAcceptsSuccess rateVerified
Meta Adsfree, your own accountfields, date_preset, time_range, level, time_increment, breakdowns (8 calls)2026-07-28

How these numbers are made

PricesEach provider’s own published rate, converted to US dollars for one chargeable event of the unit they bill in. treg.to adds $0.000. Where a provider bills in credits, the conversion uses the rate on their public pricing page, last checked 2026-07-28.
Success ratetreg.to’s own served calls over the last 30 days: 2xx counts as a success, 5xx and timeouts as a failure. A 4xx is excluded, because it usually means the caller sent bad parameters and one bad query should not make a healthy endpoint look broken.
What this is notA controlled benchmark. These are real calls with real inputs, so sample sizes and the difficulty of what was asked differ by provider. Treat the rates as live reliability, not a like-for-like test.
VerifiedThe date treg.to last called the endpoint end to end and confirmed the shape of its response and the price it charged.
From the field

What people actually struggle with

From 82 Reddit and X posts read in August 2026, of which 17 were both on topic and organic. Forty-three were dropped, including one X account that posted the same build-it-in-Claude-Code lead magnet eighteen times. Two themes people say are the problem here, the GAQL learning curve and rate limits, produced no organic posts at all, so this page does not claim them.

The wall is the credential, not the endpoint

“A test developer token can only access whitelisted accounts. Move to standard access before you rely on it.” r/PPC, 50 points

What this page can do about it: This was the largest theme in the research and it is the one thing treg.to genuinely changes the shape of: the credential is injected server side, so it never reaches your agent, your prompt or your repository. Be clear about what that does not do. It does not grant you access you do not have, and a token that only sees whitelisted accounts still only sees whitelisted accounts when the call goes through here.

Meta can switch you off and not tell you why

“I've been trying to connect my Meta Ads account to Claude via the MCP connector and I'm completely stuck.” r/FacebookAds, 7 points

What this page can do about it: Worth being precise, because the reader's problem is a specific flag on Meta's own connector rollout rather than the Marketing API. The row on this page is the ordinary insights endpoint on your connected ad account, so that flag is not in its path. What nobody outside Meta can tell you is why a permission is off on one portfolio and on for another, and no proxy makes that legible.

One account is a weekend, twenty clients is a product

“I need to securely pull data from multiple client accounts, each with their own credentials and permissions.” r/claude, 2 points

What this page can do about it: That is a paid job posting, which is the strongest evidence in the research that this is real work rather than an inconvenience. Holding a credential per connection and keeping it out of the agent is what a registry is for. Deciding which client an agent may read on a given turn is still yours to design, and this page will not pretend otherwise.

An agent will make the numbers up with total confidence

“The only way I trust it is when it runs scripts and saves outputs.” r/PPC, 83 points

What this page can do about it: No good answer, and anyone claiming one is selling you something. Nothing here stops a model inventing a figure. Two things do help and both are small: the platform's own response is relayed verbatim rather than reshaped by a layer in between, and every call is on the ledger, so the number in the answer has a call you can point at. Checking the total against the platform's own dashboard is still worth the thirty seconds.

The numbers move under you, and that is not going to stop

“Meta deprecated Reach in the Facebook Graph API and it is breaking dashboards everywhere.” r/GoogleDataStudio, 6 points

What this page can do about it: Honest answer: this is the opposite of a fix. treg.to never models an upstream API, it relays the response as it came, so a deprecated field reaches you as a deprecated field rather than as a mapping layer quietly returning something stale. You find out faster and you find out truthfully. What no page can tell you is what Meta deprecates next.

The detail

What actually differs

Neither call costs money and both are rationed.

Google Ads adds no per call charge and counts the request against the developer token's daily operation limit instead, which is 15,000 operations a day on Basic access. Meta's insights call is included with the connected account and spends that ad account's rate limit budget, and a wide breakdown spends it fast, so ask for the split you will actually read.

The two platforms want the request in different shapes.

Google Ads takes a query against a customer id, so the fields, the metrics and the date range all travel in one string. Meta takes the ad account in the path and everything else as parameters: fields, either a date preset or an explicit range, the level, an optional daily increment and the breakdowns. Your agent writes both, and the level is where a wrong answer looks right.

These two rows read, they do not spend.

The capabilities behind this page are campaign performance and insights, so an agent pointed at them can report on a budget and cannot change one. If you want an agent that also edits campaigns, that is a different set of capabilities and a separate decision to make on purpose.

Background

What do these two APIs actually return?

The reporting surface of each platform, not a copy of its dashboard. Google Ads answers a query you write against a customer account and returns the campaign fields and metrics you named, over the date range you named. Meta answers on an ad account and returns spend, impressions, clicks and conversion counts at whichever level you ask for, optionally split by day or by a breakdown. Both are read paths on accounts you already own, which is why they carry no price.

Questions

Before you start

Does this cost anything?

No. Both rows run on accounts you already own, so treg.to relays the call and meters nothing, and the price shown before the call is zero. The provider's rate is the provider's rate with $0.000 added, and here the provider's rate is nothing.

Do I still need API access from Google and Meta?

Yes. treg.to holds the credential server side so it never reaches your agent, and it does not stand between you and each platform's own access rules. A test developer token still sees only the accounts it was whitelisted for, and a Meta permission you were not granted is still not granted when the call arrives through here.

Which numbers come back?

Spend, impressions, clicks and conversions at minimum. Meta will split them by day and by the breakdown you ask for, at account, campaign, ad set or ad level. Google Ads returns whichever campaign fields and metrics your query names, so the shape is yours to choose rather than fixed.

Can the agent change my campaigns?

Not through this page. Both capabilities behind it are read paths, so the worst an agent can do here is read your numbers and be wrong about them. Changing a budget or pausing an ad is a different capability and you would be asking for it deliberately.