---
title: "Buyer analytics"
description: "Forward SeatPicker journey events to PostHog, Google Analytics, or your own telemetry system."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.seatlayer.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Buyer analytics

`SeatPicker.onAnalytics` is an optional callback that lets your application route
buyer journey events to any analytics system. SeatLayer does not require or
select the destination.

> **Event names are Preview**
>
> The callback is public, but the current event catalog covers the 3D buyer
> journey and may expand or change before it is declared stable. Treat unknown
> events as valid and avoid using this stream as a billing or transaction
> authority.

## Add a provider adapter

### PostHog

```js
const picker = new seatlayer.SeatPicker({
  container: "#picker",
  event: "ev_9f3a",
  onAnalytics: (event, properties) => {
    posthog.capture(`seatlayer_${event}`, properties);
  },
});
```
### Google Analytics

```js
const picker = new seatlayer.SeatPicker({
  container: "#picker",
  event: "ev_9f3a",
  onAnalytics: (event, properties) => {
    gtag("event", `seatlayer_${event}`, properties);
  },
});
```
### Custom endpoint

```js
const picker = new seatlayer.SeatPicker({
  container: "#picker",
  event: "ev_9f3a",
  onAnalytics: (event, properties) => {
    navigator.sendBeacon(
      "/analytics",
      JSON.stringify({ event, properties }),
    );
  },
});
```

Every property object includes `surface: "buyer"`. A throwing callback is caught
inside the picker and does not interrupt rendering, but your adapter should still
fail quietly and avoid synchronous network work.

## Current event catalog

| Event | Additional properties | Emitted when |
|---|---|---|
| `3d_opened` | `seats`, `hasHeights` | The interactive venue view opens |
| `3d_orbit_engaged` | — | The first real orbit/dolly gesture in this 3D mount occurs |
| `3d_seat_picked` | `seatId`, `sectionId?` | The buyer picks a seat from 3D |
| `3d_cinematic_played` | `durationMs`, `reducedMotion: false` | The seat approach animation completes |
| `3d_cinematic_skipped` | `reducedMotion: true` | Reduced-motion preference skips the animation |
| `3d_cinematic_cancelled` | — | The active cinematic is cancelled |
| `3d_panorama_opened` | — | A view-from-seat panorama opens |
| `3d_panorama_closed` | `viewMs` | The panorama closes |

All rows also include `surface: "buyer"`.

## Use a stable internal envelope

Decouple your product analytics from Preview names by wrapping them:

```ts title="browser/seatlayer-analytics.ts"
type SeatLayerJourneyEvent = {
  schemaVersion: 1;
  source: "seatlayer";
  name: string;
  occurredAt: string;
  properties: Record<string, unknown>;
};

function forwardSeatLayerEvent(
  name: string,
  properties: Record<string, unknown>,
) {
  const event: SeatLayerJourneyEvent = {
    schemaVersion: 1,
    source: "seatlayer",
    name,
    occurredAt: new Date().toISOString(),
    properties,
  };

  productAnalytics.capture("buyer_seat_journey", event);
}
```

Your warehouse or dashboard can then map the Preview name without requiring SDK
callbacks throughout the codebase.

## Product questions these events can answer

- How many buyers discover and open the 3D venue view?
- Does interaction with 3D correlate with seat selection?
- How often is the cinematic skipped because of reduced-motion preference?
- Which sections receive the most 3D seat picks?
- Do buyers open a view-from-seat panorama, and how long do they inspect it?

These are journey signals, not proof that a hold, payment, or booking succeeded.
Use checkout responses, orders, and signed webhooks for transactional analytics.

## Privacy and resilience

- Do not attach buyer email, name, payment data, or unneeded identifiers.
- Confirm that seat and section identifiers fit your privacy policy.
- Respect the consent model already used by your application.
- Sample or batch in the analytics provider, not inside critical picker logic.
- Accept unknown names so a newly added event cannot break the adapter.
- Keep provider exceptions and rejected network calls away from the buyer UI.

## Verification checklist

- [ ] Events arrive in the intended test analytics project.
- [ ] The adapter prefixes or envelopes Preview names.
- [ ] Unknown event names are accepted.
- [ ] No personal or payment data is added.
- [ ] Analytics consent is respected.
- [ ] A deliberately throwing adapter does not break the picker.
- [ ] Booking conversion comes from server/order data, not this callback.

Continue with the [3D buyer view](/buyer-sdk/3d-view) or
[custom application architecture](/integrations/custom-applications).

Source: https://docs.seatlayer.io/buyer-sdk/analytics/index.mdx