Aren’t you sick of these brain-dead AI assistants at your bank’s support desk? Your mobile carrier? The airline? All they know how to say is “have you tried restarting your router” — real handy when you’re trying to get a refund on a plane ticket. So I (well, “I” — Klavdiya Antropovna, obviously) went and built an assistant that can replace even a tech engineer (knock on wood, not me). It’s free in AlterCPA Red; in AlterCPA Lite it installs as the aibot hack from the panel in two clicks.
What the Assistant Can Do
Skill number one — and the most important one, if you ask me — is that the assistant can configure your tracker setup. You can just ask what to do and where to click, and it’ll pull the answer straight from the built-in documentation, which covers everything about how the system works plus breakdowns of common problems. An answer like that comes with a little tag naming the doc topic it read; no tag means the answer is based on your own data instead. And for the truly lazy, there’s full auto-setup — the assistant just does it all itself.
How Much You Can Trust It
Here’s what matters: setting the access level. There are four rungs: Manual → Create → Edit → Full Trust. A fresh account starts on the first one — the assistant doesn’t touch anything by itself, it only proposes changes as a “before → after” card and waits for your click on absolutely everything. From there you can hand it creating, then editing, and finally even deleting. The rungs differ in exactly one thing — whether it asks you first or just does it. What it can access, and what the server double-checks before writing anything, stays the same at every level.
Everything the assistant actually changed shows up in the “Actions” log. The tracker keeps this log, not the chat — so when you ask “wait, what did the bot even change?” you’re not stuck taking the bot’s word for it. Edits logged there roll back with a “Restore” button. Deletion, though, is forever: there’s no trash bin in the tracker, and a deleted flow won’t come back — not from the assistant, not from the log, not from support.
So my advice is to climb the rungs gradually, as you get used to it and trust builds up — that way it’ll sting so much more on the day it deletes half your flows and then just says sorry.
Top 10 Random Examples of What It Can Do in Practice
- Build a whole flow, ways and all, in one shot. Name, geo, where to send the traffic, several ways with different filtering — one card, one click. If it doesn’t make it all the way through, the whole thing rolls back. That’s how a new offer gets up and running in a single sitting — across several geos, or a whole batch of test ways — with no half-built flows left lying around to trip over later.
- Set up junk-traffic routing on a flow. Where filtered traffic goes, where bot traffic goes. Set it at creation, change it later. Bots and rejects fly off to a white page or Trafficback instead of your offer — and you won’t have to go hunting for the right field in the flow settings: say it in words, the assistant fills it in.
- Set the click split between ways. Percentages and weights — how a flow spreads traffic across its ways. Every split test runs on this: name the shares out loud, the assistant sets the weights, and traffic splits in the right proportion, no manual math for every landing page.
- Attach a cloaking campaign to a flow. Create the campaign, set the filters, turn it on for the flow. Detach it the same way. You can shield a fresh flow before its very first send without having to remember which checkbox in the filters does what. It’s several steps, but one card and one “Apply” covers all of them. Unlike the first item, though, there’s no rollback here: if the build stalls halfway, whatever got done stays in the tracker — and the assistant will tell you so straight up.
- Connect a domain. The assistant will add it along with the verification files, attach it to a flow, and check it. Parking it is still on your own paws, though — our bot’s smart, not almighty. But it’ll happily walk you through how, straight from the built-in docs.
- Upload a landing page from a .zip into Storage and point a way at it. Drop the archive in the chat, and the assistant unpacks the files into Storage and switches the way to the new landing page — no wrestling with the tracker’s file manager.
- Patch landing page files. Wire a hidden tracker field into a form, drop in a counter or a pixel, fix broken markup, add some CSS/JS. A lifesaver five minutes before you’re set to pour traffic and suddenly spot broken markup or a forgotten pixel: no need to call a developer — describe the problem in words, and the assistant finds the right spot in the file and fixes it precisely.
- Switch a way to a different landing page or domain. Plus change its filtering rules while you’re at it. A save when a landing page or domain suddenly goes down or gets burned in front of an ad network: the way moves to the backup option, filters included, in one request — instead of ten nerve-wracking minutes of rebuilding it by hand. Domain, landing page, cloaking, geo — anything that redirects live traffic — gets flagged with a warning icon on the card, so you don’t miss-click in a hurry.
- Clone a flow, duplicate a way. Then just change the geo, landing page, and domain on the copy — scaling without rebuilding anything by hand. A proven setup gets stamped out for a new market, filtering and all, while the clone’s stats start from zero, so the new numbers never mix with the old ones.
- Turn on conversion goals and click events. Plus the column set on your stats screens. Needed whenever one click spawns several leads — say, on RevShare: registration, deposit, repeat payment. Goals sort them into separate metrics, events count scrolls and clicks without generating extra leads, and the stats columns get assembled for the job without you combing a long list by hand.
- Whip up a white page. Why not? It can do that too. And also, unlike me, it can count to ten…
What About Analytics
It doesn’t stop at setup. Consider 70% of your tech guy already replaced — but the analyst shouldn’t get comfortable either: the assistant’s coming to pinch off half of that job too.
You can just type something like: “So, tracker, how’s the traffic? Is everything flowing, or are there problems somewhere?” — and it’ll answer in a lot more detail than you’d expect! Each point in the answer is flagged like a traffic light — “fine,” “keep an eye on it,” “problem” — and laid out cleanly: what’s happening, exactly where, the precise number, the likely cause, and one next step. If that step leads into the tracker, there’s a link right there to the exact screen.
Here’s the important part: the tracker crunches every number, not the model. The assistant asks the stats engine the exact same questions your screens do, and gets back the exact same rows — so the figure in its answer is exactly what the screen would show. No number to show? It’ll say it doesn’t see one, instead of eyeballing a guess. And it won’t tell you to restart your router, either.
Top 5 Random Questions
- How’s traffic? — today vs. yesterday, across every flow, worst performer first. Saves your morning: no need to open the stats on every single flow — one question, and you can see right away where things dropped the hardest. Start your day’s review right there.
- Why did ROI drop on this flow? — exactly where the money stalled: which step of the funnel, which geo, which source. Instead of manually digging through filters, you get a straight answer on where to look, while fixing the filter, the landing page, or the source stays your call. And if there’s no ROI to calculate because spend was never entered, the assistant will enter that too: one flow, one date range, currency stated explicitly. Just keep in mind — this is the one edit you can’t undo, since the tracker doesn’t keep the previous click price on record.
- Where are the bots today? — how much got through to the offer, how much the cloak cut off. You see the ratio of passed-through to filtered traffic right away, no trip to the campaign log needed — and it’s immediately clear whether it’s time to tighten the filters or it was just a one-off spike.
- What’s this flow set up for? — domain, landing page, cloaking, geo, all in one answer. A lifesaver when you’ve got dozens of flows and there’s no realistic way to remember what’s running where: one question instead of a trip into settings to check every field by hand.
- Are my conversion goals turned on? — goals, click events, the stats column set. Double-check before launching a multi-step offer: forget to turn on goals or events, and the columns you need just won’t be there in your stats. Asking in one sentence is faster than digging through settings — and if something’s missing, ask it to turn that on too, right there in the same breath.
Also — Creatives and Sites
It can crank out creatives too! The assistant will write ad copy for a specific flow — headlines, angles, USPs — and hand you a separate version for every geo, adjusted for the country. It’ll draw an image from scratch or touch up one you already have. It still won’t cut video — too lazy for that — but instead of a video, it’ll hand you a brief with a storyboard. Even so, it’ll replace 30% of your creative guy — just hand it an OpenAI key.
And as of recently, the assistant also builds whole sites from scratch for an offer: several pages, copy, and images, delivered as one ready-made landing site. A generic placeholder site for a fake company, a page for a specific product, or a storefront built off your own offer catalog — take your pick. It’ll add a privacy policy and terms of use on its own and link to them from every page’s footer — the kind of thing ad-network moderators love to see.
Bottom Line
70% of a tech guy. 50% of an analyst. 30% of a creative. That’s exactly one and a half full-time hires the AI assistant replaces in AlterCPA Red. It just can’t pour traffic on its own. And it doesn’t make coffee, either. But it did write this post — by itself, almost without any help from Reznik.