<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Server-Side Tracking on pxta.com</title>
    <link>https://pxta.com/tags/server-side-tracking/</link>
    <description>Recent content in Server-Side Tracking on pxta.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 25 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://pxta.com/tags/server-side-tracking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What a Browser Tracking Audit Can&#39;t See, Server-Side Tagging and Conversion APIs</title>
      <link>https://pxta.com/what-a-browser-tracking-audit-cant-see-server-side-tagging-and-conversion-apis/</link>
      <pubDate>Sun, 25 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://pxta.com/what-a-browser-tracking-audit-cant-see-server-side-tagging-and-conversion-apis/</guid>
      <description>&lt;p&gt;PXTA watches what leaves the browser. That covers most tracking on most websites, and it&amp;rsquo;s where the consent questions are sharpest, because it&amp;rsquo;s the visitor&amp;rsquo;s own device doing the sending. But it&amp;rsquo;s not everything, and a report that says nothing about the rest would be easy to misread.&lt;/p&gt;&#xA;&lt;p&gt;So here&amp;rsquo;s the part a browser can&amp;rsquo;t see, stated plainly.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://pxta.com/images/server-side.png&#34; alt=&#34;A diagram: the browser sends to facebook.com/tr, which PXTA sees; the browser also sends an order to the site&amp;rsquo;s server, which then sends data to Meta through the Conversions API, a path that never passes through the browser.&#34;&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
