Which TikTok events count as a purchase?

TikTok's purchase events, such as CompletePayment and Purchase, depending on your setup.

Can it see the TikTok Events API?

No. Server-side events don't pass through the browser.

My confirmation page needs an order. Will it work?

It sees whatever renders without an order context. Use a URL from a real test order if it stays accessible.

Does it check deduplication?

It focuses on whether the purchase fires with value and currency. If you also send server events, use a shared event ID on both.

Is anything purchased?

No. The scan only loads the confirmation page you supply; it never starts or completes a checkout.

Free tool by Clarvivo · no login

Check whether TikTok sees a usable purchase event

Inspect a public confirmation page passively for TikTok browser events without touching checkout.

Public confirmation page

Inspect the public page where a TikTok purchase event should fire. The scan remains passive and never starts or completes checkout.

This tool answers: Does TikTok receive a browser-side purchase event with usable value and currency?

Enable JavaScript to run the check — the diagnosis itself is free and needs no account.

Why this happens

TikTok's ad optimisation depends on purchase events with usable values. If the TikTok Pixel doesn't fire on the confirmation page, or fires a purchase without value and currency, campaigns optimised for purchases or value have little to learn from and drift toward cheap, low-quality traffic.

TikTok Pixel setups break in familiar ways: the Pixel is installed through an app that doesn't cover every checkout path, the purchase event is named differently from what the campaign optimises for, or value is missing because the template variable changed.

This checker loads your confirmation page and reports whether the TikTok Pixel fired, whether a purchase event was sent, and whether it carried value and currency.

Next checks

These answer the questions this one tends to raise.

How this check works

So you can trust the result — and your developer can verify it.

We load your confirmation page
The public order-confirmation URL is opened in an isolated browser. We never start or complete a checkout.
We capture TikTok Pixel requests
Requests to TikTok's pixel endpoint are recorded with their event names.
We check the purchase event
We report whether a purchase event was observed and whether it includes value and currency.

Common causes and fixes

Pixel missing from the confirmation page: Apps sometimes install the Pixel on the storefront but not on checkout or thank-you pages hosted elsewhere.
Purchase event not configured: If only PageView fires, the purchase event isn't set up or fires on a different page.
Value and currency not mapped: Map value and currency from the order data. Without them, value-based optimisation can't work.
Consent blocks the Pixel: If consent isn't granted on the confirmation page, the Pixel may not fire at all.

Frequently asked questions

Which TikTok events count as a purchase?: TikTok's purchase events, such as CompletePayment and Purchase, depending on your setup.
Can it see the TikTok Events API?: No. Server-side events don't pass through the browser.
My confirmation page needs an order. Will it work?: It sees whatever renders without an order context. Use a URL from a real test order if it stays accessible.
Does it check deduplication?: It focuses on whether the purchase fires with value and currency. If you also send server events, use a shared event ID on both.
Is anything purchased?: No. The scan only loads the confirmation page you supply; it never starts or completes a checkout.

Make TikTok reporting answer to payment truth.

Clarvivo links paid-social signals to real revenue.

Connect TikTok to revenue

What this tool reads, and what it keeps

We load the public URL in an isolated browser and inspect public document and tracking signals.
We do not log in, submit forms, complete checkout, or retain a page recording.
Redacted diagnostic evidence is retained for 7 days, then deleted.