Kliq
Guide/Getting Started

Getting Started

Understand the core Kliq workflow for domains, parent links, sublinks, and attribution.

Kliq keeps a destination canonical while giving every placement its own short URL and attribution context.

Core workflow

  1. Create an account, finish onboarding, and select your organization.
  2. Add or select a verified short-link domain.
  3. Create a parent link with its destination and social metadata.
  4. Create a sublink for a specific placement, including its slug, context, and UTM parameters.
  5. Copy the short URL and use it in the intended video, post, or automation.
  6. Compare clicks, identified users, conversions, and revenue across the parent's sublinks.
  7. Create a tracking site under Organization → Attribution and install its publishable browser configuration in the destination application.

Product surfaces, in the order you will actually use them:

  1. Create a Link — the New link dialog, slugs, UTM, and the link page.
  2. Parent Links and Sublinks — why destinations stay canonical.
  3. Tags — campaign and channel grouping.
  4. Analytics — the funnel tiles and breakdowns.
  5. Events — the raw click / lead / sale feed.
  6. Customers — who was identified and which link is credited.
  7. Attribution — first-touch, lf_id, leads, and sales.
  8. Multi-Domain Attribution — when the landing page and the app live on different hosts.
  9. Configure AI Agents — MCP, skills, and the 26-tool adapter.

Attribution

Redirects pass a click identifier to the destination. The first-party SDK can retain that identifier for a 30-day first-touch window, then associate identified events with the sublink that opened it — later Kliq links the visitor clicks inside that window do not take the credit.

The destination does not need accounts to report a customer. A form submit can be captured as a lead with kliq.lead(email), which keys the customer by that email; identify(user.id) takes over once the application has a user ID. Revenue is then reported from your server.

Events support an idempotency key so retrying the same request does not create a duplicate conversion or revenue record.

See Attribution and Events for the complete browser SDK, origin allowlist, verification, and trusted server conversion flow.

Agent access

Agents and internal tools use revocable organization API tokens. Create a key under Settings → API Keys, store it as a secret, and revoke it when the workflow no longer needs access.

Setup: Configure AI Agents. Tool catalog: Agent Tools. REST: Admin API. OpenAPI is at /api/v1/openapi.json; the live skill is at /api/v1/agent-skill.

Members APICreate a Link