Ad blockers and cookie rules hide some conversions from any browser pixel. Server-side conversions close that gap: your server, or your tracker, sends the conversion straight to the Koast pixel with a key you create in Koast. Keep the browser pixel in place too. The two work together.

Before you start

• This is for Koast ad accounts, which are provided through our partner Whop.
• Set up the browser pixel first. See Set up the Koast pixel.
• You need someone who can change your server code or your tracker's settings.

Create a key

1. Open Settings, then Pixel, and scroll to Server-side tracking, marked Optional.

2. Select Create key. Type a name you'll recognise, for example "Checkout server", and select Create key again. Names are 2 to 60 characters.

3. Select Copy key and store the key somewhere safe. It's shown once, so copy it now.

4. Select I saved it. The key stays listed with its first characters and Active, and the count goes up, for example 1 of 3 keys created.

Select API instructions to copy a ready-made set of instructions, with your ad account ID already filled in, for your developer or an AI coding agent.

Send an event

Send a POST request to https://api.whop.com/api/v1/events with your key in the Authorization header:

curl -X POST https://api.whop.com/api/v1/events \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"account_id":"biz_7Qm2NimbusSleep","event_name":"lead","event_id":"order_1234",
       "value":49.99,"currency":"usd","action_source":"website",
       "user":{"email":"buyer@example.com"},
       "context":{"fbclid":"...","ip_address":"...","user_agent":"..."}}'

The event is acknowledged right away and shows up within about 15 minutes.

Supported events: lead, complete_registration, submit_application, schedule, contact, view_content, add_to_cart and purchase.

Rules that keep your numbers right

• Match the browser pixel's event_id. When the browser and your server report the same conversion with the same event_id, it's counted once. Different IDs count it twice.
• Keep event_id unique per conversion. If a macro such as {txid} isn't filled in, every event carries the same ID and all but the first are dropped as duplicates.
• Send one IP address, 45 characters at most. If your tracker sends a comma-separated chain of addresses, send only the first one. Anything longer is rejected with "ipAddress is too long (maximum is 45)".
• Don't resend Whop checkout purchases. Purchases through Whop checkout are already tracked. Send purchase only for sales on your own checkout.

Send conversions from a tracker

Trackers like RedTrack, Voluum and BeMob send conversions as a postback: a plain GET URL with macros in it. The events endpoint needs a POST with your key in the Authorization header, which a postback can't carry. So put a small relay in between, such as a Zapier or Make webhook, or a short script on your own server.

Koast's RedTrack, Cometly and Hyros integrations only read data into Koast. They don't send conversions anywhere, so you still need this relay.

1. Create a webhook in Zapier (Webhooks by Zapier, Catch Hook) or Make (Custom webhook) and copy its URL.

2. In your tracker, set that URL as the postback URL for your traffic source, with the tracker's macros as query parameters, for example https://hooks.example/abc?txid={txid}&payout={payout}&fbclid={fbclid}&ip={ip}&ua={ua}. Macro names differ per tracker, so pick them from its list.

3. Add a step that sends a POST to https://api.whop.com/api/v1/events with the headers Authorization: Bearer YOUR_KEY and Content-Type: application/json, and a JSON body built from the query parameters, mapped as below.

4. Fire a test conversion in your tracker. It shows up within about 15 minutes.

Using ClickFlare? It can send the POST itself, with no relay. See ClickFlare.