Menu
ATA Edge / Docs /

ATA Edge features

Last updated: 2026-11-13

Everything the current release of ATA Edge does, and what it doesn't do yet. For the offer and the price, see ATA Edge.

Sales to your ad platforms

  • Purchases from your checkout. When a payment is approved, your checkout sends a webhook to your Worker. When it can link the sale to a visit on your site, and the consent your setup asks for allows it, it sends a purchase to each live platform you connect.
  • Live today. Meta Conversions API and GA4. Google Ads is in testing, and more ship as each passes a live test.
  • One order, one purchase. Retries don't double count. On Meta it replaces your other Purchase sends to that pixel, so Meta doesn't count a sale twice.
  • Consent respected. With a cookie banner, a sale goes to Meta only after ad consent and to GA4 after analytics consent (an optional setting sends GA4 an anonymized, labeled sale when no visit was linked and consent is unknown). With no banner, consent mode is off and a linked sale goes unless the visitor said no.
  • Each platform's time limit. On Meta, a sale with no tracked visit, or older than 7 days, stays in your dashboard only. GA4 takes sales up to 72 hours old, and when consent allows, a sale without the visitor's GA4 IDs goes to GA4 anonymized and marked unmatched.
  • Test before going live. A test purchase shows in Meta's Test Events before you switch sending on.

Checkouts

  • Hotmart is live. Stripe and 26 more are in testing. The 26 are Kiwify, Eduzz, Cakto, Hubla, Guru, PerfectPay, Yampi, Ticto, Payt, Lastlink, Mundpay, Monetizze, GGCheckout, Assiny, Wiapy, Kirvano, Greenn, Braip, Cartpanda, Doppus, Frendz, Herospark, PagTrust, Kavoo, Wiven, Blimboo.
  • Stripe: one-time payments. Payment Links need no code. A Checkout Session your own server creates needs a short snippet. Subscriptions aren't covered yet.
  • Refunds and chargebacks arrive by product, campaign and ad, where the checkout sends them.

Supported means the checkout's webhook passes our tests with test data and you can install it, with no live test with a real sale yet. Live means a real sale went through: ATA's own Hotmart sale showed up in Meta's Test Events on 5 Oct 2026. On any checkout, your own first real sale is the proof. A sale is linked to its visit when the checkout sends our marker back. Blimboo sends none, so its sales link only through a form on your site. Kavoo and Wiven report your commission, not the full sale.

Bots and AI traffic

  • AI crawlers read your site for free. Crawlers like GPTBot, ClaudeBot and PerplexityBot fetch your pages but mostly don't run scripts, so they never touch your Worker. Nothing blocks them: being read by AI search is how people find you there.
  • Your Worker never sends bots. AI crawlers, signed AI agents such as ChatGPT agent, search crawlers, link previews, Cloudflare verified bots and automated browsers are stored and counted in your dashboard, and never sent to your ad platforms, so their ads learn from people, not from bots.
  • Cloud-server visits marked. A visit from a cloud or hosting network (AWS, Google Cloud, Hetzner and similar) is marked as datacenter. It is still sent by default, because people on a VPN can come from those networks. One setting holds these visits back too.
  • A paid sale is never held back as a bot. A payment proves a buyer, so a sale follows the same rules as any other sale whatever its visit was, even when the buyer asked ChatGPT agent to buy for them. Only the bot's own browsing stays out.
  • Bot traffic by ad. The Quality screen shows, per ad, how many visitors were people, datacenter visits or bots, each counted once, next to the clicks Meta counted (that column needs the optional read-only Meta token). An ad with a high share points to a placement worth cutting.

Limits: a bot that fakes a normal browser on a home connection isn't caught. The optional browser Pixel runs before your Worker sees the visit, so it isn't covered by this filter.

The dashboard

  • Sales and spend: net revenue from your checkout next to Meta spend, ROAS and cost per sale, by day. Spend and ROAS need an optional read-only Meta token.
  • Sales: each order's status, whether it's linked to a visit, the checkout and the ad source, with every send attempt and the platform's response in the order's trace.
  • Refunds: how many, what they're worth, the refund rate and how many days after the sale they arrive.
  • Health: late webhooks, a Meta ads token close to expiring and a change in the share of linked orders, each with the fix.
  • Setup: Meta and GA4, each with its last delivery, your checkout webhooks and the site tag, on one screen.
  • Quality: how much Meta accepted in the last 24 hours and 7 days, which identifiers your purchases carry, and the bot traffic by ad.
  • Flow: your funnel as steps, from PageView to InitiateCheckout or Lead to Purchase, each with its count, the rate from the step before and one row for each ad platform and GA4. A banner names the earliest problem, and each step opens its real events as a timeline. It only reads, so it changes nothing.

Ask Claude about your numbers

  • The analyst skill. Ask Claude about your sales, refunds, ad spend and ROAS. It pulls a read-only copy of your data and tells you where each number came from.
  • Honest about gaps. It warns you about days that haven't ended, spend the platforms may still change, and mixed currencies. The numbers behind each answer are saved in a small file you can check.
  • Read-only. It never changes anything on your install.

Where it runs

  • Your own Cloudflare account, on your domain. No Stape bill and no server to rent. From US$5 a month on Cloudflare's paid Workers plan to run live, billed by Cloudflare. Free to test.
  • Yours to keep. Nothing in the install checks your membership, so it keeps running if you cancel.
  • Client work. Your license covers installs for clients, each on their own Cloudflare account.

Install

  • AI does the install. You fill one setup page on your computer, and Claude Code or Codex runs every command and checks each step.
  • Lessons cover moving your DNS to Cloudflare, getting your tokens, connecting your checkout and going live.

Not yet, and not a fit

  • ChatGPT Ads, TikTok, Microsoft Ads, LinkedIn Ads and Kwai come next, each as it passes a live test.
  • Not a fit for a domain that can't move to Cloudflare, or for multi-product carts yet. WooCommerce is next.
  • In sensitive categories like health or finance, Meta can block Purchase events, and no tracking setup changes that.