Start with the event journey
Klar’s server-side Pixel integration accepts HTTP POST requests and needs a Klar Pixel data source. Create the source for the correct store and keep its dataSourceId attached to the events you send.
Decide what each event means
Before implementation, make a small event map: what happened, which system observed it, and when it should be reported. A product view and a completed order have different owners. Define those owners so a browser action and a backend update do not accidentally describe the same outcome twice.
Preserve the context
Match your payload to Klar’s current event schema. Treat visitor identity, timestamps, page context, and consent as part of the implementation—not details to add after launch. An accepted request alone does not prove that an event is linked to the intended journey.
Test one complete journey
Use a controlled test from product discovery through checkout. Write down the expected events, then compare them with the records you can observe. Check a repeated notification and a failed request as well as the successful path. Agree how your integration handles retries before enabling live traffic.
Make the handover useful
Document field ownership, the event map, and the steps for investigating missing data. Give the next person enough context to trace one order without guessing. Review the mapping whenever checkout or the shop backend changes.
Explore Klar tracking