Events

Prism tracks three kinds of events: the automatic PageView, declarative events via HTML attributes, and programmatic events via the JavaScript API.

Automatic: PageView

Fired once per page load, no configuration needed. Carries the URL, referrer, UTMs, and any ad click IDs.

Declarative: data-prism-event

Add an attribute to any form or clickable element — no JavaScript required.

Form submission (fires on submit):

<form data-prism-event="Lead">
  ...
</form>

Click (fires on click of the element or anything inside it):

<a href="/book" data-prism-event="AppointmentRequest">Book now</a>

<button data-prism-event="Purchase" data-prism-value="49.00">
  Buy — $49
</button>

data-prism-value (optional, clicks only) attaches a numeric value to the event — used as the conversion value when the event is delivered to Meta / Google Ads.

Programmatic: window.prism('track', ...)

For anything the attributes can't express — post-AJAX confirmations, SPA route changes, multi-step funnels:

window.prism('track', 'Lead');

window.prism('track', 'Purchase', {
  value: 129.0,
  currency: 'USD',
  order_id: 'A-1042',
});

The snippet queues calls made before it finishes initializing, so you can call prism('track', ...) at any time after the script tag.

Any properties you pass ride along with the event and are visible in Adsidian analytics. A few property names are special — they're treated as customer data, hashed in the browser, and never sent raw. See Customer data & privacy.

Naming events

• Use PascalCase names: Lead, Purchase, AppointmentRequest, SignUp.
• Be consistent — analytics, Meta event mapping, and Google conversion mapping are all keyed by exact event name.
• Lead-style events: the dashboard's built-in funnels treat Lead and AppointmentRequest as lead events.
• Meta restricted categories: for advertisers in special categories (health, housing, credit, …) Meta silently drops standard event names like Lead or Schedule. Your agency can remap your event names to Meta-safe custom names in the dashboard — you don't need to change your site.

What every event carries automatically

• adsidian_id — the 1-year server-issued identity
• Ad click IDs captured on any prior visit (fbclid, gclid, ttclid, LinkedIn, Snapchat) — held in 90-day first-party cookies
• UTM parameters (utm_source … utm_content)
• Page URL, referrer, user agent
• Meta's _fbp browser ID (created by Prism if no Meta pixel is present)