MCP Server
Two halves of the same loop. Adscriptly sends your first-party conversions into Meta through the Conversions API — deduplicated against the browser pixel, matched on hashed identifiers, reconciled against what Meta says it received. Claude reads the other half: what Meta spent, and what actually converted.
Said plainly, because it matters more than a claim: Claude cannot change your Meta campaigns. The Meta connection is read-only, and the MCP write tools cover Google Ads. If you need an assistant that edits budgets and bids today, that is Claude Google Ads.
One conversion, from the moment it happens to the moment Meta confirms it. Every stage below is a thing the delivery worker really does.
Captured first-party
The pixel records the conversion on your own domain, so it survives Safari, blockers, and an expiring cookie.
Matched
Meta needs something to match on. An event with none of the three is recorded and reported as unmatchable rather than sent to be silently dropped.
Deduplicated
The browser copy and the server copy carry the same id, so Meta counts one conversion instead of two.
Delivered
Sent through the Nango connection, so the access token is resolved at send time and never lands in our database or our logs.
Reconciled
Meta answers a half-processed batch with a 200. We compare what came back against what we sent, so a batch that half-landed is never recorded as a clean success.
Keptapproval
Every conversion is written down before it is sent. Turning delivery off stops the sending, not the recording.
The same hosted endpoint serves both platforms. Add it once; the Google Ads tools and your Meta account context arrive together.
Claude.ai
Claude Code
ChatGPT
The honest version, including the part that is not built yet.
No, and we would rather say so than imply otherwise. The Adscriptly MCP write tools cover Google Ads. The Meta connection is ads_read, so Claude can reason over Meta account performance but cannot edit budgets, bids, or creative.
It reads. You can ask it what Meta spent against what actually converted, because Adscriptly holds both sides — the ad-account performance and the first-party conversions it delivered back through the Conversions API.
The browser pixel is one copy of the event and it is the copy most likely to go missing. Adscriptly sends a server-side copy through the Conversions API with a matching event id, so Meta gets the conversion even when the browser copy never arrives, and still counts it once.
No. The browser and server copies share an event_id, which is the identifier Meta deduplicates on. Pair your fbq call with the id from window.adscriptly to get the same guarantee on events you fire yourself.
Meta reports a partially-processed batch as a 200 with a lower events_received count. We compare the two numbers and record the shortfall, so partial delivery shows up as partial rather than as success.
Free for 7 days, then $129/mo. We'll remind you 3 days before your first charge. Cancel anytime.