# Intrio documentation (full text) > Intrio (https://intrio.co) runs partner, referral and affiliate programmes: partner links, a browser tracking script, a Conversions API, a Node SDK, webhooks and Stripe, Shopify and WooCommerce integrations. Amounts are integer minor units. --- # Get started: Intrio documentation URL: https://intrio.co/docs Last updated: 2026-11-20 How Intrio tracks partner referrals, works out rewards and pays partners, with guides and API reference for developers. Intrio runs partner, referral and affiliate programmes. Partners share a link, a code or an introduction. Intrio works out who sent each customer, records what that customer pays, calculates the partner's reward and pays it out once the money is in. - Quickstart: software (/docs/quickstart/software): Track sign-ups and subscription payments in about 10 minutes. - Quickstart: online shops (/docs/quickstart/shops): Connect Shopify or WooCommerce in one click. - Quickstart: services (/docs/quickstart/services): Referral pages, a pipeline and rewards on paid invoices. - Conversions API (/docs/api/conversions): Record sign-ups, payments, orders and refunds from your server. ## How attribution works Every credited sale follows the same path, whichever way you install Intrio: - 1. Partner shares: A short link (/go//), a ?via= link to any page, a referral page or a discount code. - 2. Visitor arrives: The tracking script stores the partner code and click id in a first-party pp_attr cookie for the attribution window. - 3. Customer converts: A sign-up or order is reported by the script, your server, Stripe, Shopify or WooCommerce, carrying the partner code. - 4. Payment recorded: Each payment is matched to the customer. Intrio prices it with the partner's tier and your rules. - 5. Reward unlocks: The reward is payable at once, or after your hold days. Refunds shrink or claw it back. - 6. Partner is paid: The partner requests a payout. You pay through your own Stripe (no Intrio fee; Stripe’s own fees apply) or by bank transfer. The partner is credited on the customer's first event. After that, Intrio recognises the customer by the customer.id you send, so payments don't need to carry the partner code again. ## Ways to install Method | Best for | Plans Tracking script (/docs/tracking-script) | Any website: stores the partner, reports leads and sales from the browser | All plans Stripe (/docs/integrations/stripe) | Subscriptions billed by Stripe: every paid invoice is credited automatically | All plans Shopify (/docs/integrations/shopify) and WooCommerce (/docs/integrations/woocommerce) | Online shops: orders, refunds and partner discount codes | All plans Conversions API (/docs/api/conversions) and @intrio/node (/docs/sdk/node) | Server-side reporting from any backend | Growth and above Webhooks (/docs/webhooks) | Reacting in your own systems when partners join, deals win or rewards change | Growth and above ## Key terms - Workspace: your business in Intrio, with its own partners, programmes, currency and settings. - Programme: what partners promote. Each has a type (Introductions, Sign-ups or Sales), an attribution window, hold days and an optional limit on rewarded payments. - Partner code: the partner's unique code, such as maya-7k3q. It appears in every link and is what you send as ref. - Referral: one referred customer or deal. It moves from open to won when the first payment lands. - Reward: the partner's share of one payment. Rewards move from building to payable to paid, or are voided. > Amounts are minor units: Every amount in the API, SDKs and webhooks is an integer in the smallest currency unit: 4900 is £49.00. --- # Get started: Quickstart for software URL: https://intrio.co/docs/quickstart/software Last updated: 2026-11-20 Track partner sign-ups and recurring subscription payments for a SaaS product in about 10 minutes, with the tracking script and Stripe Billing. By the end of this guide a partner link will lead to a tracked sign-up, and each subscription payment will create a reward. Allow about 10 minutes. ## 1. Create a workspace and programme 1. Sign up at intrio.co/signup (/signup) and choose SaaS and digital products. This switches on tracking links and recurring rewards, and seeds tiers from 20% to 30%. 2. Open Programmes and create a Sign-ups programme. Set the destination to your sign-up page, for example https://example.com/signup. 3. Note the programme's slug (shown on the programme, for example app). You'll send it as programme. 4. Set Reward the first N payments if commission should stop after, say, 12 payments. ## 2. Add the tracking script Copy your publishable key from Tracking, add your domain to the allowed domains there, then put this in the of every page: HTML: ```html ``` If your marketing site and app are on different subdomains, add data-domain="example.com" so the cookie is shared. See cross-subdomain attribution (/docs/links/cross-subdomain). ## 3. Report sign-ups Pick one. Both credit the partner on the sign-up. Browser: ```js // After your sign-up form succeeds intrio.track("lead", { customer: { id: user.id, email: user.email } }); ``` Node: ```ts import { Intrio } from "@intrio/node"; const intrio = new Intrio(process.env.INTRIO_API_KEY!); // In your sign-up handler. The script fills hidden pp_ref / pp_click inputs, // and the pp_attr cookie arrives with the request. const { ref, clickId } = Intrio.attributionFrom({ body: req.body, cookie: req.headers.cookie }); await intrio.trackLead({ id: `signup_${user.id}`, programme: "app", ref, clickId, customer: { id: user.id, email: user.email } }); ``` > The server route is more reliable: ad blockers can't stop it, and it works even if the visitor declined cookies but you carried the code in the form. The Node SDK and Conversions API need the Growth plan or above. ## 4. Report payments If you bill with Stripe, connect it under Integrations and tag the customer when you create them. Every paid invoice is then credited without more code: Node: ```ts await stripe.customers.create({ email: user.email, metadata: { pp_programme: "app", pp_ref: ref ?? "", pp_click: clickId ?? "" }, }); ``` Not on Stripe? Report each payment yourself (Growth and above): Node: ```ts await intrio.trackSale({ id: invoice.id, programme: "app", customer: { id: user.id }, amount: 4900, currency: "GBP" }); ``` ## 5. Test it 1. In Partners, invite yourself as a partner (use a different email) and copy the link from the partner portal. 2. Open the link in a private window. You should land on your sign-up page with ?pp_ref= and ?pp_click= in the address bar. 3. Sign up. Within seconds a referral appears under Referrals and the partner sees it in their portal. 4. Pay with a Stripe test card. The referral moves to won and a reward appears under Rewards. Nothing showing? Check troubleshooting (/docs/help/troubleshooting). --- # Get started: Quickstart for online shops URL: https://intrio.co/docs/quickstart/shops Last updated: 2026-11-20 Credit creators and affiliates for Shopify or WooCommerce orders with a one-click install, partner discount codes and a returns window. Shop integrations are available on every plan and need no code. ## Shopify 1. Create a workspace and choose E-commerce and consumer brands. 2. Open Integrations, choose Shopify and enter your store (acme or acme.myshopify.com). Approve the permissions in Shopify. 3. Intrio then sets everything up: an Online shop sales programme with a 30-day hold, your store domains as allowed tracking domains, the tracking script on your storefront, and webhooks for paid orders, refunds and uninstalls. 4. Invite creators. Each one gets a link and, from the Intrio app inside Shopify admin, can be given their own discount code. ## WooCommerce 1. Open Integrations, choose WooCommerce, enter your store address (https only) and approve the keys in WordPress. 2. Install the Intrio for WooCommerce plugin and paste your publishable key (from Tracking) into Settings › Intrio. The plugin adds the tracking script and saves the partner on each order. ## How an order is credited When an order is paid, Intrio looks for the partner in this order: the partner saved on the order (cart attribute or order meta), the landing page's pp_ref or via, then a discount code matching a partner's code. Refunds reduce or claw back the reward. See Shopify (/docs/integrations/shopify) and WooCommerce (/docs/integrations/woocommerce). ## Test it 1. Invite yourself as a creator and open your link in a private window. 2. Place a test order. It appears in Referrals as an order, with a reward that is held for 30 days (change hold days on the programme). 3. Check Integrations for the connection log: each order shows whether it was credited and how (link, click or discount code). --- # Get started: Quickstart for services and introducers URL: https://intrio.co/docs/quickstart/services Last updated: 2026-11-20 Run an introductions programme: referral pages, a deal pipeline and rewards that unlock as invoices are paid. For agencies, consultancies, recruiters and financial introducers. No code is needed. ## 1. Set up 1. Create a workspace and choose Services, agencies and consultancies (or Financial, FX and high-trust introducers, where rewards unlock when funds settle). 2. Check Tiers. New workspaces start with Starter 7.5%, Established 10% (3 wins), Preferred 12.5% (6 wins) and Strategic 15% (10 wins). Edit them freely. 3. Edit pipeline stages if you like. Defaults: Submitted, Qualified, Proposal, Won, Lost, Declined. The text partners see for each stage is editable too. ## 2. Invite partners Invite partners by email or share an invite link. Each partner gets a portal and a referral page at /r/. Anyone can fill in the form there and the partner is credited. Partners can also submit introductions from their portal, including the mobile quick-refer form. ## 3. Run the pipeline - Move each introduction through your stages. Partners see the stage and its text, so you don't have to send updates. - When you win, enter the contract value and an invoice plan: a single invoice, a deposit and completion split, or monthly instalments. - The partner's reward is worked out from their tier (or agreed rate) and your rules, and split across the invoices. ## 4. Rewards unlock when invoices are paid Each invoice's share of the reward becomes payable when you mark that invoice paid, or automatically when a linked Stripe invoice is paid. The partner then requests a payout and you pay via Stripe or bank transfer. See rewards (/docs/concepts/rewards) and payouts (/docs/concepts/payouts). --- # Concepts: Workspaces and business types URL: https://intrio.co/docs/concepts/workspaces Last updated: 2026-11-20 What an Intrio workspace holds, the five business types you can choose, and the modules each type switches on or hides by default. A workspace is one business. It has one currency, its own partners, programmes, tiers, rules, team and settings. Partner codes are unique across all of Intrio, so a code always identifies one partner in one workspace. ## Business types You choose a business type when creating a workspace. It decides which modules start switched on and what things are called. Every module can be toggled later in Settings › Modules without losing data. Type | Partners are called | Modules on by default | Rewards unlock when Services, agencies and consultancies | Introducers | Pipeline, quick-refer, stage invoices | An invoice or deposit is paid Financial, FX and high-trust introducers | Introducers | Pipeline, quick-refer, settlement tracking | The client's funds settle E-commerce and consumer brands | Creators | Links and SDK, discount codes, return-window holds | The order clears the returns window SaaS and digital products | Affiliates | Links and SDK, recurring billing | Each subscription payment is made Hybrid | Partners | Everything except settlement tracking | An invoice is paid ## Modules Module | What it does Deal pipeline | Referrals move through stages on a board or table. Quick-refer | A mobile, three-field referral form partners can use from WhatsApp. Stage invoices | Deposits and milestone invoices each unlock their share of a reward. Tracking links and SDK | Partner links, the browser script and click analytics. Discount codes | Vanity codes per partner, credited at checkout. Return-window holds | Hold rewards until the refund window has passed. Recurring billing | Reward subscription payments from Stripe for a set number of months. Settlement tracking | Rewards unlock when client funds settle, for financial introducers. ## Several businesses Agencies and groups can run several workspaces under one login on the Agency plan, with a portfolio dashboard across them. See the agency recipe (/docs/recipes/agency). --- # Concepts: Programmes URL: https://intrio.co/docs/concepts/programmes Last updated: 2026-11-20 Programme types, attribution windows, hold days and limits on rewarded payments: the settings that decide which conversions earn a reward. A programme is what partners promote. A workspace can run several, for example one for your app and one for your shop. The number you can create depends on your plan (Free 1, Starter 2, Growth 5, Scale and Agency unlimited). ## Types Type | How referrals arrive | Reported by Introductions | Partners submit a client or deal (portal, quick-refer or referral page) | You, in the pipeline. Not accepted by the Conversions API. Sign-ups | Visitors arrive via a partner link and sign up | Tracking script, Stripe, Conversions API Sales | Visitors arrive via a link or use a partner code and order | Shopify, WooCommerce, tracking script, Conversions API Sign-ups and Sales programmes are link programmes and need a destination URL (https). Partner short links send visitors there. ## Slug Each programme has a slug made from its name when it's created, for example app or online-shop. It's used in short links (/go//) and as programme in the API, SDKs and Stripe metadata. ## Settings - Attribution window (1 to 365 days): How long a visitor stays credited to a partner after clicking. Default 90. It sets the script's cookie lifetime only if you pass the same value as data-days; on the server it's enforced when the event carries a click_id. - Hold days (0 to 180 days): Rewards stay building for this many days after the payment, then become payable. Use it to cover your refund window. Default 0; shop programmes created by Shopify or WooCommerce start at 30. - Reward the first N payments (1 to 120, or empty): Only a customer's first N positive payments earn a reward. Later payments are recorded with status no_reward. Empty means every payment. - Active (on or off): Inactive programmes reject conversions and their short links go to a "link unavailable" page. > Terms are frozen at the first payment: When a referred customer's first payment is recorded, the partner's tier, any agreed rate and the matching rules are saved on that referral. Later edits to tiers or rules never change rewards for that customer. --- # Concepts: Programme page URL: https://intrio.co/docs/concepts/programme-page Last updated: 2026-11-20 Your public page for recruiting partners at /join/: templates, colours, fonts and images. GET https://intrio.co/join/{workspace} Every workspace has a public programme page where people read your terms and apply. The reward, referral window, unlock timing and payout methods are generated from your live programme settings, so the page always matches what partners are paid. Edit it under Programme page in your workspace; the preview updates as you type and has a mobile view. ## Templates Template | Best for | Plan Classic | Headline beside a terms card, details and calculator below. | All plans Minimal | Short and centred, with the application form on the same page. | All plans Spotlight | A full-width cover image with your terms as stat tiles. | Growth and above Creator | Affiliates and influencers: a big reward figure, perk cards, a testimonial and partner logos, plus a share button. | Growth and above Templates change the layout only. Every one shows the same generated terms, metadata and share card, and the apply and agreement pages take on the same header, colours and fonts. ## Customisation - Colours: an accent colour and a theme (Light, Dark or Brand tint, a soft background made from your accent). Contrast is checked automatically: button text is black or white, whichever reads better, and an accent that's too light or dark for text is adjusted for text only. The editor tells you when this happens. - Fonts: a heading font and a body font from a curated list (Inter, Inter Tight, DM Sans, Manrope, IBM Plex Sans, Space Grotesk, Fraunces and Instrument Serif for headings). Growth and above. - Buttons: rounded or square. - Images: your logo; a cover image for Spotlight and Creator (Growth and above; resized in the browser, with alt text required); and an optional share image (cropped to 1200 × 630) used instead of the generated card when the link is shared. - Social proof: an optional testimonial (quote, name, role) and up to 6 partner or brand logos. Only use quotes and logos you have permission to show. - Powered by Intrio: a small footer link. Growth and above can switch it off. > If your plan changes: Your choices are kept. If the plan no longer includes them, the page quietly falls back to Classic with the default fonts and no cover image until you upgrade again. If a payout is badly overdue, the page stops accepting applications whichever template you use. See payout assurance (/docs/concepts/payout-assurance). --- # Concepts: Partners and codes URL: https://intrio.co/docs/concepts/partners Last updated: 2026-11-20 How partners join your programme, what their partner code is, and where that code is used in links, discount codes and the conversions API. Partners join by email invite or an invite link, and always use Intrio free. Each partner has a portal showing their links, referrals, rewards, payouts and statements. ## Partner codes Every partner has a code made from their name and four random characters, for example maya-7k3q. Codes are lower case letters, numbers and dashes. The tracking script only accepts codes of 3 to 40 such characters. The code appears in every link the partner shares and is what you send as ref. On Shopify, the matching discount code is the same code in capitals without dashes (maya-7k3q becomes MAYA7K3Q); discount codes are matched ignoring case and punctuation. ## Status Only active partners are credited. Links of paused or removed partners stop working, and conversions carrying their code are recorded as unattributed. ## Agreed rates You can give a partner a custom rate. It replaces their tier rate as the base for every reward. Rules still apply on top. See tiers and rules (/docs/concepts/tiers-and-rules). --- # Concepts: Tiers and rules URL: https://intrio.co/docs/concepts/tiers-and-rules Last updated: 2026-11-20 How Intrio calculates every reward: commission tier rates, agreed partner rates, deal-size bands, overrides, one-off bonuses and caps. ## Tiers Partners move up tiers as they win more. A partner's tier is the highest whose threshold their number of won referrals has reached, and it's re-checked when a referral is won. Default tiers | Services and hybrid | SaaS Starter | 7.5% from 0 wins | 20% from 0 wins Established | 10% from 3 wins | 22.5% from 5 wins Preferred | 12.5% from 6 wins | 25% from 15 wins Strategic | 15% from 10 wins | 30% from 30 wins ## Rules Rules adjust rewards. Each rule has conditions and one effect. Conditions (all must match) - Minimum value (money): The payment or deal value is at least this. - Maximum value (money): The value is below this. - Category (category): Only deals in this category. - Tiers (list): Only partners in these tiers. - Programme (programme): Only referrals in this programme. - First N payments (number): Only a customer's first N payments. Effects - Set rate (rate): Replaces the base rate. - Fixed (amount): Replaces the rate with a flat amount. - Add rate (rate): Adds a bonus on top. Bonuses stack. - Cap (amount): Any rule can carry a cap that limits the total. ## Order of evaluation 1. Base: the partner's agreed rate if set, otherwise their tier rate. 2. The first matching set rate or fixed rule (lowest position) replaces the base. 3. Every matching add rate rule adds its rate on top. 4. The lowest cap among matching rules limits the total. Each reward stores a plain-English explanation, for example £490.00 at 20% (Starter tier) +5% Launch bonus, which partners see in their portal. > Tiered and volume commission bands need the Growth plan or above. --- # Concepts: Rewards lifecycle URL: https://intrio.co/docs/concepts/rewards Last updated: 2026-11-20 How a reward moves through building, payable, paid and voided, and how refunds, part payments and clawbacks change what a partner is owed. A reward is the partner's share of one payment, order or invoice. State | Meaning Building | Earned but not yet payable: waiting for hold days to pass, or for the client's invoice to be paid. Payable | Ready. The partner can request a payout. Paid | Included in a payout you've paid. Voided | Cancelled, for example by a full refund before payout. ## Hold days With hold days set on the programme, a reward is created as building with a release date of payment date plus hold days. Intrio releases due rewards automatically and tells the partner. ## Refunds and clawbacks - Before payout (building, or payable and not yet in a payout): the reward shrinks in proportion to the refund. A full refund voids it. - After payout: Intrio records a negative clawback reward that's deducted from the partner's next payout. - A refund is capped at the original payment, and also reduces the customer's recorded value. --- # Concepts: Payouts URL: https://intrio.co/docs/concepts/payouts Last updated: 2026-11-20 How partners are paid in Intrio: payout requests and approvals, Stripe transfers with no fee, bank transfers and numbered statements. 1. The partner requests a payout of all their payable rewards from their portal. 2. You pay it: through your own Stripe account, or by bank transfer and then mark it paid with your reference. 3. The rewards become paid, a numbered statement is issued and the partner is told. ## Stripe payouts Connect Stripe in Integrations. Partners onboard to a Stripe Express account on your platform; money moves from your Stripe balance straight to them. Intrio never holds funds and charges no fee on payouts. If a transfer fails, for example because your balance is too low, the payout is released with the reason so you can fix it and retry. If Stripe reverses a transfer, the payout fails and its rewards become payable again. Direct Stripe payouts are on Starter and above. On Free, pay by bank transfer and mark payouts paid. --- # Concepts: Payout assurance URL: https://intrio.co/docs/concepts/payout-assurance Last updated: 2026-11-20 How Intrio makes late partner payments visible: payout terms, overdue rewards, reminders, recruitment pauses and payment reports. > You pay your partners: Intrio never holds funds and never pays partners. Your business is solely responsible for paying the rewards shown as payable, within the terms you set. Payout assurance makes non-payment visible; it is not a guarantee of payment. ## Payout terms Each workspace states how many days it takes to pay a requested payout (30 by default), and optionally a minimum payout. Partners see these terms in their portal and agreement, phrased as your commitment: "Acme pays within 30 days of a payout being requested." ## When a reward is overdue Partners request payouts of their payable rewards. A requested payout that is still unpaid after your terms is overdue, and so is every reward in it. Partners see each reward's state in plain words: earned, waiting for the customer to pay, payable from a date, requested on a date, paid on a date, or overdue since a date. ## Reminders Once a day, owners and admins are emailed and notified in the app when payouts reach 7, 14, 30 days overdue. Each reminder is sent once. The overview, Payouts and Billing pages show a banner with the overdue amount and number of partners. The reward.overdue webhook fires at the same points. ## Recruitment pause If any payout is more than 60 days overdue, your public programme page and share links stop accepting new partners. Existing partners, links and tracking keep working, and nothing is lost. The pause lifts automatically once the overdue payouts are paid. ## Payment reports A partner can report a payment problem on an overdue reward or payout. It goes to your owners and admins first; reply or resolve it from Payouts. If there is no response within 14 days, the report is passed to Intrio staff, who may contact you and can pause recruitment for the programme. The payment_report.created webhook fires when a report is made. ## Statements Every partner statement lists each reward, the customer payment that unlocked it, the date it became payable and its status, so both sides share one record. --- # Concepts: Stablecoin payouts URL: https://intrio.co/docs/stablecoin-payouts Last updated: 2026-11-20 Pay partners in USDC on Base from your own wallet. Intrio prepares and verifies the transfers but never holds funds or keys. Available on Growth and above. Stablecoin payouts let partners choose to be paid in USDC, a dollar stablecoin issued by Circle, on the Base network. It suits partners abroad who would otherwise wait days and lose money to international bank fees. ## Non-custodial by design - Intrio never holds funds, keys or seed phrases, and never moves money. - Intrio never exchanges currency, never pays gas, runs no relayer and takes no fee from payouts. - You sign and send every transfer from your own wallet. Partners receive in their own wallet. - Intrio prepares the transfer data, verifies the result on chain and records it on the statement. ## For brands - Turn it on: In Payouts → Settings, turn on stablecoin payouts and connect the wallet you will pay from. Sign a free message to prove it is yours. Paying from a Safe? Enter the Safe address and sign with one of its owners. - Lock a rate: Rewards stay in your workspace currency. When you pay, Intrio shows a live rate from a public reference source (or enter your own). The rate is locked when you prepare the batch and stored with each payout. - Sign and send: Choose Pay N partners in USDC. Wallets that support batching (EIP-5792) confirm once; others confirm each transfer in turn. A Safe gets a Transaction Builder file to upload, sign and execute, then you paste the transaction hash. - Verified, then paid: Intrio reads each transaction on chain and checks the exact amount reached the partner's verified wallet from your wallet. Only then is the payout marked paid, the statement issued and the payout.sent webhook sent. Wrong amounts, recipients or senders are flagged and never marked paid. > Rounding: USDC has 6 decimal places. Converted amounts are always rounded down, so you never over-pay; the tiny remainder is shown before you sign. You need USDC and a small amount of ETH on Base in your wallet to cover network fees, which you pay directly. ## For partners - In Settings, choose USDC as your payout method, connect your wallet and sign a free message. This proves the wallet is yours. - Changing your wallet needs a new signature and a confirmation link sent to your email. Your old wallet stays active until you confirm. - Use a wallet that supports Base. Some exchange deposit addresses do not credit Base USDC. - Every paid statement shows the transaction hash with a link to Basescan. ## Supported wallets Wallet | How MetaMask, Rabby, Coinbase Wallet, Brave | Browser extension, detected automatically Mobile wallets | WalletConnect, where enabled Ledger and Trezor | Through MetaMask or Rabby, or Ledger Live via WalletConnect Safe multisig (brands) | Transaction Builder batch file, then paste the executed hash Smart contract wallets | Signatures verified with EIP-1271 ## Sanctions screening Partner wallet addresses and names are screened against sanctions lists when a wallet is connected and again before every batch. Flagged wallets are blocked and every result is logged. Connections from comprehensively sanctioned jurisdictions are blocked where practicable. Screening is an aid, not a guarantee: you remain responsible for your own sanctions compliance. ## Risks > Transfers are irreversible: A blockchain transfer cannot be reversed or recalled. Check recipients and amounts before signing. Intrio cannot recover funds sent to the wrong address or a wallet whose keys are lost. - USDC aims to hold a 1:1 value with the US dollar but is not a bank deposit and is not covered by deposit protection schemes. - Exchange-rate movements between the reward and the payout date affect what the partner receives in dollars. - Network congestion can delay confirmation. ## Tax Rewards are taxable income for partners in most countries whichever way they are paid, and disposing of USDC may have its own tax treatment. Partners are responsible for their own tax. Brands should take advice on how payouts in USDC are recorded in their accounts. ## Networks and contracts Network | USDC contract Base | 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 Base Sepolia (testnet) | 0x036CbD53842c5426634e7929541eC2318f3dCF7e --- # Concepts: Plan limits and locked items URL: https://intrio.co/docs/concepts/plans-and-limits Last updated: 2026-11-20 What each Intrio plan includes, how partners and tracked revenue are counted, and what happens when a workspace goes over a plan limit. | Free | Starter | Growth | Scale | Agency Active partners | 5 | 30 | 150 | Unlimited | Unlimited Tracked partner revenue a month | £2,500 | £15,000 | £75,000 | £250,000 | £500,000 Programmes | 1 | 2 | 5 | Unlimited | Unlimited Team seats | 1 | 3 | 10 | Unlimited | Unlimited Workspaces | 1 | 1 | 1 | 1 | 10 Direct Stripe payouts | | Yes | Yes | Yes | Yes Return-window holds | | Yes | Yes | Yes | Yes API, Node SDK and webhooks | | | Yes | Yes | Yes Tier bands, custom domain, white label | | | Yes | Yes | Yes New workspaces get a 14-day Growth trial. Current prices are on the pricing page (/pricing). ## Soft limits: nothing is lost Going over the partner or revenue limit never stops tracking. Partners can still join, and referrals and payments are still recorded and credited. The overflow is locked from view until you upgrade, and upgrading unlocks it instantly. - Partners: active partners beyond the limit, newest first, are locked. Paused partners don't count. - Revenue: positive payments are totalled per calendar month. A referral whose first payment lands after that month's total has reached the limit is locked. - A locked partner's referrals are locked too. ## Features after a downgrade API keys created on Growth or above keep working after a downgrade, so no tracking is lost. New keys can only be created on Growth and above. --- # Partner links: Direct ?via= links URL: https://intrio.co/docs/links/direct Last updated: 2026-11-20 Let partners link to any page of your site with ?via=, so every visit is credited to them without short links or extra set-up. With the tracking script (/docs/tracking-script) on your site, a partner can link to any page by adding ?via=: URL: ```text https://example.com/pricing?via=maya-7k3q ``` The script reads via (or pp_ref) and stores it in the pp_attr cookie. These links look tidy and keep your domain in the address bar, which helps partners in social posts. > Direct links don't count clicks: A ?via= link goes straight to your site, so Intrio doesn't see a click and there's no click id. The partner is still credited, but click analytics don't apply. The attribution window still does: the tracking script sends the cookie's first-touch time as attributed_at. Use short links (/docs/links/short-links) when you want both. Partners find their direct link in the portal under Links. --- # Partner links: Short links and ?to= URL: https://intrio.co/docs/links/short-links Last updated: 2026-11-20 Partner short links explained: how clicks are counted, deep linking to any page with ?to=, and how bots and link previews are filtered out. GET https://intrio.co/go/{partner-code}/{programme-slug} A short link records a click and redirects (302) to the programme's destination with two parameters added, keeping any query string the destination already has: Redirect: ```text https://example.com/signup?pp_ref=maya-7k3q&pp_click=Xb2k9QwLmN4pR7sT1vYz0a ``` - pp_ref (string): The partner code. - pp_click (string): A unique click id (22 characters). Send it as click_id to apply the attribution window on the server. ## Deep links with ?to= Add ?to= to send the visitor to another page on the same site: URL: ```text https://intrio.co/go/maya-7k3q/app?to=/pricing ``` to can be a path or a full URL. It must be http or https on the destination's host or one of its subdomains (www. is ignored). Anything else falls back to the destination, so short links can't be used as open redirects. ## Click counting and bots - Requests whose user agent looks like a bot, crawler or link preview (Slack, WhatsApp, Telegram, Discord, curl and so on) are recorded as bot clicks with no click id. They still redirect. - Each visitor counts for at most 20 clicks per partner per hour. Extra clicks still redirect but aren't recorded and get no click id. - Visitors are de-duplicated with a hash of their IP address that is salted daily. IP addresses are never stored. ## When a link doesn't work Unknown codes, paused partners, inactive or Introductions programmes, programmes with no destination and suspended workspaces all redirect to a "link unavailable" page. --- # Partner links: Referral page URL: https://intrio.co/docs/links/referral-page Last updated: 2026-11-20 The hosted /r/ referral page each partner can share: what it shows, how it credits the partner and how to brand it for your programme. GET https://intrio.co/r/{partner-code} Every partner has a hosted referral page headed " recommended ". - If the workspace has active link programmes, the page shows a button per programme (each goes through the partner's short link) and an optional contact form. - Otherwise it shows the contact form. Submissions arrive in your pipeline as introductions credited to the partner. The page is not indexed by search engines. --- # Partner links: Cross-subdomain attribution URL: https://intrio.co/docs/links/cross-subdomain Last updated: 2026-11-20 Keep partner attribution when visitors move from your marketing site to your app on another subdomain, with a shared first-party cookie. By default the pp_attr cookie belongs to the exact host that set it. If partners link to example.com but people sign up on app.example.com, add data-domain on both sites: HTML: ```html ``` - The cookie is then set with Domain=example.com and is readable on every subdomain. - The value must be a registrable domain that the current page is on. If the page's host isn't example.com or a subdomain of it, the setting is ignored and a host-only cookie is used. - A leading dot is allowed and removed. - Add both hosts (or just example.com, which covers subdomains) to the allowed domains under Tracking. > Carry the code as well: Cookies can be blocked or declined. Adding ?via= to links from your marketing site into your app means the app still knows the partner. The separate marketing site recipe (/docs/recipes/marketing-site-and-app) shows this. --- # Partner links: Cookies and consent URL: https://intrio.co/docs/links/cookies-and-consent Last updated: 2026-11-20 What Intrio stores in the browser, how long the attribution cookie lasts, and how to handle UK GDPR and PECR consent on your site. ## What the script stores Name | Type | Contents | Lifetime pp_attr | First-party cookie | { ref, click, at }: partner code, click id, time | data-days, default 90 days intrio_seen | sessionStorage | 1 once the install check-in is sent | The browser tab intrio_cart | sessionStorage (Shopify only) | The partner code last copied to the cart | The browser tab There are no third-party cookies and no fingerprinting. The cookie is only set when the visitor arrives with a partner code. ## Do you need consent? Under PECR, storing information on a device needs consent unless it is strictly necessary for a service the user asked for. Affiliate tracking cookies are not usually treated as strictly necessary, so the cautious approach in the UK and EU is to load the script only after the visitor accepts the relevant cookie category. This is guidance, not legal advice; check with your own adviser. JavaScript: ```js function loadIntrio() { if (document.getElementById("intrio-sdk")) return; const s = document.createElement("script"); s.id = "intrio-sdk"; s.async = true; s.src = "https://intrio.co/sdk.js"; s.setAttribute("data-key", "pk_…"); document.head.appendChild(s); } // Call loadIntrio() from your consent banner's "accept" handler, // and on page load if consent was given earlier. ``` ## Attribution without cookies If the visitor declines, you can still credit the partner by carrying the code through the visit instead of storing it on the device for later: - Read via or pp_ref from the landing URL and keep it for the current tab (in memory or sessionStorage). - Add it to your sign-up form as a hidden field, or to links into your app as ?via=. - Send it as ref from your server with the Conversions API (/docs/api/conversions), or save it on the customer in Stripe metadata. This credits partners whose visitors convert in the same visit. Visitors who come back days later without the cookie can't be matched. --- # Tracking script: Tracking script reference URL: https://intrio.co/docs/tracking-script Last updated: 2026-11-20 Reference for sdk.js: attributes, URL parameters, the pp_attr cookie, intrio.track and every response. Available on every plan. HTML: ```html ``` The second line is a stub that queues intrio.track calls made before the script loads. Queued calls are sent once it loads (their return values are discarded). ## Attributes - data-key (string): Your publishable key (pk_…) from Tracking. Safe to expose. Needed for intrio.track and the install check-in; without it the script still stores the partner and fills forms. You can pass ?key=pk_… on the script URL instead. - data-days (integer): Cookie lifetime in days. Default 90. Set it to your programme's attribution window. - data-domain (string): Share the cookie across subdomains, for example example.com. See cross-subdomain attribution (/docs/links/cross-subdomain). ## URL parameters read - pp_ref (string): Partner code, added by short links. - via (string): Partner code, for direct links. pp_ref wins if both are present. - pp_click (string): Click id, added by short links. The code must be 3 to 40 letters, numbers or dashes; it's stored in lower case. A new partner link overwrites the cookie, so the last partner link wins. ## The pp_attr cookie URL-encoded JSON, Path=/, SameSite=Lax, Secure on https, with Max-Age from data-days: JSON: ```json { "ref": "maya-7k3q", "click": "Xb2k9QwLmN4pR7sT1vYz0a", "at": 1763640000000 } ``` ## Form fields When the page has loaded, the script fills any and with the stored values, so a plain form posts them to your server: HTML: ```html
``` Fields are filled at DOMContentLoaded, again whenever new inputs appear (forms rendered later by React or another framework), and on focus and submit. Add to also send the first-touch time for the attribution window. ## JavaScript API - intrio.ref() (string | null): The stored partner code. - intrio.clickId() (string | null): The stored click id. - intrio.attributedAt() (string | null): When the visitor first followed the partner link (ISO 8601). - intrio.clientReferenceId() (string | null): ref:click (or just ref). Pass it as Stripe Checkout's client_reference_id and Intrio credits the payment. - intrio.track(event, data) (Promise): Report a lead or sale. See below. window.partnerRef is the same object, kept for older installs. ## intrio.track JavaScript: ```js // Lead: needs customer.email or customer.id intrio.track("lead", { customer: { email: "sam@acme.com", name: "Sam Lee" } }); // Sale: needs id and amount (minor units) intrio.track("sale", { id: "ORDER-1001", amount: 4900, currency: "GBP", customer: { email: "sam@acme.com" }, }); ``` data - id (string): Your order or event id. Required for sale. Converted to a string. - amount (integer): Minor units. Required for sale. - currency (string): ISO code. Must match the workspace currency if given. - programme (string): Programme slug. Defaults to the workspace's oldest active Sign-ups or Sales programme. - customer (object): id, email and name. For leads, id or email identifies the customer. - If the visitor has no stored partner, track resolves to { status: "unattributed" } without a network request. Only partner-referred visitors are ever sent. - A lead is recorded as a signup with id web:lead: (or the customer id or email when no id is given). A sale is recorded with id web:sale:, as a payment on Sign-ups programmes and an order on Sales programmes. With Shopify connected, a Shopify order id (numeric or gid://shopify/Order/…) is recorded as shopify:order:, the same id the Shopify app uses, so the order is credited once. The cookie's first-touch time is sent as attributed_at. Repeats of the same id are duplicates, so calling twice is safe. - Requests go to POST https://intrio.co/api/v1/track as text/plain, so there's no CORS preflight. ## Responses On success, track resolves to the same result as the Conversions API (/docs/api/conversions#statuses): { status, message, referralId }. Otherwise it resolves (never rejects) with an error: error | HTTP | Cause missing_key | | No data-key on the script. network | | The request failed. invalid_json, invalid_request | 400, 422 | Malformed body or fields. invalid_key | 401 | Unknown publishable key. suspended | 403 | The workspace is suspended. unknown_origin | 400 | No Origin header or page URL. domain_not_allowed | 403 | The page's host isn't in your allowed domains (subdomains of a listed domain are allowed). rate_limited | 429 | More than 60 requests a minute from one IP address. no_programme | 422 | No programme given and no active link programme. customer_required | 422 | A lead without customer.email or customer.id. id_and_amount_required | 422 | A sale without id or amount. paused | 503 | Browser tracking is temporarily paused platform-wide. ## Install check Once per browser session the script sends a check-in so Tracking can show it's installed and on which host. The check-in doesn't need the domain to be allowed. ## Shopify On Shopify storefronts the script also copies pp_ref and pp_click onto the cart as attributes, so they travel with the order. The Shopify integration installs the script for you. ## Security The publishable key can only report leads and sales for partner-referred visitors from your allowed domains. Rewards on sales reported from the browser can be faked by a determined visitor, so set hold days on the programme, or report sales from your server or a platform integration instead. --- # Server-side: Authentication and API keys URL: https://intrio.co/docs/api/authentication Last updated: 2026-11-20 Create secret API keys, keep them safe, and authenticate Conversions API and Node SDK requests from your own server with a bearer token. Available on Growth and above. On Free and Starter, use the tracking script (/docs/tracking-script), Stripe (/docs/integrations/stripe), Shopify (/docs/integrations/shopify) or WooCommerce (/docs/integrations/woocommerce), which work on every plan. Keys created on Growth keep working after a downgrade. Create a key under Programmes › API keys. The key is shown once; Intrio stores only a hash. Name keys after where they're used so you can revoke one without affecting others. The list shows when each key was last used. Header: ```text Authorization: Bearer pp_live__ ``` - Keys start pp_live_. There are no separate test keys; see testing (/docs/api/conversions#testing). - A key belongs to one workspace. Its events are recorded in that workspace's currency. - Revoked keys and keys of suspended workspaces get 401 invalid_api_key. - Keep keys on your server. The publishable key (pk_…) is the one for browsers. --- # Server-side: Conversions API URL: https://intrio.co/docs/api/conversions Last updated: 2026-11-20 POST /api/v1/conversions: record sign-ups, payments, orders and refunds from your server. Every field, status and error. Available on Growth and above. On Free and Starter, use the tracking script (/docs/tracking-script), Stripe (/docs/integrations/stripe), Shopify (/docs/integrations/shopify) or WooCommerce (/docs/integrations/woocommerce), which work on every plan. Keys created on Growth keep working after a downgrade. POST https://intrio.co/api/v1/conversions Record one sign-up, payment, order or refund. cURL: ```bash curl https://intrio.co/api/v1/conversions \ -H "Authorization: Bearer $INTRIO_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "id": "in_1QxY2z", "type": "payment", "programme": "app", "customer": { "id": "user_42", "email": "sam@acme.com" }, "amount": 4900, "currency": "GBP" }' ``` Node: ```ts import { Intrio } from "@intrio/node"; const intrio = new Intrio(process.env.INTRIO_API_KEY!); const result = await intrio.trackSale({ id: "in_1QxY2z", programme: "app", customer: { id: "user_42", email: "sam@acme.com" }, amount: 4900, currency: "GBP", }); ``` Python: ```python import os, requests res = requests.post( "https://intrio.co/api/v1/conversions", headers={"Authorization": f"Bearer {os.environ['INTRIO_API_KEY']}"}, json={ "id": "in_1QxY2z", "type": "payment", "programme": "app", "customer": {"id": "user_42", "email": "sam@acme.com"}, "amount": 4900, "currency": "GBP", }, timeout=10, ) print(res.status_code, res.json()) ``` PHP: ```php true, CURLOPT_RETURNTRANSFER => true, CURLOPT_HTTPHEADER => [ "Authorization: Bearer " . getenv("INTRIO_API_KEY"), "Content-Type: application/json", ], CURLOPT_POSTFIELDS => json_encode([ "id" => "in_1QxY2z", "type" => "payment", "programme" => "app", "customer" => ["id" => "user_42", "email" => "sam@acme.com"], "amount" => 4900, "currency" => "GBP", ]), ]); $body = json_decode(curl_exec($ch), true); $status = curl_getinfo($ch, CURLINFO_HTTP_CODE); ``` ## Body - id (string, required): Your unique id for this event, 1 to 200 characters. Use the invoice, order, charge or user id. See idempotency (#idempotency). - type (string, required): signup, payment, order or refund. - programme (string, required): The programme slug, up to 60 characters. Must be an active Sign-ups or Sales programme. - ref (string): The partner code (pp_ref / via), up to 60 characters. - click_id (string): The click id (pp_click), up to 80 characters. Applies the attribution window. - customer.id (string): Your stable id for the customer, 1 to 200 characters. Required for signup and payment. For an order without it, Intrio uses order:. - customer.email (string): Valid email, up to 254 characters. Shown to you and used as the referral's label. - customer.name (string): Up to 120 characters. - amount (integer): Minor units, 0 to 1,000,000,000. Required for payment and order. For refund, the amount refunded (defaults to the full original amount). - currency (string): 3-letter code. If given, it must match the workspace currency (any case). - refunds (string): For refund: the id of the payment or order being refunded. Required for refunds. - attributed_at (string): ISO 8601 date-time: when the visitor first followed the partner link (the pp_attr cookie's at). Optional. Applies the attribution window when there's no click_id; without either, the event is accepted. - occurred_at (string): ISO 8601 date-time with offset, for example 2026-11-20T09:30:00Z. Defaults to now. Used for the attribution window, hold days and the referral date. ## How each type is handled - signup (type): Credits the partner for the customer. Creates the referral if it's new. - payment (type): A recurring or one-off payment. Credits the partner (if the customer is new and the event carries a ref or click_id), moves the referral to won on the first payment, and creates a reward. - order (type): Like payment, for shop orders. customer is optional. - refund (type): Reduces or claws back the reward on the payment named in refunds. Attribution happens once per customer and programme. When the first event for a customer.id carries a valid ref or click_id, a referral is created for that partner. Later payments for the same customer.id are credited to that partner without needing ref. If the first event has no partner, it's recorded as unattributed and nothing is created. When both ref and click_id are given and the click belongs to this programme, the click's partner is used. A click_id, or for ref-only events an attributed_at, older than the programme's attribution window gives unattributed. ## Responses 201: Recorded, or accepted with no credit (unattributed, no_reward). ```json { "status": "recorded", "message": "Payment 1 recorded: reward £980.00", "referral_id": "cmi8x2k0w0001qk08z9f3h1a2" } ``` 200: Duplicate: this id was already processed. ```json { "status": "duplicate", "message": "Event in_1QxY2z was already processed (recorded)", "referral_id": "cmi8x2k0w0001qk08z9f3h1a2" } ``` 422: Rejected by business rules, or invalid fields. ```json { "status": "rejected", "message": "No active programme \"ap\"", "referral_id": null } { "error": "invalid_request", "message": "Check the fields", "fields": { "amount": ["amount must be integer minor units"] } } ``` 401: Missing or invalid key. ```json { "error": "invalid_api_key", "message": "Missing or invalid API key" } ``` 400: Body isn't JSON. ```json { "error": "invalid_json", "message": "Body must be JSON" } ``` 429: Rate limited. ```json { "error": "rate_limited", "message": "Too many requests; slow down and retry" } ``` 500: Server error. Nothing was saved; retry with the same id. ```json { "error": "internal", "message": "Couldn't record that conversion. It's safe to retry with the same id." } ``` ## Statuses status | HTTP | Meaning recorded | 201 | Saved. For payments and orders, a reward was created (it may be £0 if your rules give nothing). unattributed | 201 | No valid partner: no ref or click_id, an unknown code, an inactive partner, or a first touch outside the attribution window. no_reward | 201 | Saved, but no reward: the payment is beyond the programme's rewarded payments, or a refund had nothing to reverse. duplicate | 200 | This id was already processed. The original outcome is in message. rejected | 422 | Not accepted. message says why (see below). ### Rejection messages - No active programme "" - Introductions programmes take referrals from partners, not the conversions API - Currency doesn't match the workspace currency - customer.id is required for sign-ups and payments - amount is required for payments and orders - refunds must be the id of the payment or order being refunded - No recorded payment "" ## Idempotency Every event is processed once per id, whatever the retries. Each request runs in a single transaction, so after a 500 or a timeout nothing was saved and you can safely retry with the same id. > Fix and resend with the same id: Only recorded and no_reward use up an id. A rejected or unattributed event changed nothing, so once you fix it (for example a wrong programme slug, or a sign-up that now has its ref) send it again with the same id. A customer is still credited to one partner only, and a payment is never counted twice. Use ids that are unique per event within your workspace: prefix them if two systems report to the same workspace, for example signup_ and . ## Rate limits 1,200 requests per minute per workspace, counted in fixed one-minute windows. Over the limit you get 429; wait and retry with the same id. The Node SDK (/docs/sdk/node) retries 429s and 5xx for you. ## Testing There's no separate test mode. To test safely: - Create a separate test programme (for example slug app-test) and switch it off when you're done; events for an inactive programme are rejected. - Invite yourself as a partner and use your own code as ref. - Use clearly fake ids such as test_001. - Events without a ref or click_id for a new customer create nothing, so you can check authentication and validation without side effects. --- # Server-side: @intrio/node URL: https://intrio.co/docs/sdk/node Last updated: 2026-11-20 Reference for the @intrio/node server SDK: trackLead, trackSale, trackRefund, attributionFrom, retries and errors. Available on Growth and above. On Free and Starter, use the tracking script (/docs/tracking-script), Stripe (/docs/integrations/stripe), Shopify (/docs/integrations/shopify) or WooCommerce (/docs/integrations/woocommerce), which work on every plan. Keys created on Growth keep working after a downgrade. npm: ```bash npm install @intrio/node ``` pnpm: ```bash pnpm add @intrio/node ``` Node 18 or later (it uses the built-in fetch). ES modules only. The SDK is a thin wrapper over the Conversions API (/docs/api/conversions). ## new Intrio(apiKey, options) TypeScript: ```ts import { Intrio } from "@intrio/node"; const intrio = new Intrio(process.env.INTRIO_API_KEY!, { retries: 2 }); ``` - apiKey (string, required): A secret key starting pp_live_. Passing anything else throws immediately. - options.baseUrl (string): Default https://intrio.co. - options.fetch (typeof fetch): Custom fetch, for tests or proxies. - options.retries (number): Retries after the first attempt for network errors, 429 and 5xx. Default 2, waiting 300 ms then 600 ms (doubling); there's no wait after the last attempt. ## trackLead(input) Sends a signup. - id (string, required): Unique event id, for example signup_. - programme (string, required): Programme slug. - customer ({ id, email?, name? }, required): Your customer. - ref (string | null): Partner code. - clickId (string | null): Click id. - attributedAt (Date | string | null): First-touch time; attributionFrom fills it from the cookie. Applies the attribution window without a click id. - occurredAt (Date): Defaults to now. ## trackSale(input) Sends a payment (default) or an order. - id (string, required): Unique id, for example the invoice id. - programme (string, required): Programme slug. - amount (number, required): Integer minor units. - customer ({ id, email?, name? }): Required for payments. - currency (string): Must match the workspace currency. - kind ("payment" | "order"): Default payment. - ref, clickId, attributedAt, occurredAt (): As for trackLead. ## trackRefund(input) - id (string, required): Unique id for the refund. - programme (string, required): Programme slug. - refunds (string, required): The id of the payment or order being refunded. - amount (number): Refunded amount. Defaults to the full payment. - currency, occurredAt (): As above. ## Intrio.attributionFrom(source) Reads the partner from a form body (pp_ref, pp_click, pp_at) or, failing that, from a Cookie header containing pp_attr. Returns { ref, clickId, attributedAt }, or {} when there's nothing. TypeScript: ```ts const { ref, clickId, attributedAt } = Intrio.attributionFrom({ body: req.body, cookie: req.headers.cookie }); ``` ## Results and errors Every method resolves to { status, message, referralId? } for recorded, unattributed, no_reward and duplicate. It throws IntrioError for other 4xx responses, and the last error once retries run out. TypeScript: ```ts import { Intrio, IntrioError } from "@intrio/node"; try { await intrio.trackSale({ id: invoice.id, programme: "app", customer: { id: user.id }, amount: 4900 }); } catch (e) { if (e instanceof IntrioError) { console.warn(e.status, e.code, e.message, e.fields); } else { throw e; // network failure after retries } } ``` IntrioError - status (number): HTTP status. - code (string): The response's error field, such as invalid_api_key or invalid_request. For a rejected event it's rejected (the result's status); read message. - message (string): Human-readable reason. - fields (Record): Per-field validation errors for invalid_request. > Never let reporting block your sign-up or billing flow. Call the SDK after your own work succeeds, catch errors and log them, or push the call onto a background job. --- # Integrations: Stripe URL: https://intrio.co/docs/integrations/stripe Last updated: 2026-11-20 Credit partners for every paid Stripe invoice using customer metadata, handle refunds and pay partners through Stripe. Payment tracking is available on every plan. Direct Stripe payouts are on Starter and above. Connect Stripe under Integrations. We recommend a restricted key (rk_live_…) with only the permissions below; a secret key also works. Partner payouts also need Stripe Connect switched on in your account (Stripe dashboard > Connect > Get started): if it isn't, Intrio still connects and shows a reminder on Integrations and Payouts until it is. Intrio listens for invoice.paid, checkout.session.completed, checkout.session.async_payment_succeeded, charge.refunded, charge.refund.updated and transfer.reversed on your account, and account.updated for partners' connected accounts. Every event is signature-checked and processed once. ## Restricted key permissions In Stripe, go to Developers > API keys > Create restricted key and set these. Everything else can stay at None. Permissions - Accounts (Connect) (Write): Check Connect is on, create each partner's Express account and read its payout status - Account Links (Connect) (Write): Send partners to Stripe's hosted onboarding - Transfers (Connect) (Write): Pay approved rewards from your balance to partners - Customers (Write): Read customers on sales, and tag them with the referring partner so renewals stay attributed - Charges (Read): Match refunds to the original sale - Refunds (Read): Reverse rewards for refunded sales - Invoices (Read): Link payments to invoices so subscription renewals credit the right partner - Webhook Endpoints (Write): Create the webhooks that tell Intrio about sales, refunds and partner accounts ## Tag the customer Put the partner on the Stripe customer when you create it. Every paid invoice for that customer is then credited automatically. Customer metadata - pp_ref (string): Partner code. intrio_ref or via are also read, in that order. - pp_programme (string): Programme slug. Optional if the workspace has exactly one active Sign-ups or Sales programme. - pp_click (string): Click id, optional. Applies the attribution window. Node: ```ts const customer = await stripe.customers.create({ email: user.email, metadata: { pp_programme: "app", pp_ref: ref ?? "", pp_click: clickId ?? "" }, }); ``` Python: ```python customer = stripe.Customer.create( email=user.email, metadata={"pp_programme": "app", "pp_ref": ref or "", "pp_click": click_id or ""}, ) ``` PHP: ```php $customer = $stripe->customers->create([ 'email' => $user->email, 'metadata' => ['pp_programme' => 'app', 'pp_ref' => $ref ?? '', 'pp_click' => $clickId ?? ''], ]); ``` Using Stripe Checkout? Pass client_reference_id: intrio.clientReferenceId() (or pp_ref / pp_click / pp_programme in the session's metadata). On checkout.session.completed Intrio writes the partner onto the session's customer when it isn't tagged yet, so every later invoice is credited. Tag existing customers with stripe.customers.update. ## What happens on invoice.paid - Invoices with amount_paid of 0 are ignored. - The invoice is recorded as a payment with the invoice id as its id, the customer id as customer.id, and the paid date as occurred_at. - The first paid invoice credits the partner and wins the referral; each later invoice earns a reward until the programme's rewarded payments run out. - Customers with no partner in metadata are ignored, unless they were already credited. ## What happens on checkout.session.completed - Paid sessions (payment_status paid) in payment or subscription mode with a partner are recorded as a payment of amount_total. Unpaid and free sessions are ignored; delayed methods are credited on checkout.session.async_payment_succeeded. - The id is the session's invoice when it has one (subscriptions, or invoice creation), so invoice.paid for that invoice is a duplicate whichever arrives first. Otherwise it's the PaymentIntent id. - client_reference_id must be exactly intrio.clientReferenceId() (ref or ref:click); any other value is ignored. > Connected before 20 November 2026?: Reconnect Stripe under Integrations so the webhook endpoint subscribes to the Checkout and refund events. Manually created endpoints need them added in Stripe. ## Refunds On charge.refunded for a credited payment (an invoice or a Checkout payment), each succeeded Stripe refund is recorded once under its own refund id and amount, and the reward is reduced, voided or clawed back as described in rewards (/docs/concepts/rewards). Several partial refunds reverse exactly what was refunded. Pending refunds count when charge.refund.updated reports them succeeded. ## Introductions billed in Stripe For Introductions programmes, link a Stripe invoice id to a won referral's invoice line. When Stripe reports it paid, the line is marked paid and its reward unlocks. ## Payouts See payouts (/docs/concepts/payouts). --- # Integrations: Shopify URL: https://intrio.co/docs/integrations/shopify Last updated: 2026-11-20 Install the Intrio Shopify app in one click: paid orders, refunds, creator discount codes and storefront tracking set up without code. Available on every plan. Connect from Integrations in Intrio. The install asks for these permissions: read orders, read customers, read and write discounts, and write script tags. It then sets up, without further steps: - An Online shop Sales programme (slug shop) with a 30-day hold, if you don't have a Sales programme yet. - Your store's domains as allowed tracking domains, and a publishable key. - The tracking script on your storefront (via a script tag). - Webhooks for orders/paid, refunds/create and app/uninstalled. ## How orders are credited Paid orders are credited to the oldest active Sales programme. The partner is found in this order: 1. The order's pp_ref / pp_click note attributes, which the script copies to the cart. 2. pp_ref or via in the order's landing page URL. 3. A discount code matching an active partner's code, ignoring case and punctuation. Orders are recorded with id shopify:order: and the Shopify customer as the customer, so repeat orders from the same customer stay with the first partner. ## Creator discount codes From the Intrio app inside Shopify admin you can invite creators and create a creator's own discount code with a percentage off. The code is their partner code in capitals without dashes, so amelia-10 becomes AMELIA10. ## Refunds Successful refund transactions reduce or claw back the order's reward. ## Uninstalling Removing the app disconnects the store and discards its token. History in Intrio is kept. --- # Integrations: WooCommerce URL: https://intrio.co/docs/integrations/woocommerce Last updated: 2026-11-20 Connect WooCommerce in one click: order webhooks, refunds, partner coupon codes, and the optional Intrio for WooCommerce plugin for link tracking. Available on every plan. ## Connect 1. In Integrations, choose WooCommerce and enter your store address. It must be https. 2. Approve Intrio with read and write access on WooCommerce's authorise screen. 3. Intrio creates an order.updated webhook signed with its own secret, an Online shop Sales programme with a 30-day hold if needed, and adds your store as an allowed tracking domain. ## Install the plugin Install Intrio for WooCommerce and paste your publishable key under Settings › Intrio. The plugin adds the tracking script to every page and, at checkout (classic and block), saves the partner on the order as _pp_ref, _pp_click and _pp_at (first-touch time, for the attribution window) meta. If Intrio gave you a different address, set Intrio URL there or define INTRIO_APP_URL in wp-config.php; it defaults to https://intrio.co. ## How orders are credited - Orders are recorded when their status is processing or completed, as woocommerce:order:. Later updates to the same order are duplicates. - The partner comes from the order's pp_ref / pp_click meta, otherwise from a coupon matching a partner's code. - Refunds on the order reduce or claw back the reward. > Without the plugin, only orders using a partner's coupon code can be credited. --- # Integrations: CRMs and accounting URL: https://intrio.co/docs/integrations/more Last updated: 2026-11-20 HubSpot and Xero are coming soon. How to connect CRMs and accounting tools today with the API and webhooks. Today Intrio integrates directly with Stripe, Shopify and WooCommerce. HubSpot and Xero are coming soon. Until then you can connect any system yourself: - Send payments and orders in with the Conversions API (/docs/api/conversions). - Get partner, referral and reward events out with webhooks (/docs/webhooks), for example to create a deal in your CRM when a referral is created. --- # Webhooks: Webhooks URL: https://intrio.co/docs/webhooks Last updated: 2026-11-20 Receive signed HTTP notifications when partners join, referrals change, conversions are recorded, rewards move and payouts are sent. Available on Growth and above. Webhooks send an HTTPS POST to your endpoint when something happens in your workspace. Use them to create CRM deals, notify your team, sync rewards to accounting or kick off onboarding. ## Set up an endpoint 1. Open Webhooks in your workspace and add an endpoint URL. 2. Choose the events to receive. 3. Copy the signing secret (whsec_…). It's shown once; you can rotate it later. 4. Click Send test event to deliver a ping and check your endpoint responds. ## Payload Every event has the same envelope. api_version is 2026-11-20. Amounts are integers in minor units with an ISO 4217 currency. Partner bank details are never included. JSON: ```json { "id": "evt_3Jf9xQ2mZr8LkP0aT1sW", "type": "referral.won", "created_at": "2026-11-20T10:15:00.000Z", "api_version": "2026-11-20", "workspace": { "id": "cmws_5q8r2t", "slug": "acme" }, "data": { "referral": { "id": "cmr_4h7d0q", "programme": "intro", "stage": "Won", "external_customer_id": "cus_9921", "company": "Acme Ltd" }, "partner": { "id": "cmp_8f2k1x", "code": "jane-a1b2", "name": "Jane Smith", "company": "Smith Advisory" }, "value": 1200000, "currency": "GBP" } } ``` - id (string, required): Unique event id, evt_…. The same id is used for every retry. Deduplicate on it. - type (string, required): The event type. - created_at (string, required): When the event happened, ISO 8601 in UTC. - api_version (string, required): Payload version, currently 2026-11-20. - workspace (object, required): id and slug of the workspace. - data (object, required): Event-specific data. See event types (/docs/webhooks/events). ## Headers - Intrio-Event-Id (string): Same as id. - Intrio-Event-Type (string): Same as type. - Intrio-Signature (string): t=,v1=. See signatures (/docs/webhooks/signatures). - User-Agent (string): Intrio-Webhooks/1.0. ## Responding Return any 2xx status within 10 seconds. Anything else, including redirects and timeouts, counts as a failure and is retried. See delivery and retries (/docs/webhooks/retries). --- # Webhooks: Webhook event types URL: https://intrio.co/docs/webhooks/events Last updated: 2026-11-20 Every Intrio webhook event, from referral created to payout paid, with a plain description of when it fires and an example JSON payload. Available on Growth and above. Subscribe each endpoint to the events it needs. Field values in these examples are illustrative. Event | When partner.applied | Someone applied through your public programme page. status is approved when applications are approved automatically (a partner.joined follows), otherwise pending until you review it. partner.joined | A partner joined the programme: accepted an invite, or was approved from an application. referral.created | A new referral was submitted by a partner, came in through a referral link, or was attributed from a tracked conversion. referral.stage_changed | A referral moved to a different pipeline stage. referral.won | A referral was won: marked as won by an admin or converted by its first paid conversion. conversion.recorded | A sign-up, payment, order or refund was recorded through the Conversions API, the tracking tag, Stripe or a shop integration. reward.created | A reward line was created for a partner. It may be held (building) or immediately payable. reward.payable | A reward became payable: the client paid, or the hold or return window passed. reward.voided | A reward was voided, for example because the referral left Won or the payment was refunded. payout.sent | A payout was sent to a partner, by bank transfer or through Stripe. reward.overdue | A requested payout passed your stated payout terms without being paid. Sent at 7, 14 and 30 days overdue; days_overdue says which. payment_report.created | A partner reported a payment problem with a reward or payout. Reply or resolve it from Payouts in your workspace. ping | A test event sent from the Webhooks page. Safe to ignore. > conversion.recorded has data.conversion.type of signup, payment, order or refund. Conversions that were unattributed, rejected or duplicates don't send it. ## Partners ### partner.applied Someone applied through your public programme page. status is approved when applications are approved automatically (a partner.joined follows), otherwise pending until you review it. JSON: ```json { "id": "evt_3Jf9xQ2mZr8LkP0aT1sW", "type": "partner.applied", "created_at": "2026-11-20T10:15:00.000Z", "api_version": "2026-11-20", "workspace": { "id": "cmws_5q8r2t", "slug": "acme" }, "data": { "application": { "id": "cma_6p2w9k", "name": "Jane Smith", "email": "jane@smithadvisory.co.uk", "website": "https://smithadvisory.co.uk", "describes": "Consultant or adviser", "promotion": "Introductions to my clients", "status": "pending" } } } ``` ### partner.joined A partner joined the programme: accepted an invite, or was approved from an application. JSON: ```json { "id": "evt_3Jf9xQ2mZr8LkP0aT1sW", "type": "partner.joined", "created_at": "2026-11-20T10:15:00.000Z", "api_version": "2026-11-20", "workspace": { "id": "cmws_5q8r2t", "slug": "acme" }, "data": { "partner": { "id": "cmp_8f2k1x", "code": "jane-a1b2", "name": "Jane Smith", "company": "Smith Advisory" }, "tier": "Bronze" } } ``` ## Referrals ### referral.created A new referral was submitted by a partner, came in through a referral link, or was attributed from a tracked conversion. JSON: ```json { "id": "evt_3Jf9xQ2mZr8LkP0aT1sW", "type": "referral.created", "created_at": "2026-11-20T10:15:00.000Z", "api_version": "2026-11-20", "workspace": { "id": "cmws_5q8r2t", "slug": "acme" }, "data": { "referral": { "id": "cmr_4h7d0q", "programme": "intro", "stage": "New", "external_customer_id": "cus_9921", "company": "Acme Ltd" }, "partner": { "id": "cmp_8f2k1x", "code": "jane-a1b2", "name": "Jane Smith", "company": "Smith Advisory" }, "source": "portal" } } ``` ### referral.stage_changed A referral moved to a different pipeline stage. JSON: ```json { "id": "evt_3Jf9xQ2mZr8LkP0aT1sW", "type": "referral.stage_changed", "created_at": "2026-11-20T10:15:00.000Z", "api_version": "2026-11-20", "workspace": { "id": "cmws_5q8r2t", "slug": "acme" }, "data": { "referral": { "id": "cmr_4h7d0q", "programme": "intro", "stage": "Proposal sent", "external_customer_id": "cus_9921", "company": "Acme Ltd" }, "partner": { "id": "cmp_8f2k1x", "code": "jane-a1b2", "name": "Jane Smith", "company": "Smith Advisory" }, "previous_stage": "Qualified" } } ``` ### referral.won A referral was won: marked as won by an admin or converted by its first paid conversion. JSON: ```json { "id": "evt_3Jf9xQ2mZr8LkP0aT1sW", "type": "referral.won", "created_at": "2026-11-20T10:15:00.000Z", "api_version": "2026-11-20", "workspace": { "id": "cmws_5q8r2t", "slug": "acme" }, "data": { "referral": { "id": "cmr_4h7d0q", "programme": "intro", "stage": "Won", "external_customer_id": "cus_9921", "company": "Acme Ltd" }, "partner": { "id": "cmp_8f2k1x", "code": "jane-a1b2", "name": "Jane Smith", "company": "Smith Advisory" }, "value": 1200000, "currency": "GBP" } } ``` ## Conversions ### conversion.recorded A sign-up, payment, order or refund was recorded through the Conversions API, the tracking tag, Stripe or a shop integration. JSON: ```json { "id": "evt_3Jf9xQ2mZr8LkP0aT1sW", "type": "conversion.recorded", "created_at": "2026-11-20T10:15:00.000Z", "api_version": "2026-11-20", "workspace": { "id": "cmws_5q8r2t", "slug": "acme" }, "data": { "conversion": { "id": "inv_1001", "type": "payment", "status": "recorded", "amount": 4900, "currency": "GBP" }, "referral": { "id": "cmr_4h7d0q", "programme": "intro", "stage": "Won", "external_customer_id": "cus_9921", "company": "Acme Ltd" }, "partner": { "id": "cmp_8f2k1x", "code": "jane-a1b2", "name": "Jane Smith", "company": "Smith Advisory" } } } ``` ## Rewards ### reward.created A reward line was created for a partner. It may be held (building) or immediately payable. JSON: ```json { "id": "evt_3Jf9xQ2mZr8LkP0aT1sW", "type": "reward.created", "created_at": "2026-11-20T10:15:00.000Z", "api_version": "2026-11-20", "workspace": { "id": "cmws_5q8r2t", "slug": "acme" }, "data": { "reward": { "id": "cmw_2n6s3p", "amount": 15000, "currency": "GBP", "state": "building", "referral_id": "cmr_4h7d0q", "partner_id": "cmp_8f2k1x" } } } ``` ### reward.payable A reward became payable: the client paid, or the hold or return window passed. JSON: ```json { "id": "evt_3Jf9xQ2mZr8LkP0aT1sW", "type": "reward.payable", "created_at": "2026-11-20T10:15:00.000Z", "api_version": "2026-11-20", "workspace": { "id": "cmws_5q8r2t", "slug": "acme" }, "data": { "reward": { "id": "cmw_2n6s3p", "amount": 15000, "currency": "GBP", "state": "payable", "referral_id": "cmr_4h7d0q", "partner_id": "cmp_8f2k1x" } } } ``` ### reward.voided A reward was voided, for example because the referral left Won or the payment was refunded. JSON: ```json { "id": "evt_3Jf9xQ2mZr8LkP0aT1sW", "type": "reward.voided", "created_at": "2026-11-20T10:15:00.000Z", "api_version": "2026-11-20", "workspace": { "id": "cmws_5q8r2t", "slug": "acme" }, "data": { "reward": { "id": "cmw_2n6s3p", "amount": 15000, "currency": "GBP", "state": "void", "referral_id": "cmr_4h7d0q", "partner_id": "cmp_8f2k1x" }, "reason": "Referral moved to Lost" } } ``` ## Payouts ### payout.sent A payout was sent to a partner, by bank transfer or through Stripe. JSON: ```json { "id": "evt_3Jf9xQ2mZr8LkP0aT1sW", "type": "payout.sent", "created_at": "2026-11-20T10:15:00.000Z", "api_version": "2026-11-20", "workspace": { "id": "cmws_5q8r2t", "slug": "acme" }, "data": { "payout": { "id": "cmo_7t1v5c", "amount": 45000, "currency": "GBP", "partner_id": "cmp_8f2k1x", "reward_ids": [ "cmw_2n6s3p", "cmw_8k3m1z" ] }, "method": "manual", "reference": "BACS 0412", "partner": { "id": "cmp_8f2k1x", "code": "jane-a1b2", "name": "Jane Smith", "company": "Smith Advisory" } } } ``` ## Payout assurance ### reward.overdue A requested payout passed your stated payout terms without being paid. Sent at 7, 14 and 30 days overdue; days_overdue says which. JSON: ```json { "id": "evt_3Jf9xQ2mZr8LkP0aT1sW", "type": "reward.overdue", "created_at": "2026-11-20T10:15:00.000Z", "api_version": "2026-11-20", "workspace": { "id": "cmws_5q8r2t", "slug": "acme" }, "data": { "payout": { "id": "cmo_7t1v5c", "amount": 45000, "currency": "GBP", "partner_id": "cmp_8f2k1x", "reward_ids": [ "cmw_2n6s3p" ] }, "days_overdue": 7, "overdue_since": "2026-11-13T10:15:00.000Z", "terms_days": 30 } } ``` ### payment_report.created A partner reported a payment problem with a reward or payout. Reply or resolve it from Payouts in your workspace. JSON: ```json { "id": "evt_3Jf9xQ2mZr8LkP0aT1sW", "type": "payment_report.created", "created_at": "2026-11-20T10:15:00.000Z", "api_version": "2026-11-20", "workspace": { "id": "cmws_5q8r2t", "slug": "acme" }, "data": { "report": { "id": "cmpr_1x9d4f", "reason": "not_paid", "amount": 45000, "currency": "GBP", "partner_id": "cmp_8f2k1x", "reward_id": null, "payout_id": "cmo_7t1v5c" } } } ``` ## Test ### ping A test event sent from the Webhooks page. Safe to ignore. JSON: ```json { "id": "evt_3Jf9xQ2mZr8LkP0aT1sW", "type": "ping", "created_at": "2026-11-20T10:15:00.000Z", "api_version": "2026-11-20", "workspace": { "id": "cmws_5q8r2t", "slug": "acme" }, "data": { "message": "Test event from Intrio" } } ``` --- # Webhooks: Verifying signatures URL: https://intrio.co/docs/webhooks/signatures Last updated: 2026-11-20 Verify the Intrio-Signature header with HMAC-SHA256 in Node, Python and PHP, with Next.js and Express examples. Available on Growth and above. Every delivery is signed so you can check it came from Intrio and wasn't changed or replayed. Header: ```text Intrio-Signature: t=1763633700,v1=5257a869e7ecebeda32affa62cdca3fa51cad7e77a0e56ff536d0ce8e108d8bd ``` 1. Split the header on ,. Take t (Unix seconds) and every v1 value. 2. Reject the event if t is more than 5 minutes from your clock. 3. Compute the hex HMAC-SHA256 of . using your full secret, including the whsec_ prefix, as the key. 4. Accept if it equals any v1 value, using a constant-time comparison. > Use the raw body: Sign-check the exact bytes you received. Parsing JSON and serialising it again changes whitespace and key order, and the signature won't match. Node: ```ts import crypto from "node:crypto"; const TOLERANCE_SECONDS = 5 * 60; /** Returns true if the raw body was signed with your secret in the last 5 minutes. */ export function verifyIntrioSignature(rawBody: string, header: string | null, secret: string): boolean { if (!header) return false; let t = 0; const signatures: string[] = []; for (const part of header.split(",")) { const [k, v] = part.split("=", 2); if (k === "t") t = Number(v); if (k === "v1" && v) signatures.push(v); } if (!t || Math.abs(Date.now() / 1000 - t) > TOLERANCE_SECONDS) return false; const expected = crypto.createHmac("sha256", secret).update(`${t}.${rawBody}`).digest(); // During a secret rotation there are two v1 values; accept either. return signatures.some((sig) => { const got = Buffer.from(sig, "hex"); return got.length === expected.length && crypto.timingSafeEqual(got, expected); }); } ``` Python: ```python import hashlib, hmac, time TOLERANCE_SECONDS = 5 * 60 def verify_intrio_signature(raw_body: bytes, header: str | None, secret: str) -> bool: if not header: return False t, signatures = 0, [] for part in header.split(","): k, _, v = part.partition("=") if k == "t": t = int(v) elif k == "v1": signatures.append(v) if not t or abs(time.time() - t) > TOLERANCE_SECONDS: return False expected = hmac.new(secret.encode(), f"{t}.".encode() + raw_body, hashlib.sha256).hexdigest() return any(hmac.compare_digest(expected, s) for s in signatures) ``` PHP: ```php 300) return false; $expected = hash_hmac('sha256', $t . '.' . $rawBody, $secret); foreach ($signatures as $sig) { if (hash_equals($expected, $sig)) return true; } return false; } $raw = file_get_contents('php://input'); if (!verify_intrio_signature($raw, $_SERVER['HTTP_INTRIO_SIGNATURE'] ?? null, getenv('INTRIO_WEBHOOK_SECRET'))) { http_response_code(400); exit; } $event = json_decode($raw, true); http_response_code(200); ``` Next.js: ```ts // app/api/intrio/webhooks/route.ts import { verifyIntrioSignature } from "@/lib/intrio-signature"; export async function POST(req: Request) { const raw = await req.text(); // the raw body, before any JSON parsing if (!verifyIntrioSignature(raw, req.headers.get("intrio-signature"), process.env.INTRIO_WEBHOOK_SECRET!)) { return new Response("Invalid signature", { status: 400 }); } const event = JSON.parse(raw); // Deduplicate: retries reuse the same id. if (await alreadyHandled(event.id)) return new Response("ok"); switch (event.type) { case "referral.created": await createCrmDeal(event.data.referral, event.data.partner); break; case "reward.payable": await notifyFinance(event.data.reward); break; } await markHandled(event.id); return new Response("ok"); } ``` Express: ```js import express from "express"; import { verifyIntrioSignature } from "./intrio-signature.js"; const app = express(); // Use the raw body for this route; express.json() would change the bytes. app.post("/webhooks/intrio", express.raw({ type: "application/json" }), (req, res) => { const raw = req.body.toString("utf8"); if (!verifyIntrioSignature(raw, req.get("intrio-signature") ?? null, process.env.INTRIO_WEBHOOK_SECRET)) { return res.status(400).send("Invalid signature"); } const event = JSON.parse(raw); res.sendStatus(200); // acknowledge quickly, then work queue.add(event); }); ``` ## Rotating the secret Rotate a secret from Webhooks. For 24 hours after rotating, each delivery carries two v1 signatures, one with the new secret and one with the old, so you can deploy the new secret without dropping events. Code that accepts any matching v1 handles this automatically. --- # Webhooks: Delivery, retries and best practices URL: https://intrio.co/docs/webhooks/retries Last updated: 2026-11-20 Webhook delivery guarantees, the retry schedule, automatic disabling and how to build a reliable handler. Available on Growth and above. ## Delivery - A delivery succeeds when your endpoint returns 2xx within 10 seconds. - Delivery is at least once: the same event can arrive more than once. Deduplicate on id. - Events can arrive out of order. Use created_at and the state in data, not arrival order. ## Retry schedule Failed deliveries are retried up to 8 attempts in all: Attempt | Delay after the previous failure 1 | Immediately 2 | 1 minute 3 | 5 minutes 4 | 30 minutes 5 | 2 hours 6 | 6 hours 7 | 12 hours 8 | 24 hours ## Disabled endpoints An endpoint that has failed continuously for 3 days is disabled, and the workspace owners are told by email and notification. Fix the endpoint, then re-enable it from Webhooks. ## Best practices - Verify every signature and reject old timestamps. - Respond fast: store the event, return 200, and do the work in a background job. - Make handlers idempotent: record processed ids and skip repeats. - Subscribe only to the events you need. - Treat the payload as a notification. If you need the latest state, look it up rather than relying on order. ## Testing locally 1. Expose your local server with a tunnel, for example cloudflared tunnel --url http://localhost:3000 or ngrok http 3000. 2. Add the tunnel's https URL as an endpoint in Webhooks. 3. Click Send test event to receive a ping, then trigger real events (invite a test partner, record a test conversion). To unit-test your handler, sign a sample payload yourself: Node: ```ts import crypto from "node:crypto"; const body = JSON.stringify({ id: "evt_test", type: "ping", created_at: new Date().toISOString(), api_version: "2026-11-20", workspace: { id: "ws", slug: "acme" }, data: { message: "Test event from Intrio" } }); const t = Math.floor(Date.now() / 1000); const v1 = crypto.createHmac("sha256", process.env.INTRIO_WEBHOOK_SECRET!).update(`${t}.${body}`).digest("hex"); await fetch("http://localhost:3000/api/intrio/webhooks", { method: "POST", headers: { "content-type": "application/json", "intrio-signature": `t=${t},v1=${v1}` }, body, }); ``` --- # Recipes: Next.js and Stripe Checkout URL: https://intrio.co/docs/recipes/nextjs-stripe Last updated: 2026-11-20 A SaaS on Next.js with Stripe subscriptions: capture the partner, tag the Stripe customer and let Intrio credit every invoice. This recipe needs no Intrio API key, so it works on every plan. Stripe reports each paid invoice; you only make sure the customer carries the partner. ## 1. Load the script app/layout.tsx: ```ts import Script from "next/script"; export default function RootLayout({ children }: { children: React.ReactNode }) { return ( {children}
``` On Growth and above, report the lead from your server: PHP: ```php true, CURLOPT_RETURNTRANSFER => true, CURLOPT_TIMEOUT => 5, CURLOPT_HTTPHEADER => ['Authorization: Bearer ' . getenv('INTRIO_API_KEY'), 'Content-Type: application/json'], CURLOPT_POSTFIELDS => json_encode([ 'id' => 'lead_' . $leadId, 'type' => 'signup', 'programme' => 'enquiries', 'ref' => $ref, 'click_id' => $_POST['pp_click'] ?: null, 'customer' => ['id' => (string) $leadId, 'email' => $_POST['email']], ]), ]); curl_exec($ch); } ``` Python: ```python import os, requests ref = request.form.get("pp_ref") if ref: requests.post( "https://intrio.co/api/v1/conversions", headers={"Authorization": f"Bearer {os.environ['INTRIO_API_KEY']}"}, json={ "id": f"lead_{lead.id}", "type": "signup", "programme": "enquiries", "ref": ref, "click_id": request.form.get("pp_click") or None, "customer": {"id": str(lead.id), "email": request.form["email"]}, }, timeout=5, ) ``` On Free or Starter, report from the browser after the form succeeds instead: intrio.track("lead", { customer: { email } }). --- # Recipes: Shopify brand with creators URL: https://intrio.co/docs/recipes/shopify-creators Last updated: 2026-11-20 Run a creator or influencer programme on Shopify with tracked links, personal discount codes and a returns hold before rewards are payable. 1. Connect Shopify (guide (/docs/integrations/shopify)). Intrio creates the shop programme, installs the script and listens for orders and refunds. 2. Set hold days on the programme to your returns window (30 by default), so rewards only become payable once returns are no longer possible. 3. Set creator tiers or a flat rate, and add rules for launches, for example +5% on the first payment for a month. 4. Invite creators. In the Intrio app in Shopify admin, give each one a personal discount code (their code in capitals, for example AMELIA10). 5. Creators share either their link or their code. Code-only sales (podcasts, video) are credited from the order's discount code. 6. When the hold ends, rewards become payable. Creators request payouts and you pay via Stripe (no Intrio fee; Stripe’s own fees apply) or bank. > The Shopify integration covers orders on its own. If you also paste the custom pixel snippet from the Tracking page, both record the order as shopify:order:, so it's credited once. --- # Recipes: Agency running several client workspaces URL: https://intrio.co/docs/recipes/agency Last updated: 2026-11-20 Run separate referral and partner programmes for each client from one login on the Agency plan, with their own partners, payouts and branding. Give each client their own workspace, so partners, currency, programmes, payouts and API keys stay separate. 1. On the Agency plan, create up to 10 client workspaces from one login (more for £25 a month each). 2. Pick each client's business type, so terms and modules fit (creators for a brand, introducers for a consultancy). 3. Create an API key and a publishable key per workspace. A key only ever acts on its own workspace, so one client's events can't land in another's. 4. Install the script on each client's site with that client's publishable key, and add their domains to the allowed domains. 5. Use the portfolio dashboard to see partners, revenue and rewards across every client. Partner codes are unique across Intrio, so a partner who promotes two of your clients has a different code in each. --- # Help: Troubleshooting URL: https://intrio.co/docs/help/troubleshooting Last updated: 2026-11-20 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. ## A partner link isn't crediting - 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/ 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. ## Cookie blocked or declined 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 (/docs/links/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. --- # Help: FAQ URL: https://intrio.co/docs/help/faq Last updated: 2026-11-20 Answers to common questions about referral and affiliate program attribution, rewards, payouts, plans and the Intrio API. ## Which partner gets credit if a visitor clicks two links? In the browser, the last partner link wins: a new link overwrites the cookie. Once a customer is credited (their first event), they stay with that partner. ## How long does attribution last? The cookie lasts data-days (90 by default). On the server, the first touch is checked against the programme's attribution window (1 to 365 days): the click's time for a click_id, otherwise attributed_at (the cookie's time, sent by the tracking script, the Node SDK's attributionFrom and the WooCommerce plugin). When neither is known, the event is accepted. ## Do partners pay anything? No. Partners always use Intrio free, and there's no fee on payouts through your own Stripe. See pricing (/pricing) for what each plan includes. ## Can I use the API on Free or Starter? The Conversions API, Node SDK and webhooks need Growth or above. On every plan you can use the tracking script, partner links, referral pages, and the Stripe, Shopify and WooCommerce integrations. ## What happens when I go over a plan limit? Nothing is lost. Everything is still tracked and credited, but the overflow is locked from view until you upgrade. See plan limits (/docs/concepts/plans-and-limits). ## Can I change commission rates later? Yes. Changes apply to new customers. Customers who have already paid keep the terms frozen at their first payment. ## Is there a sandbox? Not yet. See testing (/docs/api/conversions#testing) for a safe approach. ## Where is my data stored? Intrio is made in the UK and built for UK GDPR. Click tracking never stores IP addresses. --- # Help: Changelog URL: https://intrio.co/docs/changelog Last updated: 2026-11-20 New features, fixes and breaking changes to the Intrio API, browser and Node SDKs, webhooks and integrations, newest first. ## 20 November 2026 - Fixes: rejected and unattributed event ids can be resent once corrected (previously they returned duplicate). Successful ids are still processed exactly once. - Attribution window without a click id: new optional attributed_at on conversions and /api/v1/track. The tracking script, @intrio/node (attributedAt), the WooCommerce plugin and Shopify cart attributes send the cookie's first-touch time, so ?via= links and Stripe or shop orders respect the window too. - Stripe refunds: each refund is recorded under its own refund id and amount, so a second partial refund no longer reverses the cumulative total again. Refunds are matched through the PaymentIntent and invoice payments (charge.invoice is gone on current API versions). Also listens for charge.refund.updated. - Stripe Checkout: paid one-off Checkout payments are credited from checkout.session.completed using client_reference_id (intrio.clientReferenceId()) or session metadata, and the partner is written onto the Stripe customer so later invoices are credited. Subscription checkouts use the first invoice's id, so they're never counted twice. Reconnect Stripe to subscribe existing connections to the new events. - Shopify: the custom pixel and the Shopify app now record an order under the same shopify:order:, so using both can't credit an order twice. - Tracking script: pp_ref, pp_click and new pp_at fields are filled in forms rendered after page load (React and other frameworks) and again on focus and submit. intrio.attributedAt() added. - Browser sales on Sign-ups programmes are recorded as payments; on Sales programmes as orders. - @intrio/node: IntrioError.code is the result status (for example rejected) when the body has no error field, and there's no wait after the final failed attempt. - WooCommerce plugin: optional Intrio URL setting (or INTRIO_APP_URL in wp-config.php); saves the first-touch time as _pp_at. - Documentation: this site, with quickstarts, concepts, API and SDK reference, recipes and /docs/llms-full.txt for AI assistants. - Webhooks: signed outgoing webhooks for partners, referrals, conversions, rewards and payouts, with retries and secret rotation. Growth and above. API version 2026-11-20. - API on Growth: creating API keys now needs Growth or above. Existing keys keep working. - Soft plan limits: going over the partner or revenue limit locks the overflow from view instead of stopping tracking. - Conversions API POST /api/v1/conversions for sign-ups, payments, orders and refunds, idempotent on id. - Tracking script with ?via= links, data-domain for subdomains, form filling and intrio.track. - @intrio/node 0.1.0 with trackLead, trackSale, trackRefund and attributionFrom. - Integrations: Stripe (invoices, refunds, payouts), Shopify (orders, refunds, creator discount codes) and WooCommerce (orders, refunds, plugin).