Campaigns

A campaign is the unit an advertiser buys and an affiliate promotes. It carries the destination URL, the pricing on both sides of the deal, the rules that decide which traffic is accepted, and the list of affiliates allowed to send it. Everything else in AffClix — clicks, conversions, payouts, reports — hangs off a campaign.

What a Campaign Is

In other platforms you may know this object as an offer. The naming differs; the job does not. A campaign answers five questions, and it has to answer all five before it can take live traffic:

  • Where does the visitor go? The campaign URL, plus any landing pages you split across.
  • Who pays, and how much? Revenue is what the advertiser pays you. Payout is what you pay the affiliate.
  • What counts as a conversion? The events attached to the campaign and the validation window they are accepted in.
  • Which traffic is allowed? Targeting rules, capping, and the anti-fraud thresholds.
  • Who may promote it? Visibility plus the per-affiliate approval list.
AffClix campaign list showing total, active, pending and ended counts above a table of campaigns with payout, revenue and status columns
Campaigns → All Campaigns. Counters across the top; payout and revenue shown side by side on every row.

Anatomy of a Campaign

The margin on a campaign is the gap between the two prices it carries. Keeping them visible next to each other on the list screen is deliberate — an inverted campaign is the single most expensive configuration mistake in affiliate marketing.

ConceptWhat it meansSet on
RevenueWhat the advertiser pays you per conversion, as a fixed amount or a percentage of sale value.Basic Info
PayoutWhat you pay the affiliate. Must be at or below revenue unless you are deliberately buying volume at a loss.Basic Info
Payment modelThe action being bought — CPA, CPL, CPI, CPS, CPC, RevShare. Determines how revenue and payout are read.Basic Info
Campaign URLThe advertiser destination, with tracking tokens appended so click data survives the redirect.Basic Info
EventsThe conversions this campaign can record. Every campaign has a built-in initial event.Event
VisibilityPublic, Public + Require Approval, or Private. Controls who can see and request the campaign.Basic Info
Payout above revenue loses money on every conversion

There are legitimate reasons to run negative margin — buying data, honouring a launch commitment — but it should be a decision, not a typo. Check both numbers on the campaign list before you open traffic.

Before You Start

Two things must exist before a campaign can be saved:

An advertiser record. The campaign has to belong to one, and the field is required. See Create an Advertiser.
The advertiser's destination URL, along with whatever tracking parameters they expect you to pass. If they run their own tracker, ask which parameter carries your click ID.

Useful to have, but not blocking: the payout terms in writing, the geos the advertiser will accept, and any daily cap they have committed to.

The Setup Flow

Only Basic Info is available while you are creating a campaign. The other tabs stay disabled until the record exists, because each of them attaches rows to a campaign ID that has not been issued yet. Save first, then configure.

  1. Fill in Basic Info and save

    Identity, campaign URL, pricing and schedule. This is the only step that is mandatory to get a campaign on disk. See Create a Campaign.

  2. Attach your conversion events

    Set the validation window and decide whether repeat conversions are allowed. Generate the advertiser postback here.

  3. Add targeting and capping

    Restrict by geo, device or OS, and cap daily volume so you never oversell what the advertiser agreed to buy. See Targeting Rules and Capping.

  4. Set payout rules and upload creatives

    Per-geo or per-affiliate pricing overrides go in Payout Rules; banners and assets go in Creatives.

  5. Approve affiliates and hand out links

    Approve who may run it, then build each affiliate's tracking URL. See Manage Affiliates.

Tab Reference

Every tab on an existing campaign, and the article that covers it in depth:

TabWhat you configure there
Basic InfoIdentity, campaign URL, landing pages, pricing, schedule, description and KPI.
TargetingGeo, device, OS, browser and connection rules that accept or reject a click.
EventConversion events, validation window, duplicate handling, advertiser postback builder.
PayoutConditional revenue and payout overrides by geo, affiliate or event.
CappingClick and conversion limits per day, hour or month, globally or per affiliate.
AffiliatesApprove or reject access, and build per-affiliate tracking URLs.
CreativesBanners and assets affiliates can pull for this campaign.
Anti FraudClick-spam sensitivity, proxy and referrer policy, redirect policy, and trafficback.
CouponCoupon codes attributed to this campaign for offline and code-driven conversions.
Explore MoreJump-off points to reports, audit log, and the postback builders and tester.

Status and Lifecycle

StatusBehaviour
ActiveAccepts clicks and records conversions, subject to schedule, targeting and caps.
PendingConfigured but not yet taking traffic. Use while the advertiser contract is still open.
EndedClosed. Incoming clicks are rejected, and trafficback sends them elsewhere if configured.
Ending a campaign does not have to waste the traffic

Configure Fallback (Trafficback) on the Anti Fraud tab so that clicks arriving at an expired or capped campaign are redirected to another campaign instead of hitting a dead end.

Verify Before Launch

Run this list before you tell an affiliate the campaign is live:

Payout is at or below revenue, and both are in the currency you agreed.
The campaign URL carries {click_id} — without it, no conversion can ever be attributed back.
The advertiser has your postback URL and knows which parameter to return your click ID in.
A test click reaches the landing page and appears in the Clicks Report.
A test conversion fires and lands in the Conversion Report.
Caps match what the advertiser actually committed to buy.

The Link Tester walks a click through targeting, capping and redirect logic without spending real traffic, and tells you which rule rejected it.

Rate this article
★★★★★
Thanks for rating!

Was this article helpful?