Tracking data looks wrong

This page covers the usual reasons conversion numbers look off: events counted twice, events that never arrive, Whop checkout purchases counted twice, and RedTrack numbers that don't line up with Meta.

Conversions are counted twice

Why it happens. Two things report the same conversion and Koast can't tell they're the same. The browser pixel and your server (or a tracker like ClickFlare) both send it, with different event_id values.

How to fix it. Send the same event_id from the browser pixel and from your server for the same conversion. When they match, the conversion is counted once. See Server-side conversions.

Only the first conversion counts

Why it happens. Every event carries the same event_id. That happens when a macro in your tracker, such as {txid}, isn't filled in, so every event gets the same ID. Each one after the first looks like a duplicate and is dropped.

How to fix it. In your tracker, pick the macro from its own list rather than typing it, and check a test event to confirm event_id arrives as a real, unique value.

Server-side events are rejected

Why it happens. The ip_address field holds more than one address. Some trackers pass a comma-separated chain of forwarded addresses.

How to fix it. Send only one IP address, 45 characters at most. If you get a chain, send the first entry.

Purchases are doubled on Koast ad accounts

Why it happens. Purchases made through Whop checkout are already tracked automatically. If your pixel or your server also sends purchase for them, each sale counts twice.

How to fix it. Fire purchase only for sales on your own checkout, with the sale amount as a positive value. Never resend a sale Whop processed. If your page is hosted on Whop, the Pixel tab says "Tracked automatically" and you don't need to fire purchases at all.

The pixel shows no conversions

The Pixel tab tells you where it stands:

• Only page views are tracked. The snippet is live, but no conversion event has fired. Add the event calls to your funnel. See Set up the Koast pixel.
• No activity for N days. The pixel has gone quiet. Check the snippet is still on your live pages.

Events take a few minutes to be counted, and server-side events show up within about 15 minutes.

RedTrack numbers don't match

• Today looks low. Koast imports RedTrack once a night, at 3:00 UTC, for the day before. Today's numbers are partial or missing until the next run.
• Days are shifted. RedTrack splits days by the timezone set on your RedTrack account. If that isn't UTC, days in Koast can be offset from days in Meta by your UTC offset. Setting your RedTrack account to UTC avoids it.
• Some traffic is missing. Koast matches RedTrack data to your campaigns by the Meta IDs in sub3 (campaign), sub2 (ad set) and sub1 (ad). If your RedTrack tracking link still contains a raw macro such as {{adset.id}}, the ID was never filled in and that traffic can't be matched. Check the tracking template on your Meta ads.
• A lot of traffic has no source. Koast only keeps traffic whose RedTrack source is facebook. Traffic with no source, or a different one, is left out. That's usually your other ad channels and is expected.

See RedTrack.

Still stuck?

Send us the ad account, the date range and the numbers you expected against the numbers you see. Still stuck? Message us from the chat bubble.