Andrea Caravello

Marketing
Cello

Blog•
Oct 14, 2026 •
12 min read

What Is an Affiliate Link? Tracking Links in SaaS October 2026

You’ve shared an affiliate link, a customer has paid and the referral still has no commission. That can mean tracking broke, but it can also mean the purchase didn’t qualify under your program’s rules. Following the referral identifier from the first click to the billing account helps you separate missing credit from a correctly rejected reward.

Table of Contents

TLDR:

An affiliate link is a trackable URL that identifies an affiliate for conversion credit.
Clicks alone earn no commission. Your program rules determine reward eligibility.
Check referral parameters and disclosures; campaign tags alone do not prove affiliate status.
Map signup users to billing accounts to track credit when a different contact pays.
Cello’s User Referral and Partner Referral programs are distinct from affiliate programs.

Affiliate link meaning in B2B SaaS

An affiliate link is a trackable URL that identifies an affiliate so eligible conversions can earn credit under a program’s rules. For example, a SaaS signup URL that ends in https://draftdesk.example/signup?ref=affiliate_abc points to the signup page and identifies the approved promoter whose qualifying conversions earn commission. SaaS user referrals and partner referrals also use referral links, but they are distinct program types. A user referral URL could use the same format with ref=user_abc, identifying an existing user recommending the product to a colleague. The participant’s relationship and reward agreement distinguish the programs, not the parameter name or URL format. Cello calls these User Referral and Partner Referral programs.

The URL carries the identifier; cookies and server records preserve attribution separately.

A click or tracking parameter alone does not create a commission.

The conversion must meet the program’s eligibility rules.

The anatomy of an affiliate link

An affiliate link combines a destination with tracking fields that identify the participant and campaign.

Link part	Purpose
Destination path	Signup page
`ref=partner_abc`	Participant identifier
`utm_source=partner&utm_campaign=launch`	Traffic source and campaign tags

Campaign tags alone do not determine commission eligibility. Tracking fields must connect to the program’s attribution logic.

Direct links carry tracking fields to the destination.
Redirect links pass through another endpoint first.
Shortened links conceal a longer destination.

Program rules govern compensation across these formats.

Recognizing whether a URL is an affiliate link

An affiliate link is easier to recognize when you check both the URL and its publishing context.

Look for referral parameters such as ref or affiliate_id; names vary by program.
Inspect redirect destinations with a link preview or inspection tool. Shortened URLs can hide identifiers.
Read nearby compensation disclosures to check whether the sender earns money from qualifying purchases.

UTM tags alone do not confirm an affiliate relationship. Check program terms if needed. Tracking alone does not make a link unsafe.

Affiliate links, referral links and ordinary tracking links

Affiliate links, referral links and ordinary tracking links can share URL mechanics but serve different relationships and reward terms.

Program	Participant relationship	Distribution	Reward agreement
Affiliate	Approved promoter	Content or outreach	Commission on qualifying actions
User referral	Existing user	Peer recommendations	Referral incentive
Partner	Business collaborator	Introductions or joint campaigns	Negotiated compensation

Ordinary campaign tracking identifies traffic sources. Participant-level attribution connects eligible conversions to rewards; program terms determine whether payment requires a purchase. Choosing between these program types is covered in referral vs affiliate program for B2B SaaS.

How affiliate links track a SaaS conversion

An affiliate link connects a SaaS subscription to the affiliate who referred it. In fictional DraftDesk’s program, only paid subscriptions qualify.

DraftDesk generates an approved affiliate’s link, which they share in a tutorial.
A prospect clicks; the landing page captures the referral identifier.
At trial signup, DraftDesk attaches the identifier to the customer record.
When the trial converts, DraftDesk records the billing event.
Program rules assign conversion credit to the affiliate; eligibility checks determine reward approval.

Attribution windows, cookies and server-side records

First-click attribution credits the earliest eligible click; last-click credits the latest. The attribution window determines click eligibility, but browser storage can expire sooner.

WebKit’s Intelligent Tracking Prevention (ITP) 2.2 imposed a one-day cookie cap on JavaScript-set persistent cookies when navigation originated from a classified cross-site tracking domain and the destination URL contained a query string or fragment. This was conditional, not universal. WebKit later removed the JavaScript cookie expiration cap in a 2022 update, but JavaScript cookies remain subject to ITP’s script-writable storage deletion rules.

Server-side records preserve existing referral associations, not automatic anonymous cross-device identification. Privacy obligations still apply. Some programs pair tracking links with referral codes as a shareable alternative identifier.

Creating and distributing tracking links

Growth or partnerships should own commercial rules; engineering or revenue operations (RevOps) should own event mapping before tracking links are distributed.

Enroll eligible participants and generate unique identifiers.
Choose destinations that match each recommendation.
Set attribution rules and reward eligibility.
Map signup and billing events, then test a referral through reward approval.

Offer in-product sharing for users, partner dashboards for external participants, permission-based email and sales-assisted introductions. Keep recommendations relevant to recipients’ needs; avoid indiscriminate distribution.

Account-level attribution connects the signup user to the purchasing company when a different contact pays.

Attach the referral identifier to the signup record.
Map the user to an organization ID, customer relationship management (CRM) opportunity and billing customer.
Match payment events through those records without requiring identical signup and payer emails.

For multiple referrals into one account, define which eligible claim wins and exclude existing customers per program terms, whether they arrive through user referrals or partner referrals. Log identifiers, timestamps and decisions to investigate reward disputes and prevent duplicate credit.

How subscription commissions become approved payouts

Attributed revenue assigns sales credit; earned commission follows program terms. Approval clears checks and holds; payment transfers funds.

Create a text-free editorial diagram illustrating how B2B SaaS subscription commissions become approved payouts. Wide horizontal composition, clean flat vector style, off-white background, dark navy outlines with restrained violet and teal accents and generous whitespace. Show a left-to-right process connected by arrows: a database cylinder with a chain-link symbol representing attributed revenue; a geometric decision gate with a shield and checkmark representing reward eligibility checks; an hourglass representing the review hold; finally a bank-building icon receiving a transfer arrow representing payout after approval. A small muted branch from the decision gate ends at a closed barrier to show that not every attributed conversion qualifies. Use only clear pictograms and geometric shapes. No text, words, letters, numbers, labels, logos, currency symbols, watermarks or typographic marks anywhere. No retail shopping imagery, coin piles, celebration or growth charts. This is a conceptual operational diagram, not a product screenshot. Keep the distinct review gate and hold visually between the attribution record and bank transfer so attribution is not depicted as instant payment.

One-time rewards cover qualifying conversions; recurring rewards cover eligible renewals. Calculate commissions on collected revenue, define refund and cancellation payout rules and hold payouts for review. Finance should verify payment methods, recipient countries and fees.

Svix documents Stripe’s live-mode delivery retries for up to three days after failure, making duplicate-event checks necessary to keep retries from generating duplicate commissions. Store and check processed event IDs before creating rewards to prevent duplicate commissions, including teams following referral attribution setup without Stripe or Chargebee.

Measuring link performance and fixing attribution gaps

Tracking links measure referral traffic, qualified signups, paid conversions and collected revenue, not acquisition lift. Calculate signup rate as qualified signups divided by tracked visitors; paid conversion rate as paying customers divided by referred signups. Include reward costs in program economics.

For missing credit, check in order:

Did parameters survive?
Did redirects reach the destination?
Does signup map to the billing account?
Was the conversion event received?

Missing records suggest tracking failure; recorded conversions can correctly fail eligibility rules.

Disclosure, privacy and abuse prevention

Place clear compensation disclosures beside affiliate recommendations and publish readable program terms.
Minimize collected data and keep personal information and secrets out of affiliate link URLs.
Send questions about regional disclosure requirements, such as the US Federal Trade Commission (FTC) endorsement guidelines, for legal review. Server-side tracking does not guarantee compliance.
Use program controls to check self-referrals, duplicate claims and refunds. Keep an auditable dispute process, and match the safeguards to the relevant B2B SaaS referral program category. Affiliate links cannot enforce these safeguards themselves.

How Cello connects tracking links to User-Led Growth

Cello makes User-Led Growth measurable by connecting recommendations from existing users to referred signups and paid conversions. Its embedded Referral Component gives each user a personal tracking link to share with colleagues without leaving the product to join a separate referral portal. Partner Referrals use a standalone Partner Portal where external participants access their links and track referral progress. With signup and purchase tracking connected, Cello uses server-side attribution and billing data from systems such as Stripe or Chargebee to associate conversions with the referrer. For revenue-based campaigns, verified payment events trigger reward calculation under the program’s eligibility rules, while fraud checks and payout processing govern reward release. This connects link sharing to attributed revenue and rewards, so operators can assess referrals as an acquisition channel instead of counting clicks alone.

Key takeaways

Clear rules keep tracking credit separate from approved payouts.
Test your setup before sharing links more widely.

Can you launch Cello Partner Referrals before adding an in-product widget?

You can start with Cello’s standalone Partner Portal without embedding the user referral widget. Partners can access their links and performance dashboard there, but your team still needs to connect signup and conversion tracking before those links can produce reliable reward records.

How do you test Stripe affiliate tracking before distributing your links?

Test the full referral flow and its failure cases, including a paid conversion, failed payment, refund and repeated webhook delivery. Check that the referral identifier reaches the correct billing customer, only eligible collected revenue generates commission and repeated events do not create duplicate rewards. Keep the event IDs and expected outcomes as a repeatable launch checklist.

Can you use Cello tracking links if finance needs to pay partner commissions outside Cello?

Cello supports manual reward processing, so finance can retain control of commission payments while Cello handles attribution and reward calculation. Confirm the setup with Cello before launch, then assign responsibility for approving rewards, recording completed payments and handling refunds so the same commission is not paid twice.

Can you use UTM tags alone to track commissions for a small affiliate program?

UTM tags alone are not a reliable commission record, even for a small program. Use a unique affiliate identifier linked to signup and billing records, then retain UTM tags for campaign reporting.

How should you connect a referral to Stripe if your team creates billing customers manually?

Your team should copy the captured referral identifier onto the correct billing customer record before processing the qualifying payment. Keep the signup user ID and organization ID linked to that record, then check that the payment event reaches your reward system.

Will your affiliate tracking still work if someone clicks on mobile but signs up on a laptop?

Cross-device attribution requires a reliable connection between the original referral and the later signup. An existing account association or a referral code entered during signup can provide that connection; server-side storage alone cannot identify the same anonymous visitor across devices.

Can you put affiliate links in PDFs or marketing emails without sending people to a dashboard first?

Affiliate links can work in PDFs and marketing emails when they contain the correct participant identifier and reach a tracked landing page. Check the final PDF or delivered email because redirects and email link rewriting can alter the URL, and place a clear compensation disclosure near the recommendation.

Do you need a new affiliate link for every prospect, or can each affiliate reuse one?

An affiliate can generally reuse the same unique link for multiple prospects. Keep the affiliate identifier stable and use supported campaign tags to compare placements without creating a new participant record for each visitor.

Should you extend your attribution window if your free trial lasts longer than browser cookies?

Set your attribution window around the buying cycle, not browser cookie duration. Preserve the referral association on the customer record at signup and state whether the window applies to signup or paid conversion, so a valid trial referral is not lost through unclear timing rules.

How do you preserve affiliate attribution when your link points to a pricing page instead of signup?

Capture the referral identifier on the pricing page and carry the association through to account creation. If signup happens on another domain or subdomain, configure and test that handoff because browser storage is not automatically shared across every destination.

How do you credit an introduction when your prospect never clicked an affiliate link?

Use a documented manual attribution process if your program permits introductions without a tracked click. Record the referring participant, introduction date and customer account, then check existing claims and eligibility before approving credit.

Can you keep affiliate links in old content after changing your commission rules?

Existing links can remain usable if their identifiers still resolve and your tracking system preserves their participant associations. Separate link validity from reward terms by documenting which referrals retain earlier terms and when new terms take effect.

Who should own your tracking setup if growth runs the program but engineering owns billing?

Growth or partnerships should own attribution and reward rules, while engineering or revenue operations owns the mapping between referral identifiers, signups and billing events. Finance should approve payout controls, and a named program owner should coordinate missing-credit disputes across those teams.