
The Day Our Ad Campaigns Went to Zero and an AI Agent Found It in Minutes
We're building affset, a white-label ad server and CPA network tracker, and we dogfood it hard — an in-house team runs real paid traffic through our own product. That also means we're our own first support ticket when something breaks. Our buying team runs campaigns through affset's MCP server, so instead of a stats dashboard it's a chat session with direct read/write access to our tracking data — clicks, click IDs, conversions — plus a browser tool wired into the same session. One day the numbers for "today" came back completely flat: thousands of clicks recorded, and literally zero of anything downstream — no landing page views, no engagement, no conversions. The day before had looked totally normal. First instinct is always to blame the traffic — bad sources, broken targeting, start...
We're building affset, a white-label ad server and CPA network tracker, and we dogfood it hard — an in-house team runs real paid traffic through our own product. That also means we're our own first support ticket when something breaks. Our buying team runs campaigns through affset's MCP server, so instead of a stats dashboard it's a chat session with direct read/write access to our tracking data — clicks, click IDs, conversions — plus a browser tool wired into the same session. One day the numbers for "today" came back completely flat: thousands of clicks recorded, and literally zero of anything downstream — no landing page views, no engagement, no conversions. The day before had looked totally normal. First instinct is always to blame the traffic — bad sources, broken targeting, start blacklisting. This time we skipped that and just asked the agent to pull up the actual landing page in the same chat. Not a tracking bug — the CDN hosting our landing pages had suspended the domain over an unpaid invoice, with the billing alert sitting in an inbox nobody checks. Every click that day was hitting a dead page before it had any chance to convert. We paid the invoice, then checked the fix the same way we found the problem — reloaded the real page in the same session, confirmed the tracking pixel still fired, and turned traffic back on. Nothing about the actual bug was interesting — an unpaid CDN invoice is about as mundane as it gets. What we noticed was that finding it didn't take switching between a dashboard, a browser tab, and a hosting panel. The agent already had the tracking data open, so pulling up the landing page in the same window was just the next obvious step. We've since set up uptime monitoring so this specific failure doesn't repeat. But the invoice would've been paid a lot slower if someone hadn't had a live view of the page sitting right next to the numbers.