Advertisers and the event catalog: the record every offer hangs off

Ask most people to draw an affiliate program and they draw affiliates and offers. But there is a quieter record underneath both that decides how the whole thing behaves: the advertiser. Get the advertiser right and your reports, your payouts, and everything your partners see fall into place. Get it wrong and you spend months wondering why a "lead" is counting as a sale, or why an affiliate is getting pinged about an internal refund event. This guide explains what an advertiser is, why every offer hangs off one, and how the advertiser's event catalog is the single most powerful — and most misunderstood — part of program setup.

What an advertiser actually is

An advertiser is the company whose products your affiliates promote. For an in-house program, that advertiser is simply your own brand. For an agency or a network running traffic on behalf of several brands, each brand is its own advertiser, kept cleanly separate so one brand's numbers never bleed into another's.

The rule that makes advertisers foundational is this: every offer belongs to exactly one advertiser. An offer is a thing affiliates promote — a product, a signup funnel, a trial. Because each offer inherits its advertiser, the advertiser is the first record a brand-new program should create, before any offer, affiliate, or tracking link exists. If you are setting up from scratch, the getting-started walkthrough puts the advertiser at step one for exactly this reason.

Advertisers also carry contacts — the people you actually deal with at that brand, kept as a small address book on the record. Contacts don't touch tracking; they exist so the relationship has names and emails attached to it. The real weight sits elsewhere.

The event catalog: the heart of the record

Here is the idea that separates a real attribution platform from a link shortener with a dashboard. A funnel rarely has a single conversion. A visitor might become a lead, then register for a webinar, then buy, then upgrade. Each of those is a distinct action worth tracking, and each might pay differently — or not pay at all. The advertiser's event catalog is the list of actions that can be tracked and paid, and it is what lets one integration handle a whole funnel instead of just one moment.

Each event in the catalog carries a name, a type (Sale, Lead, Install, Signup, and so on), and its default economics: what the advertiser pays you when it fires, and what the affiliate earns — the baseline figures your offer contracts can later override. But the catalog's most important setting is a single toggle.

"Is a conversion": the switch that shapes every number

Every event has an is-a-conversion toggle, and it decides how that event is counted everywhere numbers appear — the analytics dashboard, every report, the affiliate portal, and the AI's answers.

When the toggle is on (the default), the event's rows count as conversions: they drive your conversion count, your conversion rate, and your headline totals. When it is off, the same rows count under a separate events metric instead — still recorded, still attributed to the right affiliate, still paid according to their economics — but kept out of your conversion count and conversion rate.

The crucial part is that the event's name has nothing to do with it. A "Lead" event counts as a conversion or as an event purely by its own toggle, not by what it is called. This is what lets you track meaningful mid-funnel actions — a signup, an add-to-cart, a page view — without them inflating the headline conversion number you probably want reserved for actual sales. If you have ever wondered why your reported conversion count looks smaller than the raw activity you know is happening, this toggle is usually the answer; the reports guide walks through exactly where the events metric surfaces.

"Published to affiliates": who sees what

The second toggle worth understanding controls affiliate visibility. When an event is published to affiliates, it shows up in their portal and their own postbacks can fire when it records. Turn it off and the event goes internal: it disappears from the partner-facing view and affiliate pixels stop firing for it, while your own tracking and reporting continue exactly as before.

This matters more than it sounds. Some events are for your books, not your partners' — a refund adjustment, an internal upsell step, a reconciliation event. Marking those internal keeps your partners' portal clean and stops them being pinged about actions that aren't theirs to see. Visibility can even be set per offer, so the same catalog event can be public on one offer and hidden on another.

How the pixel picks an event

The connection between the catalog and your tracking is elegant. A conversion pixel can name which event it is reporting, and if a pixel fires without naming one, it records the advertiser's default event — the single event you designate as the fallback. That is how one advertiser tracks leads on one page and sales on another using the same integration pattern: the pixel on the lead page names the lead event, the pixel on the purchase page names the sale, and anything unnamed lands on the default. The mechanics of firing conversions live in the conversion pixels and postbacks guide.

Overrides: one catalog, many deals

A single advertiser might run the same offer under different terms for different partner tiers. Rather than duplicate the catalog, an offer contract can override an event's amounts for that contract alone — paying more for the same lead to a premium partner, say, without touching the advertiser-wide defaults. The catalog stays the source of truth; the contract layers a deal-specific number on top. This "most-specific-wins" precedence is the same principle that governs payouts and contracts throughout the platform, and it is what keeps a growing program from collapsing into a pile of near-duplicate offers.

Where advertiser performance shows up

Once traffic flows, the advertiser becomes a reporting axis in its own right. An advertiser report breaks performance down per advertiser — clicks, conversions, conversion rate, revenue, payout, profit, margin, and EPC — answering the blunt question "which brand is actually making us money?" That is invaluable for an agency deciding where to invest attention, and useful even for an in-house team running several product lines as separate advertisers.

When conversions aren't showing up for an advertiser, the pixel log is the first place to look: it records every conversion-pixel fire received and how each was handled, which turns "the pixel isn't working" into a diagnosable event. The broader troubleshooting flow is covered in the no-conversions guide.

The mistakes that come from skipping this

Two setup mistakes trace directly back to not thinking about the advertiser and its catalog, and both are painful to fix after the fact. The first is treating every tracked action as a conversion by leaving the toggle on for events that shouldn't count — a page view, a mid-funnel step — which inflates the conversion count until it stops meaning anything and quietly distorts conversion rate across every report. The fix is cheap before traffic and awkward after, because changing what counts retroactively shifts historical numbers people have already reported.

The second is leaving internal bookkeeping events published to affiliates, so partners get pinged about refund adjustments or reconciliation steps that aren't theirs to see, and start asking confused questions about postbacks that fired for actions they never drove. Both mistakes are invisible on day one and expensive on day ninety. Deciding, per event, "does this count?" and "should partners see this?" at setup time is a few minutes of thought that saves months of cleanup — and it's why the catalog rewards being treated as a deliberate design step rather than a form to click through. For a broader map of how these settings ripple into what you can measure, the reports guide is the companion read.

Why this is worth getting right

The advertiser record is where the economics of your program are defined once and inherited everywhere. The event catalog decides what a conversion is, what gets paid, and what your partners see — three questions that otherwise generate endless confusion. Set it up deliberately and the rest of the platform behaves predictably: reports reconcile, payouts are correct, and partners see a clean, honest picture of what they can earn.

LimeliJourney treats the advertiser and its catalog as first-class structure, not an afterthought, which is what lets a single tracking integration carry an entire multi-step funnel. If you want to see a real catalog drive attribution end to end — a lead, a sale, and an internal event all flowing from one pixel — the tracking feature overview shows the mechanism, and a demo will map it onto your own funnel with you.