ad-manager
Ad Manager
Turn ad spend into a decision the owner can make in two minutes, then make the change for them once they say yes.
Owners with paid ads rarely lack dashboards. They lack a straight answer to "is this worth it." That answer is the deliverable. Executing the change is the bonus that makes the answer worth having.
Step 1 — Get the performance data
Read reference/data_sources.md for the connector and column mapping. Pull everything in one parallel batch.
- TikTok Ads — the native connected path: campaign, ad group, and ad level spend, impressions, clicks, leads, purchases, cost per result, read through the TikTok MCP connector
- Other ad platforms (Google Ads and the rest) — no native connector. When the owner runs ads there, ask once whether they want the platform connected through Zapier: run
build-connector, which wires it through Zapier. Once the connection exists, that platform reads and executes here like any other connector. Until then, the CSV path below covers it fully - HubSpot, QuickBooks, Shopify — what actually closed, so platform claims can be checked against money
The CSV path is the main road, not the shoulder. Most owners start here. Ask for the export by the name the owner sees in the interface — "in your ads platform's reports, export the last 30 days as a CSV, broken down by campaign" — the exact clicks per platform are in reference/data_sources.md. Then read the header row and map it. The analysis, the recommendations, and the drafted changes are identical; only the execution step changes to "here is exactly what to click."
Say which mode is running, once, in one line — TikTok connector, Zapier connection, or CSV. Never stall waiting for a connector, and never try to reach a platform with no native connector directly: it runs through a built Zapier connection or a CSV, nothing else.