Trackdolphin

Every purchase counts.

Trackdolphin reports orders from your shop backend to Google, Meta and the rest, past ad blockers and broken payment returns, and only within what the visitor allowed in the banner. Do not start with us, start with your shop: we measure it once and show you what is not arriving today.

We call your home page once and measure what happens. We change nothing, order nothing and do not sign in anywhere. Free, no account: you get the result in about 15 seconds.

Hosted in Germany
Your shopBrowser−20 to 40 %never arrivesServer · TrackdolphinGoogle AdsMetaGA4every orderAd blockerConsentpayment return

Trusting Trackdolphin

  • Prime Time Fitness
  • haengewelt.de
  • LUXFIT
  • kaminlicht.de
  • Van Volxem
  • deinhaengesessel.de
  • SafeMind
  • deinHandlauf.de
  • Droplion
  • Babywelt Sulingen
  • keramikgrills.com
  • LEWO Media
  • daya-health.de

Why server-side tracking

First the gap, then three reasons that move numbers: not because it is technically more elegant, but because your campaigns live on it.

First the gap

No claim. A number.

After setup, Trackdolphin reads your order history and compares it with what your previous tracking reported. The gaps are filled in, and for the first time you see what was really missing. The three cards below say why the gap appears and what changes once it is closed.

How the match rate is calculated →

Event quality at Meta

A 4 becomes an 8.

Meta rates every incoming conversion with a quality score. A pixel in the browser delivers little: no email, no phone number, often not even the click ID. From the server, all of it comes along (hashed, never in plain text). The score goes up, and with it how well Meta finds your buyers again.

Campaign performance

CPM goes down. ROAS goes up.

Google Ads and Meta bid on the conversions they can see. If they see all of them, they find the right users more cheaply (the price per thousand impressions drops), and every euro of budget brings back more revenue. That is no trick, it is the same algorithm with complete data.

Learning phase and audiences

Out of the learning phase sooner. More precise afterwards.

At Meta, an ad set needs around fifty conversions a week to leave the learning phase. Report only two thirds of your purchases and you stay stuck in it longer, or never get out. With complete data the learning phase is over in days, lookalikes are built from real buyers, and whoever bought does not see the ad again.

So how does it work?

Three stations. You already know the first and the third. Trackdolphin sits in between.

  1. 1

    Your shop reports

    • WooCommerce
    • Shopware
    • Shopify

    The plugin reports every order from the backend as soon as it exists, not only once the browser shows the thank-you page. Without a plugin it works through the API or the SDK.

  2. 2

    Trackdolphin checks and distributes

    • Trackdolphin

    Every event is received once and passed on to all connected platforms, in the format each one requires.

    • Deduplicated against your existing pixel
    • Hashes email and phone: platforms never receive plain text
    • Honours consent (configurable per project)
    • Speaks up when nothing arrives any more
  3. 3

    Your platforms receive

    • Google Ads
    • Meta
    • Google Analytics 4
    • LinkedIn
    • TikTok Ads
    • Pinterest
    • Microsoft Ads

    Google Ads sees the purchase with the click ID, Meta with hashed customer data, GA4 with the client ID. Each one gets what it needs to attribute.

What Trackdolphin does differently

Values from the shop

The amount comes from the order (the same one the invoice shows). Not from a data layer that breaks with the next theme update.

Never counted twice

One event_id from the browser all the way to the platform. If a purchase arrives on both paths, it counts once.

Refunds are corrected

Refunds reduce the reported revenue. Otherwise your ROAS looks better than it is, exactly when money is going back out.

The watchdog speaks up

An outage is silent: the site runs, only the measurement does not. Every six hours we compare against the same weekday of the previous weeks, and write to you.

Match quality, done right

Phone numbers in E.164: for Meta without, for Google with a plus sign, because the two contradict each other. A wrong hash never matches and never says so.

Plain text stays with you

Hashing happens before sending. The collector rejects plain-text PII with a 400 instead of accepting it and writing „SHA-256“ on top.

Session recording

Your recordings suddenly know where the visitor came from

Microsoft Clarity records, but knows nothing about advertising channels. Trackdolphin writes that knowledge into your recordings as filters: channel, campaign, consent state and order value. That lets you filter by things Clarity could never know on its own, and instead of ten thousand sessions you see the few dozen where money was really at stake.

  • One field, not a second script. We do not load Clarity, we label it. Your project stays yours.
  • No personal data. No visitor, no order, no amount: only channel, campaign and value band.
  • Consent first. Before the visitor has decided, nothing goes out.
  • The same for PostHog and Sentry. The same properties, the same principle. If PostHog runs with session replay, you jump from a lost conversion straight into the recording. How this works

Microsoft Clarity is a Microsoft product and stays in your account. Trackdolphin is not a Microsoft partner.

Recordings Microsoft Clarity
Filter td_channelgoogle_paidtd_value_band250_500
12.480 sessions
  • Checkout abgebrochen 9 Seiten · 4:12
  • Checkout abgebrochen 6 Seiten · 2:48
  • Zahlart gewechselt 12 Seiten · 6:03
Example figures. The SDK sets the tags exactly like this.

API · MCP · command line

Built for agents, not retrofitted

The dashboard uses the same endpoints you do. The MCP server and the command line derive their capabilities from the OpenAPI description: a new endpoint is immediately a new tool. And the docs are available as raw text from the same source as these pages.

Pricing

Every tier includes all platforms, the API, MCP and the command line. That is not an add-on, that is the product. You pay for size, not for capabilities.

Free

0 €

To try it out and for small projects.

  • 1 project · 10,000 events/month
  • All platforms: Google Ads, Meta, GA4, LinkedIn
  • Order history import with match rate
  • API, MCP server and command line
Start for free

Events count on receipt, not per platform: a purchase going to four destinations is one event. Refunds and the order history import never count against your quota.

What users say

The order history import showed us 9 % of orders that never arrived in the ad account. The conversation with the client was a different one after that.
E Example A Performance agency (placeholder)
The watchdog email arrived at seven on a Sunday: a plugin update had removed the snippet. By Monday morning everything was running again, before anyone would have noticed.
E Example B Shop owner, WooCommerce (placeholder)
I ask Claude about the delivery rate instead of logging in. You can tell that the MCP server simply mirrors the API: a tool is never missing.
E Example C Freelance developer (placeholder)

Official partner

Trackdolphin is part of the Google and Meta partner programmes. That means verified certifications, direct access to the interfaces and early information when something changes there.

Google Partner: certified for Google Ads Search, Display, Google Analytics and Measurement
Google PartnerAds · Analytics · Measurement
Meta
Meta Business PartnerConversions API · Pixel

Frequently asked questions

Do purchases count twice if the browser and the server both report them?

No. Both paths carry the same event_id, and the platforms deduplicate on it: if a purchase arrives on both paths, it counts once. So you can simply keep your existing pixel running. More about events

Does plain-text customer data leave my shop? And what about the GDPR?

Hashing happens before sending: in the plugin, in the SDK, on your server. The collector does not even accept plain text in an email address or phone number, it rejects it with a 400. Processing and storage are in the EU. Privacy details

What happens if someone pays with PayPal and never sees the thank-you page?

Exactly the case Trackdolphin is built for: the purchase is measured in the shop backend, not on the thank-you page. Whether the return trip breaks makes no difference: the order exists, so it is reported.

How long does setup take?

Upload the plugin, enter two values, connect the platforms via OAuth: realistically a quarter of an hour. After that the order history import runs and shows you the match rate of your previous setup. To the guide

Can I cancel at any time?

Yes: monthly, at the end of the billing period. Your account then falls back to the free tier, it does not disappear.

What counts as an event?

Every event once on receipt, no matter how many platforms it goes on to. A purchase going to Google, Meta, GA4 and LinkedIn is one event. Refunds and the order history import never count against your quota.