Skip to content

Set Up Conversions

Availability: Conversion tracking is available on Professional and Agency plans. Changing workspace rules requires a workspace owner or administrator.

Open Conversions → Setup to configure conversion tracking. The page walks you through three steps:

  1. Enable conversions: Workspace rules.
  2. Install click capture: Browser capture.
  3. Send events: Direct API, Provider connectors, or both.

Diagnostics has Test an event and Event log.

Workspace rules

Each workspace has its own rules. Choose the workspace at the top of the section, change what you need, then Save changes. Only owners and administrators of an active workspace can edit them.

SettingWhat it does
Conversion trackingThe workspace’s master switch. Off for new workspaces. While it’s off, no link in the workspace can track conversions; your other settings are kept.
Link tracking policyManual per link (each link opts in), Default on (new links start with tracking on), or Required on all links.
Attribution modelWhen someone clicks more than one of your links before buying, which click gets the credit: Last touch (the most recent) or First touch. Applies when your site uses the capture script or the Shopify app.
Attribution windowHow long after a click a lead or sale can still be credited to it: 1 day, 7 days, 30 days, 60 days, 90 days (default), or a custom 1 to 90 days.
Enforce attribution settingsLinks must use the workspace’s model and window and can’t override them.
Commission record retentionHow long completed commission records are kept, up to your plan’s limit. Use plan default, or set a custom number of days. Open commissions are always kept.

The workspace rules also hold the commission rules for members and partners; see commissions and payouts.

With tracking on, turn on Track leads and sales in a link’s Advanced settings, unless the policy already does it for you. There you also choose who the link credits: the workspace, a member, a team, an external partner, a campaign, or a custom label.

Browser capture

Install click capture shows the capture script to add to your destination pages, so the click id survives until signup or checkout. See install the capture script.

Direct API

Code snippets for sending events from your backend, in cURL, Node, Go and Python. Switch between Test (validates requests without recording anything) and Live (records events). Create API key opens your API keys; the key needs conversions:write. See send conversion events.

Provider connectors

A connector records sales and refunds from a payment or commerce provider, with no code on your server. Choose Add connector, then the provider:

  • Stripe: payments, invoices, and refunds.
  • Dodo Payments: purchases and refunds.
  • Shopify: orders and refunds from a Shopify store.

Stripe and Dodo Payments

  1. Choose Add connector and the provider. Enter a Connector name, the Environment (Test / sandbox or Live, matching the provider’s mode), and the Workspace its sales are credited to. Choose Create connector.
  2. Copy the connector’s Webhook endpoint into the provider:
    • Stripe: open Workbench → Webhooks, select Create new destination, choose Events on your account, then Webhook as the destination.
    • Dodo Payments: open Developer → Webhooks and select Add endpoint.
  3. Subscribe the endpoint to these events:
    • Stripe: checkout.session.completed, checkout.session.async_payment_succeeded, invoice.paid, refund.created, refund.updated.
    • Dodo Payments: payment.succeeded, refund.succeeded.
  4. Copy the endpoint’s signing secret from the provider and paste it into Endpoint signing secret on the connector. For Stripe this is the whsec_… signing secret, not an API key; anything else is refused.
  5. Send a test event from the provider, or wait for a real one. The connector moves from Pending verification to Connected once a signed delivery arrives.

A Stripe or Dodo Payments connector belongs to its workspace for good. To send an account’s sales to another workspace, disconnect the connector, then connect the account again in that workspace. To make sure each payment carries the click id, see attribute hosted checkouts.

Shopify

Shopify stores connect through the shortn.link app, not a webhook secret:

  1. Install the shortn.link app on your Shopify store (Open in the Shopify App Store).
  2. Open the app in your Shopify admin and sign in to Shortn.
  3. Choose the workspaces the store may credit sales to.

The connector then appears in your list. Unlike Stripe and Dodo Payments, one store can serve several workspaces, and you can change which later. Ad blockers in a visitor’s browser can stop Shortn from seeing the click, so some of their orders can’t be attributed.

Manage a connector

Select a connector to rename it, change its workspaces (Shopify), replace its signing secret (Replace secret), or Disconnect it. Disconnecting removes its credentials, and its workspaces stop receiving new events from that provider. A connector shows Needs attention when deliveries are failing.

Test an event

Try a lead, sale or refund without recording anything:

  1. Choose the Event type.
  2. Paste an API key with conversions:write. It’s used only for this request and cleared afterward.
  3. Edit the Request JSON, using a real click id or invoice id you can access.
  4. Choose Validate event.

The response shows whether the event would be recorded, and why not if it wouldn’t. This uses the same validation endpoints as the API.

Event log

The Event log lists every conversion event that reached Shortn: provider webhooks, conversion API calls, and cart leads from the Shopify app, with what came of each. Filter it by source, status, provider, connector, environment, and API key, or search by request, delivery or conversion ID, click ID, event name, or connector. From a connector, use View this connector’s events in the Event log.

Provider webhooks show their processing status: Processed, Partially processed, Unmatched, Ignored, Retrying, or Automatic retries stopped. A payment without a click id shows as Ignored with “Provider sale has no Shortn click attribution”. Open a delivery to see its attempts and what it created.

To process a webhook again after fixing its cause (for example, assigning the connector to the right workspace), open it and choose Replay. Replay uses the original payload and the connector’s current workspaces, and never records the same conversion twice. It’s available while the original payload is still kept.

API calls show as Accepted, Duplicate, or Rejected, with the endpoint, HTTP status, and reason. They can’t be replayed: your server sends them again. API calls and Shopify cart leads are kept for 90 days, with the click stored only as a fingerprint.

Last updated on