A free Hyros alternative

If you're looking for a Hyros alternative, you probably have one of two reasons: the price, or you want to see how a number was produced before you spend against it. neo answers both, with a narrower scope that won't suit everyone.

What neo does

• ▸Meta ads and email. Nothing else. One channel pair, done properly, instead of a matrix of integrations.
• ▸Your own tracking subdomain. You CNAME something like t.yourdomain.com to us and the visitor cookie is first-party. SSL is issued automatically; there is no manual step on either side.
• ▸Three attribution layers, never blended. Cookie match, then hashed-email match, then a strict time-window candidate — and that third one only fires when exactly one click is in the window. Probable matches render as a separate dashed figure. An exact count is never inflated by a guess.
• ▸Unattributed orders stay unattributed.If we can't tie an order to a click, it says so. It doesn't get distributed across campaigns to make a report look complete.
• ▸Server-side CAPI with hashed identifiers, deduped by order id against your browser pixel.
• ▸Ad-level drilldown— campaign, adset, ad — from Meta's ID macros, so renames don't break history.
• ▸aROAS: revenue net of payment-processor fees.
• ▸In Ads Manager.A Chrome extension writes counted sales next to Meta's own numbers, so you compare in the place you already make decisions.
• ▸An MCP server, so you can ask Claude or another AI assistant about your numbers instead of clicking through a dashboard.

The price

Free. No card, no trial countdown, no sales call. Two limits, both stated on the pricing page rather than discovered later: 25,000 tracked events a month as fair use, and a 50,000-a-day safety cap that exists so one runaway script can't generate an infrastructure bill a free product can't pay. If you cross either legitimately, you email us and it gets raised.

Where neo is worse

Worth being direct about, because switching on a bad fit wastes your week:

• ▸One channel. No Google, TikTok or native. If you need cross-channel in one view, stay where you are.
• ▸No spend ingestion. Spend lives in Meta, so in-app you get clicks, sales, revenue and revenue per click — the ROAS division happens in Ads Manager or in the extension, not on a neo chart.
• ▸No call tracking, no team seats, no SLA. One person builds this.
• ▸No fingerprinting. Deliberate, but it means neo will report a smaller matched number than a tool that stitches identities probabilistically. The trade is that you know which orders are certain.
• ▸The Chrome extension isn't on the Web Store yet— today it installs unpacked from a zip. That's friction and we're not going to pretend otherwise.

How to evaluate without switching

Run neo alongside whatever you have. Both can read the same order webhook and both can fire CAPI — event ids dedupe against the pixel, so parallel running doesn't corrupt anything. Give it two weeks and compare three numbers: total counted orders, the share tied to an exact click, and revenue after fees. If the tool you're paying for can't show you which of its conversions were observed and which were inferred, that comparison is the whole argument.

Background on why the two dashboards disagree in the first place: why Meta shows more conversions than Shopify.