Skip to main content

Attribution pixel

The pixel is a lightweight JS script that detects traffic arriving from AI platforms on your site and ties it to the visitor's session. It provides the hard level of proof in order attribution — without the pixel, attribution relies solely on declarations and the probability model.

Installation​

A ready snippet (with your workspace identifiers filled in) is available in the app: AI Attribution → Install pixel. It looks like this:

<script async src="https://geoplatform.pl/api/attribution/pixel.js?w=WORKSPACE_ID&t=TENANT_ID"></script>

Rules:

  • One tag for the whole site — placed in the template (e.g. the layout <head> or via a tag manager), not just the homepage. Conversions rarely happen on the landing page.
  • The script loads asynchronously and doesn't block rendering.
  • The event-collecting endpoint requires no authentication — identification comes from the w/t parameters in the tag.

What the pixel collects​

  • page entries together with the AI source (ChatGPT / Perplexity / Gemini referrer and UTM parameters),
  • a visitor and session identifier (to stitch the visit to a later order),
  • pageviews within the session.

The pixel does not collect form contents or payment data. Events feed a daily rollup; raw events are subject to retention.

Verifying the installation​

  1. Visit your site with ?utm_source=chatgpt.com (simulating an AI entry).
  2. In the app, open AI Attribution — the "pixel not detected" banner disappears after the first received event, and the Distribution module stops showing its warning.

FAQ​

Does the pixel slow the site down? No — it loads asynchronously, and events are sent with a lightweight background beacon.

Can a consent manager block it? Yes, if it's registered as a marketing script. Consult the category with your legal team — the pixel serves order attribution analytics.

I have several domains / shops. Install the same tag (with the right workspace identifiers) on every domain that leads to a purchase.