EarShots Pixel and Traffic Analytics

1. Send EarShots your workspace name, exact HTTPS origin, and the public paths you want to measure. Start with a single page and one event.
2. Serve /earshots-pixel.js on your site and configure your first-party server to forward POST /api/public/pixel-events to EarShots. Preserve the original Origin and Content-Type headers.
3. Use your consent manager to set window.earshotsAnalyticsGranted to true only after analytics consent. Run the loader after that signal. In Google Tag Manager, use a Custom HTML tag with an analytics consent requirement.
4. When consent is withdrawn, set the flag to false and call window.EarShots?.stop().

<script>
(function () {
  if (!window.earshotsAnalyticsGranted) return;
  if (window.EarShots) {
    window.EarShots.start();
    return;
  }
  if (document.getElementById("earshots-pixel")) return;
  var script = document.createElement("script");
  script.id = "earshots-pixel";
  script.async = true;
  script.src = "/earshots-pixel.js";
  script.dataset.endpoint = "/api/public/pixel-events";
  script.onload = function () {
    if (window.earshotsAnalyticsGranted) window.EarShots.start();
  };
  script.onerror = function () { script.remove(); };
  document.head.appendChild(script);
})();
</script>

Grant analytics consent on an approved page and check for a successful collector request. For a docs link or CTA, call window.EarShots?.track("cta_click") from its click handler. For a single-page app, send page_view once after each approved navigation. Map meaningful signup, activation and checkout events to your site’s data layer.

Open Traffic Analytics in the connected workspace and refresh. Verify that neither a page view nor a test action appears when consent is withheld. Use a tagged campaign for a declared-source test and a real referring link for an observed-source test.

• Overview shows sessions, page views and sessions with at least one recorded action.
• Acquisition shows recorded referrers, campaign tags and unattributed traffic. Switch between the first recorded source and the latest source.
• Engagement shows the number of times each action occurred and how many sessions included it.
• Journeys compares recorded signup and checkout starts with later completions on the same site. Expand a recent session to inspect its event timeline. A missing completion can also mean your site did not send that event.

Reports use UTC and label the cap when the event sample is incomplete. An AI referrer identifies a traffic source. Use separate server instrumentation to record agent API or MCP activity and confirmed payments.

The pixel can report browser actions and traffic sources. To label agent or human activity in Agent Experience, pass the journey ID from window.EarShots?.context() to your backend and use that same ID in your authenticated AXO producer. Sessions with evidence for both actors have their own row. Unlinked sessions appear as Unknown.

The pixel uses first-party storage after analytics consent and clears its local state when you stop collection. The collector saves a public path, timestamp, event and session IDs, action, and classified source. Stored events expire after 30 days.

Keep personal information out of paths and event IDs. Review regional processing, retention, and data handling with your organization before enabling a customer site. Contact EarShots to disconnect a site or request deletion of its stored traffic events.