Install the Sarge pixel and prove every conversion path.

Project dashboard

Select Production, Staging, or Development, then choose a tab. The selected environment stays selected as you navigate.

Overview

Traffic, trends, and event mix for this environment.

Sessions

Follow users and sessions through your site.

Live events

Inspect incoming events and their captured properties.

Diagnostics

Review tracking issues and recommended fixes.

Setup

Install your pixel, test tracking, and connect integrations.

Settings

Manage privacy and data controls for this project.

Overview counts real traffic, excluding test and watchdog events. Sessions loads 80 matching events at a time; load more before treating a journey as complete. Live events shows the latest 12 events. Diagnostics is available for Production on Growth and higher.

Organization admins manage credentials in Setup → Server-side calls and privacy controls in Settings. API export and MCP read access are available on every plan, including Free. Server-event secrets and partner postbacks require Starter or higher.

Copy the exact snippet from Setup → Install pixel for the selected environment. The browser/API payload field is still called `siteId`, but the value is the selected environment ID.

<script>
  window._sarge = { queue: [["track", "page.view"]] };
</script>
<script async src="https://track.sargetrack.app/pixel.js?env={siteEnvironmentId}"></script>

Place it in the document head or as early as possible in the page body. The queued `page.view` call is replayed after `pixel.js` loads. Emit the initial page view once, then another on each SPA route change. Call `window.sarge` only after it loads; earlier calls must use the queue shown in the Markdown guide.

1. Copy the user ID you want to test from the Sarge project page.
2. Open the tracked site, then open the browser console on that page.
3. Run impersonate(userId) before starting the checkout or account flow.
4. Run clear_impersonation() when the test is finished.

impersonate('customer_123');

clear_impersonation();

While impersonation is active, browser events use the impersonated value as `userId` and are marked with Sarge test metadata. This is only debug labeling; it does not authenticate as that user in the tracked site.

The pixel reads `sarge_ref` and `sarge_aff` URL parameters, stores them in localStorage, and attaches them to later browser events during the environment attribution window.

https://shop.example.com/?sarge_ref=summer-campaign&sarge_aff=partner-42

Use `sarge_ref` for the campaign, placement, click ID, or network click identifier. Use `sarge_aff` for the affiliate, creator, publisher, or partner ID.

Latent conversions

Sarge defaults to a 28-day attribution window, checked when the pixel initializes. Later browser events retain that attribution across page loads within the window; a page left open past expiration can continue sending its loaded attribution. For server-confirmed orders or affiliate.conversion callbacks, explicitly send the attribution and matching identifiers from your backend.

Use browser events for page and interaction tracking. Use server-side events for trusted backend facts such as paid orders, refunds, fulfilled subscriptions, or webhook confirmations. Organization admins create the credentials in Setup → Server-side calls on Starter and higher.

curl -X POST "https://track.sargetrack.app/v2/server/events" \
  -H "authorization: Bearer {serverEventSecret}" \
  -H "content-type: application/json" \
  -d '{
    "siteId": "{siteEnvironmentId}",
    "name": "purchase.completed",
    "eventId": "order_123",
    "userId": "customer_123",
    "properties": {
      "order_id": "order_123",
      "value": 129.99,
      "currency": "USD"
    }
  }'

If the backend also calls Meta, Google, or another vendor API directly, report that upstream dispatch as a watchdog event with `transport: "server"` and the returned HTTP status in `properties.upstream`. Add `properties.implementation.note` when AI reviews need project-specific context.

curl -X POST "https://track.sargetrack.app/v2/server/events" \
  -H "authorization: Bearer {serverEventSecret}" \
  -H "content-type: application/json" \
  -d '{
    "siteId": "{siteEnvironmentId}",
    "name": "meta.pixel.fire",
    "eventId": "order_123_meta_purchase",
    "sessionId": "sess_123",
    "userId": "customer_123",
    "properties": {
      "vendor": "meta",
      "transport": "server",
      "command": "track",
      "event_name": "Purchase",
      "payload": { "order_id": "order_123", "value": 129.99, "currency": "USD" },
      "upstream": {
        "endpoint": "https://graph.facebook.com/{api_version}/{pixel_id}/events",
        "status": 200,
        "ok": true,
        "request_id": "fb_req_123"
      },
      "implementation": {
        "mode": "server_gtm",
        "note": "This project does not fire fbq directly. Meta Purchase is dispatched server-side through GTM."
      }
    }
  }'

URL-only partner postbacks are useful when an affiliate network can only call a tracking URL. Keep server event secrets out of browser code and rotate postback tokens if a URL is exposed.

https://track.sargetrack.app/v2/postback/{siteEnvironmentId}/{postbackToken}?event=affiliate.conversion&click_id=click_123&order_id=order_123&value=42.50&currency=USD&aff=partner-42

Webhook destinations belong to the selected project environment. Organization admins on Starter and higher can configure them in Setup.

1. Open the project, select the environment, and open the Setup tab.
2. In Webhooks, enter a name and an HTTPS destination URL.
3. Optionally enter event names separated by commas or newlines, such as purchase.completed. Leave filters blank to select all events.
4. Select Create webhook and copy the signing secret into secure storage. It is shown only once.

Outbound event delivery is not implemented yet. Saving a destination stores its configuration; the configured status does not confirm delivery. Use the read-only export API to retrieve events from your backend today.