Help

Troubleshooting

Troubleshoot partner tracking: fix links that don't credit, blocked cookies, conversions on the wrong programme and duplicate events.

Start with Tracking in your workspace: it shows whether the script has checked in and from which host, clicks and conversions for 30 days, and the latest events with their status and message. Integrations shows a log for each connection.

  • Link goes to "link unavailable": the partner isn't active, the programme is inactive or has no destination, or it's an Introductions programme (use /r/<code> instead).
  • No pp_ref in the address bar after a short link: your site may redirect and drop the query string. Keep query parameters on redirects, or install the script on the first page.
  • Script not installed: in the browser console, intrio.ref() should return the code after visiting a partner link. If intrio is undefined, the script isn't loading; check your Content Security Policy allows https://intrio.co.
  • domain_not_allowed: add the host shown in the error under Tracking › Allowed domains.
  • Status unattributed: the event had no ref or click_id, the code belongs to another workspace, the partner is paused, or the first touch (the click, or attributed_at) was older than the attribution window. Fix the cause and resend with the same id.
  • Customer already credited: attribution happens once per customer and programme. A second partner link for an existing customer doesn't move them.
  • Stripe payments not credited: the customer's metadata must have pp_ref before the invoice is paid, and either pp_programme or exactly one active link programme. One-off payments without an invoice aren't seen.

If the visitor declined cookies or a blocker stopped the script, carry the code in the visit instead: hidden form fields, ?via= on links into your app, and send it from your server. See cookies and consent.

Wrong programme#

  • The browser script defaults to the oldest active Sign-ups or Sales programme. Pass programme to intrio.track when you have more than one.
  • Stripe uses pp_programme from customer metadata, falling back to your only active link programme. With two or more, set pp_programme.
  • Shopify and WooCommerce orders go to the oldest active Sales programme.
  • The programme value is the slug, not the display name.

Duplicate events#

  • duplicate means the same id was already processed. Retries are safe and never double count.
  • rejected and unattributed events don't use up their id: fix the event and resend it with the same id.
  • Don't report the same payment from two sources with different ids (for example a browser sale and a server payment with your own invoice id), or it can be credited twice. The Shopify integration and the custom pixel share one id per order, so using both is safe.

Currency rejected#

Each workspace has one currency. Events in another currency are rejected; convert before sending, or leave currency out to record the amount in the workspace currency.

Last updated 20 November 2026. Building with an AI assistant? Point it at /docs/llms-full.txt.