Attribution Model
Understand LinkQuick click identifiers, last-touch attribution, events, and revenue.
LinkQuick uses first-party, 30-day last-touch attribution.
To configure a destination application, create a tracking site under Organization → Attribution, then follow the Attribution and Events integration guide.
When the visitor lands on one domain and converts on another, see Multi-Domain Attribution.
Click, lead, sale
Attribution has three steps, in the order the visit happens.
Click. A visitor opens a sublink. LinkQuick records the click and passes its identifier to the destination, where the SDK retains it in first-party storage.
Lead. The first moment the destination learns who the visitor is. This is
the step that binds the stored click to a customer, so everything afterwards
inherits its attribution. An email from a form is enough — linkquick.lead(email)
keys the customer by that address when the application has no user ID yet. A
signed-in user ID is better; use identify for that.
Sale. Revenue for a customer that already has a lead. Sales come from your server, never the browser, and are keyed by the customer rather than the click.
A customer is identified by its external key alone. LinkQuick never merges two customers because they share an email, so pick one key per person — the email until an account exists, then your own user ID — and use it consistently.
Events and revenue
Destination applications can send named events, conversions, and revenue in minor currency units. Each request should include an idempotency key so retries remain safe.
If the click identifier is missing or expired, a valid user event may be kept as unattributed. LinkQuick does not fabricate attribution.
Reporting
Compare clicks, identified users, conversions, conversion rate, and revenue by sublink or parent. Imported historical aggregates remain separate from live daily attribution data.