Every event, accounted for

Server-side tracking from the browser and your shop's server to each platform. Consent checked, every answer on record.

Purchases from the shop's server

The order your pixel missed still reaches your campaigns, with the consent each platform needs.

The WooCommerce plugin and the Shoper app report each paid order from the shop's backend. The plugin signs each request with the shop's Ed25519 key; Shoper orders come from Shoper's verified webhook. A browser cannot pose as your shop's server: without that signature or webhook, a purchase never counts as a server order.

  • Browser and server copies of one order share an event ID; the server copy wins.
  • The browser purchase waits up to 15 minutes for the server copy before it goes out.
  • Refunds from WooCommerce go to GA4 and to Google Ads as a lower conversion value. Shoper does not offer refunds to apps yet.
  • InPost Pay orders, paid in the InPost app, go out with the consent the shopper gave in their browser; without it they are only counted. In preview until the test on InPost's sandbox is done.
POST /v1/collect X-TH-Signature: t=1762700000,kid=…,ed25519=… { "event_name": "purchase", "event_id": "7f3c…", "ecommerce": { "transaction_id": "10482", "value": 249.00, "currency": "EUR" } }

Collection on your own subdomain, always

Filter lists block tracking hosts. Your own subdomain is not one of them.

Point a subdomain such as rk4vqz.yourshop.com at TallyHost. The script loads from it and events go to it, so filter lists that block known tracking hosts have nothing to match.

  • Certificates are issued for your subdomain automatically after a DNS check.
  • With consent, the identity cookie is set by the server on your domain. For its full life in Safari, the WooCommerce plugin's same-IP mode renews it from your shop's own server.
  • The subdomain is part of installation: the panel shows the DNS records and gives you the install code once the subdomain is live. Server events from the WooCommerce plugin or the Shoper app can start before that, but they reach the platforms only once the script on your pages records the shopper's consent.

Customer data, minimised

Better matching in Meta and Google. E-mail reaches the platforms only as a SHA-256 hash.

Personal data leaves the collection step only in the form each provider requires.

  • E-mail, phone and address are normalised and hashed with SHA-256.
  • IP addresses are truncated in stored history (IPv4 to /24, IPv6 to /48).
  • Page URLs are cleaned: only the host, the path and known campaign parameters stay.
  • Without any consent, the IP, user agent and browser identifiers are removed before the event is stored.
  • The debugger masks identifiers; only owners and admins can reveal them, and each reveal is logged.

An event debugger with the provider's answer

Know in seconds whether Meta took the order, and why not if it didn't.

Every event, its source and consent, and for each destination the result and the provider's response.

ResultWhat it meansWhat you do
SentThe provider accepted the event. GA4 answers this way even to a wrong API secret.Nothing; for GA4, check a test purchase in DebugView once.
On its wayWaiting for the server copy or the next batch.Nothing.
RetryingThe provider did not answer or asked us to wait.Nothing; it goes out on the next try.
No consentThe shopper did not agree to this provider.Nothing; this is their choice.
SkippedThe provider does not take this event, for example a refund to Meta.Read the reason in the row.
FailedRetries ran out or the token stopped working.Fix the cause, then resend from the panel.

Events are kept for 14 days and delivery results for 30 days.

Retries and durability

A platform outage delays your events. It does not lose them.

An event counts as received only after it is written to durable storage. If a provider is down, deliveries wait and retry; your shop does not notice.

  • Retries after 1 minute, 10 minutes, 1 hour and 6 hours; after that you can resend from the panel.
  • Accepted events are kept for 72 hours for delivery, so an outage of a provider does not lose them.
  • A provider that keeps failing is paused for a while instead of being hammered.
  • One account's failing destinations use at most a quarter of retry capacity, so other accounts keep retrying.

Try it on your shop

The free plan has every feature on this page.