<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/cebb27dcd4b941caa0632de0853fb5db&quot; frameborder=&quot;0&quot; width=&quot;3840&quot; height=&quot;2880&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>2880</height><width>3840</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>2880</thumbnail_height><thumbnail_width>3840</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/cebb27dcd4b941caa0632de0853fb5db-6a7f53442593616b.gif</thumbnail_url><duration>65.5</duration><title>Kaminari Click | Features | S2S Ping | EN</title><description>In this video, I explain the Server to Server Pink (S2S Pink) system, which ensures double-confirmation for each click through a unique community ID. Our process begins with my server sending a guaranteed pink to a community, which the browser cannot block. Then, our JavaScript checks for a second signal from the browser to confirm the device data. If we receive the pink but not the check, we record it as a technical loss, similar to buying an airline ticket but not showing up at check-in. I encourage you to familiarize yourself with this system to better understand how we track and confirm clicks.</description></oembed>