Foundations

Adding and managing affiliates: the partner record and the pending queue

What an affiliate record holds, how to review pending signups with accept or decline, why account managers matter, and how sub-IDs and the performance grid turn the affiliate list into your most-used report.

An affiliate program is only as good as its partner roster, and the roster is only useful if you can actually manage it: onboard new partners without letting bad ones in, keep ownership clear as the list grows, and see at a glance who is producing and who is dead weight. This guide is about the affiliate record — what it holds, how partners enter it, and how the same screen you use to manage affiliates doubles as the report you'll open more than any other.

What an affiliate is

An affiliate — also called a publisher or partner — is anyone who sends you traffic. That covers a lot of ground: a media buyer running paid ads, an email marketer with a list, a content site owner, an influencer with an audience. What they have in common is that they drive visitors to your offers and expect to be paid for the ones who convert.

In a well-structured program, each affiliate is a record, not just a link. The record carries their contacts, a status, a default traffic channel, and — importantly — an assigned owner on your team. That structure is what lets a program scale past the handful of partners you can keep in your head to the hundreds you can't.

Onboarding: the required field is just a name

Adding an affiliate should be fast, because the moment you meet a promising partner you want them in the system before the conversation cools. In practice the only thing you truly need is a name; everything else — status, channel, account manager, contact details, address, tax and payment information — can be filled in on the record afterward.

Two choices at creation are worth making deliberately. The channel captures a partner's default traffic type (email, social, display, search), which later lets you slice performance by traffic style; if you're unsure, leaving it to auto-detect is fine. And the option to send login details invites the partner straight into their portal, which is the fastest way to get them self-serving their tracking links and creatives instead of emailing you for them. Once a partner is in and running campaigns, the campaigns guide covers wiring them to specific offers.

Statuses and the pending review queue

Affiliates move through a small set of statuses, and understanding them is what keeps your roster honest. Active partners are working relationships. Pending partners are applications waiting for review. Declined marks an application you looked at and turned down. Inactive marks a relationship you've stopped. Filtering by status is how you separate the partners who matter today from the noise.

The pending queue is where quality control happens. Partners land in pending when they apply through your own website — via a partner signup integration — or when you deliberately create them as pending. When someone applies through your site, everything they submitted is there to review before you decide: their media type, traffic source, the countries they run in, their website, and any notes. This is your chance to filter out the low-quality or fraudulent applications that would otherwise pollute your data and your payouts.

A pending application resolves one of two ways. Accepting makes the partner active and lets them know they've been approved — though giving them portal access is a separate, deliberate step you take when you're ready. Declining requires a reason, which is emailed to the applicant and kept on the record; a declined partner keeps their history, and you can always change your mind and re-accept them later. Until a partner is accepted, they stay out of the pickers you use to build tracking links, campaigns, and invoices — so a pending applicant can never accidentally end up with live traffic. Their historical data, though, stays findable in report filters.

One distinction trips people up: this account-level review is not the same as offer approvals. Accepting an affiliate lets them into your program; offer approvals control which specific offers an already-accepted partner can see and promote. The two layers together let you say "yes, you're a partner" and "yes, but only these offers" independently.

The affiliate record: contacts, campaigns, and sub-IDs

Open any affiliate and the record fans out into the things you actually work with.

Contacts are the people at that partner, and they do real work: a partner can have several contacts, each potentially with their own portal login, and features like sending a creative pack email the contacts you list here. Keeping contacts current is what makes partner communication self-serve rather than a hunt through old emails.

Campaigns shows every campaign the partner runs, each connecting them to one offer under one contract. This is the operational heart of the relationship — the campaigns are what make a partner's tracking links attribute to them.

Sub-IDs is quietly the most valuable tab for optimization. A sub-ID is a tag a partner appends to their tracking link to label their own traffic sources, and this view breaks their traffic down by those tags. A single affiliate might be sending you five different traffic sources of wildly different quality; without sub-ID analysis they all blur into one average, and you either overpay for the bad or underappreciate the good. The sub-IDs guide goes deep on why this dimension is where the real optimization lives.

Account managers: ownership at scale

The account manager field ties a partner to a specific member of your team. On a small program this feels like overhead; on a growing one it's essential. Assigning managers keeps ownership unambiguous — every partner has someone responsible for the relationship — and it lets you filter the entire affiliate list and its performance numbers down to one person's book of business. When a partner has a question, there's a clear answer to "whose partner is this?"

The list is a report

Here is the part people underuse: the affiliate list is also a performance report. Each row shows that partner's metrics for a chosen date range — clicks, conversions, conversion rate, revenue, payout, profit, and earnings per click — and the columns sort. That means finding your top earners, or your zero-converting senders who look busy but produce nothing, is a single click. You can choose which metrics to show, save a filter-and-column setup you return to often, and, if you use account managers, narrow the whole grid to one manager's partners.

This dual nature — management screen and league table in one — is what makes the affiliate list the screen most program operators live in. It answers the two questions that never stop mattering: who are my partners, and which of them are actually working? For the full picture of how these numbers reconcile across the platform, the reports guide maps every report to the question it answers.

Portal access is a separate decision

One design choice worth calling out is that being an accepted affiliate and having a portal login are two different things. Accepting a partner makes them active in your program; giving them a portal login is a deliberate, separate step you take when you're ready. That separation is more useful than it sounds. It lets you bring a partner onto the roster — start building their campaigns, generating their links, tracking their traffic — before you've decided to hand them self-serve access, and it lets you manage a partner entirely on their behalf if that's the relationship. Contacts under a single affiliate can each get their own login too, so a media agency partner might have three people logging in independently. The upshot is that "in the program" and "can log in" are controls you set independently, rather than one implying the other, which keeps onboarding flexible instead of forcing an all-or-nothing moment.

This flexibility also matters for how you use a partner record before they're ever self-sufficient: you can wire up their tracking links and campaigns, run their traffic, and only invite them to the portal once the relationship is proven — turning portal access into a reward for a working partnership rather than a default you hand out on day one.

Why structured partner management wins

A pile of tracking links is not a program. Structured affiliate management — a real record per partner, a review gate on the way in, clear ownership, sub-ID visibility, and performance baked into the same view — is what lets you grow a roster without losing control of quality or losing track of who earns what.

LimeliJourney is built around that structure, so the affiliate you add in ten seconds today becomes a fully attributed, fully reportable relationship the moment their traffic starts flowing. If you want to see the partner lifecycle run end to end — application, review, campaign, and the performance grid filling in — the partners feature overview shows it, and a demo will set it up on your own roster with you.

See it on your own program.

Book a demo and we'll stand up your workspace, wire your tracking domain, and walk this through on your kind of data, with you.