Getting Started

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

Core workflow

1. Sign in with an authorized internal account 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.

Attribution

Redirects pass a click identifier to the destination. The first-party SDK can retain that identifier for a 30-day last-touch window, then associate identified events with the eligible sublink.

The destination does not need accounts to report a customer. A form submit can be captured as a lead with linkquick.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

Internal agents use revocable organization API tokens. Create the smallest required permission scope, store the token as a secret, and revoke it when the workflow no longer needs access.

The stable Admin API is documented in Admin API. Its OpenAPI 3.1 contract is available at /api/v1/openapi.json and its agent guide at /api/v1/agent-skill.