Getting started

The RevRoute documentation covers the technical side of the platform: how to wire up tracking, how attribution works, and which interfaces are available to a developer. If you are looking for dashboard instructions instead, they live in the Help center.

What you can connect

• Short links — created by hand or programmatically, in bulk; see Introduction to short links.
• Click analytics — clicks broken down by device, location, referrer and UTM tags.
• Conversion tracking — lead and sale events tied back to the original click; see How attribution works.
• Partner programs — rewards and commissions for partners; setup is covered in the Help center.

Connection order

1. Connect your own domain for short links — see Choosing a custom domain.
2. Install the tracking script on your site: one tag in the <head> section. The script stores the attribution id in a first-party cookie.
3. Pick how conversions are sent. The recommended path is server-side tracking — events leave your backend and don’t depend on blockers. The alternative is client-side tracking.
4. Send your first events via the REST API: POST /track/lead on signup and POST /track/sale after a successful payment.
5. Subscribe to webhooks if you need to react to events on your side — see the webhooks overview.

Access keys

Server-to-server calls use a secret workspace key (rr_*) in the Authorization: Bearer header. Browser and mobile SDKs use a publishable key (rr_pk_*), which is safe to ship in client code. Both are generated in your workspace settings. If a call comes back 401 or 403, the API errors page maps every code to its fix.