FixOpen to everyone

Close the gap with a first-party gateway.

When purchases go missing between your store and Meta, the usual cause is the browser: blocked pixels, short-lived cookies, a checkout the tag never sees. The Anacoic gateway sends them from your own subdomain and server instead.

The free plan includes one gateway. Want to see the gap first? Start with Watch.

fix · gateway gw_n0rthw1nd · track.northwind-outfitters.com sample data
Browser events from the ana.js tracker and purchases from your backend go to one gateway on your own subdomain. The gateway sends each event on to the destinations you switch on, such as Meta's Conversions API, TikTok or a webhook.

Delivery log

sample data
Delivery log, sample data
Time Event Order Destination Status Took
14:02:51 Purchase 10482 meta_capi 200 OK 142 ms
14:02:51 Purchase 10482 pinterest 200 OK 188 ms
14:02:51 Purchase 10482 tiktok 200 OK 211 ms
14:01:37 Lead — meta_capi 200 OK 131 ms
13:58:09 Purchase 10481 meta_capi 200 OK 156 ms
13:58:09 Purchase 10481 webhook 503 Unavailable 3,000 ms

What the gateway does

Everything here works today.

Purchase · order 10482 Sample data
event
Purchase
destination
meta_capi
status
200 OK
match keys
em, ph
error
none
took
142 ms
reference
evt_8f2k91
  • The ana.js tracker and a server API

    Send browser events with the ana.js tracker and confirmed purchases from your backend. Both go through the same gateway.

  • Server-side forwarding to Meta, TikTok and other ad platforms

    One event fans out to the destinations you switch on, such as Meta's Conversions API, TikTok, LinkedIn or a webhook. It counts as one signal however many destinations it reaches.

  • Custom domains for your gateways

    On Pro and up, run the gateway on a subdomain you control, so requests stay first-party and cookies are set by your server rather than by a script.

  • Personal details hashed before they are sent on

    Email addresses and phone numbers are normalized and hashed with SHA-256 before they leave the gateway.

  • Logs of what was sent and what each platform replied

    The latest 100 delivery log entries per gateway, kept for up to 30 days: the event, the names of the match keys sent (never their values), each platform's status, any error, the time it took and a short reference.

  • A simulator to send one test event

    Send one test event through a gateway and see each destination's answer before real traffic moves.

What is server-side tracking?

The same event, sent from a place you control.

In browser tracking, each pixel sends events straight from the visitor's device to its own platform. In server-side tracking, the event goes to an endpoint you control first, where it can be checked, hashed and routed to each platform's API.

Dimension Browser pixels only Through a gateway
Where the request starts Browser pixels and tags on the visitor's device A first-party endpoint you control, or your own server
Ad blockers and browser limits Requests to ad-network domains can be blocked; script cookies expire fast in Safari Requests go to your own subdomain; cookies can be set by your server
Adding a platform Another tag, more browser code One event fans out to each platform's API
Seeing what happened Spread across each platform's own debugger One log of each delivery: status, error and timing per platform
  1. Start here

    Quickstart

    A gateway, one event and your first confirmed delivery.

  2. Integrations

    Shopify, WordPress and more

    Setup notes for each store platform and ad destination.

  3. Compare

    Anacoic vs Stape

    When a gateway fits better than a hosted server-side GTM.

Not sure the gateway is what you need?

Start with Watch. It shows how far your store and Meta are apart, and when the gap opened, before you change anything. Watch is in early access: talk to us and we'll set you up.