Skip to main content
Server-to-server (S2S) tracking sends sign-up and sale events directly from your backend to Partnero. Attribution is carried by a key that you capture from the referral URL and persist—no PartneroJS snippet, no partnero_partner / partnero_referral cookies, and no client-side calls to the Partnero API.
Partnero also offers a second server-side method: postback URL tracking. It needs no API key — conversions are matched by a Partnero-generated click ID instead of a referral key. Use this guide when you want full control and rich customer/transaction fields; use postbacks for the simplest keyless setup or tracker-style integrations.

Why use S2S

  • Resilient to tracking blockers — ad-blockers, cookie-blocking browsers (Safari ITP, Brave, in-app browsers), and snippet load failures don’t affect attribution.
  • Backend-only stacks — works without any frontend JavaScript on your site.
  • Mobile and machine-to-machine — required for native apps and headless integrations.
  • Strict privacy regimes — no third-party-style storage, no extra consent banner row.
  • Full control — you decide where the referral key lives between landing and sign-up.
Always call the Partnero API from your backend. Keep Authorization: Bearer YOUR_API_KEY on the server—never embed it in browser or mobile code.

Endpoints used

All requests use https://api.partnero.com with Authorization: Bearer YOUR_API_KEY.

How it works

  1. Visitor lands via a referral link — for example yoursite.com?aff=REFERRAL_KEY. The exact query parameter depends on your program; confirm it under Programs → Settings → Referral links in the Partnero dashboard.
  2. You capture the key — read it from the URL and persist it your way (server session, database row keyed by anonymous ID, your own first-party storage, etc.).
  3. You call POST /v1/customers at sign-up with partner.key (affiliate) or referring_customer.key (refer-a-friend).
  4. You call POST /v1/transactions at purchase—or let a connected billing integration do it for you.
Partnero ignores invalid keys, so you can call the API for every sign-up without first checking whether the visitor was referred.

Three valid paths

All options below are server-side; they differ in what carries the attribution and where it comes from. For the hybrid path, see Affiliate API integration and Refer-a-friend API integration, which both show reading the PartneroJS cookie from the request.

Step 1: Capture the referral key

Read the parameter from the landing URL and persist it.

Step 2: Track sign-ups

When the user creates an account, call POST /v1/customers with the key from Step 1.

Affiliate programs

Use partner.key for the affiliate program key.
See Affiliate API integration for the full request body and additional partner identifier options.

Refer-a-friend programs

Use referring_customer.key for the referrer. Omit the field entirely if the visitor was not referred.
The response includes referral_link so you can show the new customer their share URL. See Refer-a-friend API integration for stats, balance, and reward endpoints.

Step 3: Track sales

Record purchases against the same customer.key you sent at sign-up. Partnero calculates the commission automatically.
Using Stripe, Paddle, or Chargebee? Connect them in Program → Integration and Partnero will create transactions automatically—you can skip Step 3.

When you cannot persist the landing click

If storing the referral key between landing and sign-up is impractical (e.g., podcast or video referrals), use attribution that doesn’t depend on a remembered visit:
  • Coupon-based tracking — partners share unique promo codes; checkout integrations attribute the sale.
  • Transaction-based attribution — set the program to transaction-based and pass partner_key in payment metadata so each charge selects the partner.

Comparison

Checklist

  1. Confirm your program’s referral link URL format and query parameter in the Partnero dashboard.
  2. Persist the referral key with your session or storage between landing and sign-up.
  3. Call POST /v1/customers from your server with partner or referring_customer.
  4. Call POST /v1/transactions (or let a billing integration do it) using the same customer key.

Next steps

Postback URL tracking

Keyless inbound conversion tracking with click IDs

Affiliate API

Cookie-based variant and full customer / transaction fields

Refer-a-friend API

Referrer fields, rewards, and dashboard API calls

Mobile apps

Deep links and native storage patterns

API reference

Full REST API documentation