Server-side tracking for WooCommerce and Shoper

Get back the orders your pixel misses.

Where the pixel loses orders

Four gaps, and how a copy from your server closes them.

Blocked

Ad blockers stop pixel requests. Your shop's server is out of their reach.

Forgotten after 7 days

Safari keeps script cookies for a week. With same-IP mode on, the WooCommerce plugin renews them from your shop's server.

Never loaded

Paid by bank link, tab closed. The WooCommerce plugin reports the order once it is paid.

Counted twice

Meta and TikTok match the event ID, GA4 and Google Ads the transaction ID. Each order counts once.

Live in three steps, on any shop

No tag manager container. No server to run.

  1. Install

    A few DNS records for your own subdomain, then the WooCommerce plugin, the Shoper app, or one script from that subdomain.

  2. Connect

    Meta, TikTok, GA4 and Google Ads. A test event goes out before anything is saved.

  3. Watch

    Every event and every platform's answer in the debugger.

Any shop. One script.

No plugin for your platform? Point a subdomain of your shop at TallyHost with a few DNS records, paste one script from your domain into the <head> of your pages, and send orders from your server with a signed request. The panel shows the records and, once the subdomain is live, the exact code.

<script async src="https://rk4vqz.yourshop.com/s.js"
  data-pk="pk_…" data-site="…"></script>
  • WooCommerce plugin
  • Shoper app, not in the Shoper App Store yet
  • Any other shop script and server API

Every answer, on record

“Sent” means the platform accepted it. No consent is a result, not an error. Failures retry on their own.

Eventsexample data
EventSourcePlatformResult
PurchaseShop serverMetaSent
PurchaseShop serverTikTokNo consent
PurchaseBrowserMetaServer copy kept
Add to cartBrowserMetaRetrying

Consent decides. Every time.

Flip the switches the way a shopper might. Each platform gets an event only with the consent it needs.

The shopper's consent

Google Consent Mode, without an IAB TCF banner.

Ad cookiesad_storage
Ad dataad_user_data
Personalised adsad_personalization
Analyticsanalytics_storage
Meta
TikTok
GA4
Google Ads
Hashed

E-mail, phone and address leave only as SHA-256 hashes.

Shortened

IP addresses are truncated in stored event history.

In the EU

Servers in the EU. A data processing agreement with every account.

Start free. Grow when you need to.

The debugger on every plan. Free connects 3 destinations at a time. Prices per month, net.

Free

€0

100,000 events, 1 site, 3 destinations

Start

€35

500,000 events, 1 site

Growth

€79

1.5 million events, 2 sites

Agency

€209

5 million events, 15 sites

Compare plans

Questions

Does it work with my cookie banner?

Yes, if the banner sets Google Consent Mode v2 or IAB TCF. With IAB TCF, Google Ads also needs consent for Google as a vendor, Meta needs Google's Additional Consent for Meta, GA4 gets hashed data only with Google's vendor consent, and TikTok gets nothing.

Do I keep the Meta Pixel and gtag?

Yes. The browser covers page views and the ad click. TallyHost adds the server copy of the purchase with the same event ID, so Meta counts the order once. GA4 gets purchases, refunds and leads from the server; page views stay with gtag.

Which shop platforms work?

WooCommerce: a plugin for WordPress 6.4, WooCommerce 8.0 and PHP 7.4 or newer. Shoper: an app that is not in the Shoper App Store yet. Any other shop: one script and signed server requests.

What if I go over my monthly events?

At 80 % and 100 % you get an e-mail and a banner, and events keep flowing. From 150 % until the month ends, only purchases, refunds, leads and sign-ups are accepted.

Are refunds sent?

From WooCommerce: to GA4 as refunds, and to Google Ads as a lower conversion value. Google ignores value updates for the first 14 days after a conversion action starts receiving server conversions. Meta and TikTok do not accept refunds, and Shoper does not pass refunds to apps; the debugger shows both.

Do InPost Pay orders reach the platforms?

In preview, on every plan, until the test on InPost's sandbox is done. An order goes out only with the consent the shopper gave in the browser; without proof of consent it is only counted. The integrations page describes both ways to connect.

Send your next order from the server

Create an account, install the plugin or app, and send a test event.