Kissmetrics

Signal sends events to Kissmetrics server-to-server through the Kissmetrics tracking API: every event is a GET to trk.kissmetrics.io/e, and an identify call aliases the visitor’s anonymous ID to their user ID.

Prerequisites

The API key of your Kissmetrics product (Settings).

Configuration fields

Field	Required	Description
`api_key`	Yes	Sent as `_k`.

API endpoint

GET https://trk.kissmetrics.io/e?_k={api_key}&_p=crm-user-7&_n=Purchased&_t=1758500000&_d=1
      &Order+ID=T-1001&Order+Total=104.5&Purchased+SKU=SKU-1,+SKU-2&Currency=EUR

GET https://trk.kissmetrics.io/a?_k={api_key}&_p={anonymous ID}&_n=crm-user-7      (identify)

_p is the Signal user ID, or the anonymous ID before the visitor signs in; _t is the event time in epoch seconds with _d=1 so Kissmetrics records when it happened. Kissmetrics answers 200 even for incorrect parameters. Source: API specifications (updated 2026-01-29, read 2026-09-22).

Presets

Preset	Naming
Default	Page view, Signed up, Logged in, Product Search, Viewed Product, Add to Cart, Start Checkout, Purchased (Order ID, Order Total), Canceled Order (negative Order Total for a refund), Lead Generated
Retail	Kissmetrics E-Commerce Essentials names, with event-prefixed property names (Product Viewed - SKU, Product Added - Quantity …)
B2B / SaaS	Kissmetrics SaaS Essentials names (Requested demo, Trial started, Subscription started / billed / upgraded / downgraded / canceled, Used feature …)
Insurance	Insurance event-spec events with title-case property names

No personal data is sent. Kissmetrics stores e-mail addresses and names as raw person properties; adding them is your choice.

Default consent category: analytics.

Blueprint

Blueprint version 0.4.0 (not yet tested against a live Kissmetrics product).

Woopra Chartbeat