Conversion tracking

Pair click and scan analytics with downstream conversion events. The platform supports an optional pixel endpoint, a server-side conversions API, and optional postback URLs configured per link where your build enables them.

Pixel endpoint

A transparent GIF route records a lightweight conversion signal tied to the link. Rate limits apply per IP. Disclose pixel usage in your privacy notices.

Conversions API

Report conversions server-side with POST /api/workspaces/{workspace}/conversions, referencing a link by short code or id. Each recorded conversion also fans out to webhook endpoints subscribed to conversion.recorded. See the API reference.

Destination attribution token

Redirects may append an encrypted reference to help your destination site correlate sessions. Treat it as opaque and validate integration in staging.

Postbacks

When configured, the platform may notify an HTTPS endpoint after click or scan persistence. Monitor queues and partner SLAs—delivery is best-effort and should not replace your source-of-truth order system.

Operational notes

High-volume pixels should be paired with edge caching policies and the same queue monitoring you use for scan ingestion. See Operations and Security & privacy.