Connect Kwai Ads (Pixel and Event API)

With Kwai Ads connected, the Kwai pixel fires on the checkout and the thank-you page. With the Event API token, Vipter also sends the sales from the server, including a PIX (Brazil's instant payment) paid after the buyer closed the page.

Kwai only accepts server events from buyers who came from one of its ads, identified by the click_id parameter in the address. That is why the account works like a postback: with the token, it shows Browser + postback.

Before you start, it helps to read how conversion tracking works.

Step 1: copy the pixel ID and generate the token in KwaiCopy Anchor Link

1. In Kwai for Business, open Assets›Pixel and choose your pixel.
2. Copy the pixel ID, numbers only, such as 525567814242672725.
3. In the pixel settings, click Generate access token and copy the token.

Step 2: carry the click_id to the checkoutCopy Anchor Link

Without the click_id, nothing goes out from the server. Prepare the ads' URL before selling.

1. In the ad's destination URL in Kwai, add click_id=__CALLBACK__. Kwai replaces the __CALLBACK__ macro with the identifier of each click.
2. Also add utm_source=kwai. The Sales sources report only puts the sale in the Kwai Ads channel when the utm_source contains "kwai" or "snack" (from SnackVideo), because other networks also use the name click_id.
3. If the ad leads to a sales page on another domain, paste the UTM script on it. It carries the click_id and the UTMs to the checkout.

A ready destination looks like this:

https://yourstore.com/offer?utm_source=kwai&click_id=__CALLBACK__

If the URL already has a ?, join the new parameters with &.

Step 3: connect the account in VipterCopy Anchor Link

1. In the Vipter dashboard, open General›Conversions›Accounts and click Connect account. Choose Kwai Ads.
2. Fill in the numbered fields. Test mode is under Advanced: test mode.

3. Click Connect and verify. Vipter saves the account and checks the ID's format. The token is not tested now: Kwai only accepts events from buyers who arrived from the ad with its click_id. The token is confirmed on the first sale that comes from an ad.
4. Click Continue, check the products the pixel should fire on and click Finish. Turn on Use automatically on new products to include products created later.

Step 4: testCopy Anchor Link

Kwai refuses events without a click on an ad, so the account has no test event button. The verification completes by itself:

1. Open the account in Accounts, on the Connection tab, and click Verify now.
2. Once the first buyer fills in their details at the checkout, the list shows the first event received.
3. After the first sale from a Kwai ad, the list shows the first sale sent from the server. In General›Conversions›Activity, the purchase shows on the Server channel as EVENT_PURCHASE.

What Vipter sends to KwaiCopy Anchor Link

• Kwai has no custom events. PIX generated goes as an order placed (EVENT_PLACE_ORDER).
• Kwai does not receive Shipping chosen, Renewal or Refund / chargeback.
• Without a token, every enabled event goes out from the browser.
• With a token, Page view, Checkout started and Payment started stay in the browser. Lead (contact filled), PIX generated, Purchase and Subscription started go out only from the server, and only for buyers who arrived with the click_id. Kwai does not document how to join the browser event with the server one, so each of these events goes out by a single path, which keeps the sale from counting twice.
• Events carry value, currency, the product, the quantity and, from the server, the order ID.
• Kwai finds who clicked only by the click_id. That is why the account has no Matching data card, and no buyer data goes to Kwai.
• In What to send, choose the events, the Conversion value and the Value currency. See events and values.

With a token, a sale from someone who didn't come from a Kwai ad doesn't reach Kwai. Without the click_id, Kwai couldn't link that sale to an ad either.

Common problemsCopy Anchor Link

• Server delivery only happens when the ad brings its click identifier; without it, a PIX paid after the page was closed is not counted.

  The ad doesn't carry click_id=__CALLBACK__ in the URL, or the click_id gets lost on the sales page. Check step 2 and paste the UTM script on the sales page.

• Kwai sales show in Other campaigns (UTM) or Direct / no source in the report

  The ad's utm_source contains neither "kwai" nor "snack". Add utm_source=kwai to the destination URL. Older sales stay in the channel they went into.

• Events with the Skipped status and the no_click_id reason

  The buyer didn't come from a Kwai ad, or arrived without the click_id. For buyers who didn't come from an ad, this is expected.

• Server deliveries fail in the activity

  Kwai answers {"result":1} when it accepts the event. Any other answer is a refusal, and a refusal gets no automatic retry. Common causes are a token from another pixel, a wrong pixel ID or a click_id that didn't come from Kwai. Generate another token, check the ID in Connection and resend the event in Activity.

• Your plan does not allow another account sending from the server. Upgrade to connect one more.

  The plan has reached its limit of accounts with server delivery. Remove the token from an account you no longer use or change plans in Vipter plan.

What to do nextCopy Anchor Link

• Paste the UTM script on your sales page so you don't lose the ad's click_id.
• See where sales come from in the Sales sources report.
• Also connect TikTok Ads.