Full Guideline — About Kwai Account Pixel Setup

Before you begin optimizing your ad campaigns, properly setting up your Kwai account is crucial. In particular, correctly configuring your Kwai account's pixel settings can allow for more accurate tracking of ad data.You can use the following steps as a reference:

How to set up your pixel

• 1.Go to your operations back office, click on Assets, then select Web Events
  
• 2.Choose Standard Mode
• 3.Copy the base code and install it on both your Landing page and Moneysite
• 4.Finally, download the pixel helper
• 5.Your LP needs another section of code placed on it:
<script>
window.onload = function () {
var links = document.getElementsByTagName("a");
for (var i = 0, n = links.length; i < n; i++) {
var href =
links[i].href.trim() +
(links[i].href.indexOf("?") > 0 ? "&" : "?") +
document.location.search.replace("?", "").toString();
links[i].href = href;
}
};
</script>
• 6.Use the Pixel Helper to verify that the pixel is properly triggered on both your Landing page and Moneysite

How to set up pixel event

1.Set up the events you want to track based on your specific needs; the three basic events are:

• View Content
• Complete Registration
• Top-Up Completed

2.Three ways to set up the event

3.View content:choose Enter URL Keywords, then insert your LP link

4.Complete Registration&Recharge: Select Web Elements, selecting the button for registration (on your ms site) and the button for recharge as tracking elements (on your ms site).

5.Once all pixel events are set up, test to ensure the preview events are showing

Pixel problem self-check

Data gap

Problem definition: There is a gap between the data reported by the customer and the data reported on our ads manager platform.

Pre-understanding: Data gap is just a phenomenon. We need to clarify the core demands of customers. For example, the core demand of customers is that the account volume is not increasing, the account volume is decreasing, or the cost is over. Feedback the core demands to sales operations, and we will arrange solutions based on the core demands.

• Number of customer backend < number of Kwai backend
  No need to solve; Kwai receives a lot of data, which is convenient for running volume. If you want to control costs, you can calculate the cost based on the customer backend and calculate the platform bid based on the number of returns.
• Number of customer backend > number of Kwai backend
  This may cause Kwai to fail to achieve volume, so the problem needs to be investigated. The specific troubleshooting ideas are as follows.

Troubleshooting Guidelines：

1. Time Calibration
   Advertisers should provide the time interval and time zone where the data discrepancy occurs.
2. Event Calibration
   Verify whether the client-side event trigger is consistent with the pixel event trigger used for tracking.
3. Inconsistent Definition of Data Indicators
   For example, in the case of deduplicated payment events:
   On Kwai’s DSP delivery platform, deduplication is based on Creative ID and Request ID.
   On the customer’s backend, deduplication may be based on User ID.
   Although both are labeled as “deduplicated payments,” the statistical definitions differ, leading to data discrepancies.
4. Inconsistent Reporting Processes
   For example, when tracking registration events:
   On Kwai’s side, the reporting process is:
   User registers on the front end → Front end sends data to the backend → Backend confirms and returns → Front end triggers report to Kwai.
   On the customer’s backend, a registration is recorded as soon as the backend receives the registration request.
   Because Kwai’s reporting chain is longer, delays or deductions may occur, resulting in data gaps.
5. Inconsistent Tracking Points
   For example, for registration counts:
   The website may have multiple pages where users can register.
   The customer’s R&D team may only track and report a few of these pages to Kwai.
   However, the backend counts all registration behaviors, causing a data mismatch.
6. Data Calibration
   Confirm whether the data attribution standard is consistent between Kwai and the customer’s backend.
   Exposure-based calibration: Records event data on the day the ad is shown.
   Conversion-based calibration: Records event data on the day the event actually occurs.
7. Channel Clarity
   Verify whether the customer’s backend data includes only Kwai traffic, or if it is mixed with other channels and organic traffic.
8. Attribution Calibration
   If only the Kwai channel is being analyzed, clarify how the customer attributes events to Kwai.
   For instance:
   Kwai attributes events that occur on landing pages opened within the Kwai app, or user actions on shared ad landing pages, to the Kwai channel.
   If the customer uses a different attribution model, data discrepancies may arise.
Division of investigation:Agent: Pre-investigate customer problems based on time caliber, data caliber, and event caliber.

If there is still a data gap after the caliber is aligned, clarify the customer problem and organize the following information for PSO:

• 1.Account ID:
• 2.URL for delivery:
• 3.Pixel ID:
• 4.Event name with gap:
• 5.Time Period + time zone:
• 6.Event scope:
• 7.Data scope:
• 8.Attribution scope:
• 9.Data comparison excel under unified scope:
• 10.Related screenshots:

FAQ