Skip to content
Browse documentation

Manage advertisers

Create advertiser records, hand out their postback token and integration snippets, manage portal users, and use every tab of the advertiser page.

Last updated 5 min read

On this page

An advertiser is the company whose offers you run and who pays you for conversions. Advertisers are listed under Offers → Advertisers (https://app.trackcrown.com/app/advertisers). Every staff role can view them; managers, admins and owners can create and change them (permission advertisers.write).

An advertiser record gives you three things:

  • its own postback token, so the advertiser can report conversions for its offers only;
  • invoices in its currency and billing terms;
  • an optional advertiser portal where its users see their offers, conversions, postback log and invoices.

Offers without an advertiser use the workspace postback token instead (typical for brands running their own program).

The advertiser list#

Columns: Advertiser, Status, Offers, Revenue 30d, Currency, Account manager and Created; Company, Contact, Email, Country, Terms, Portal users and Tags can be shown from the column menu. Filters: Status, Manager (including Unassigned), Tag and Currency (when you bill in several).

Bulk actions for selected advertisers: Set active, Pause and Set inactive.

Create an advertiser#

  1. Click New advertiser.
  2. Fill in the sheet:
FieldNotes
NameRequired. "Shown in reports, invoices and the advertiser portal."
Company, Contact name, Email, Phone, Website, CountryOptional contact details
CurrencyRequired. The invoice currency.
Billing termsprepaid, due_on_receipt, net7, net15, net30, net45, net60 or net90 — "Sets invoice due dates."
Account managerA member of your team
StatusActive, Paused or Inactive (below)
TagsComma separated, e.g. finance, direct, tier-1
Notes"Internal — never shown to the advertiser."
  1. Save. The advertiser gets its own random postback token.

Statuses#

StatusMeaning
Active"Working account: offers run, postbacks accepted, portal open."
Paused"Offers stop, postback token refused; portal stays open."
Inactive"Like paused, and the portal is closed; history kept." Portal users see "Advertiser account inactive".

A Paused or Inactive advertiser stops its traffic and its postbacks:

  • Offers act as paused on affiliate links (/r, /click), smart links and server-side clicks (/clk error code 4): clicks go to the fallback chain with the reason paused, and smart links skip the offers. The offers keep their own status, so setting the advertiser active again resumes them as they were.
  • Transparent links are unchanged: a request with url= (Google Ads templates) still redirects to exactly that URL; the click only records the reason.
  • Its postback token is refused: postbacks and status updates sent with the advertiser's token get HTTP 401 with advertiser_inactive and record nothing. The workspace token keeps working for its offers, and pixel or SDK conversions (which carry no token) are still accepted. The inbound postback log shows these requests as Advertiser inactive.
  • Portal: a paused advertiser's users can still sign in and see the notice "Your account is paused"; an inactive advertiser's users cannot open the portal. Reports, conversions and invoices are kept.

Change the status from the advertiser page's ⋯ menu (Set active, Set paused, Set inactive — each with its effect underneath) or with the bulk actions. Pausing or deactivating asks for confirmation and explains the effect first. While the advertiser is paused or inactive, its page shows the banner "This advertiser is paused — its offers do not receive traffic" (or inactive).

Delete an advertiser#

Delete advertiser… in the ⋯ menu works only for advertisers without offers, conversions or invoices. Otherwise the dialog explains what still references it ("Deleting would break reports and billing history") and offers Set inactive instead. Deleting asks you to type the advertiser's name.

The advertiser page#

The header has New offer (pre-selects this advertiser), Edit details and the ⋯ menu.

TabContents
OverviewThe advertiser's numbers and details
OffersIts offers
IntegrationPostback token and ready-to-send snippets (below)
Portal usersLogins for the advertiser portal
InvoicesIts invoices (visible to roles with billing access). See Invoices.
DocumentsInsertion orders and contracts, optionally for e-signature. See Documents & terms.
Accounts & dealsParent advertiser and link template, the advertiser's own partner sign-up page, deals and product feeds. See Parent and child advertisers, Advertiser sign-up and Deals and product feeds.
Postback securityIP allowlist for the advertiser's postback servers, the migration postback, our outbound IPs and advertiser-scoped postback rules (below)
Notes"Only your team sees these notes."

Integration tab#

Everything the advertiser's developers need, built for your active tracking domain:

CardContents
Postback tokenThe token (hidden for roles that may not see tokens) and Regenerate token
Server-to-server postbackPostback URL (all parameters) and Minimal (default event, click ID only), with a description of each parameter
Conversion pixelsImage, iframe and JavaScript pixel snippets per offer and event
Landing-page SDKThe sdk.js tag for every page ("Every page (in <head>)") and the call On conversion
Test the integration (test=1)"Sends a validation-only request through the live postback endpoint with this advertiser's token … Nothing is recorded, billed or sent to affiliates."

Example of a minimal postback URL:

URL
https://trackcrown.com/pb?click_id={click_id}&token=ADVERTISER_TOKEN

Parameters, responses and pixels in detail: S2S postback, Pixels, Landing-page SDK.

Postback security tab#

  • Postback server IPs → Allowed IPs and ranges — the addresses the advertiser's servers post from (one per line, IPv4/IPv6 or CIDR, at most 100). They are enforced only on offers that turn enforcement on (offer → Conversion rules tab, or in bulk from the offer list); the card Offers enforcing the allowlist lists them. Without enforcement, "postbacks are accepted from any address with a valid token". Requests from other addresses on enforcing offers are stored as rejected (ip_not_allowed).
  • Migration postback URL — while moving from another tracker, postbacks whose click ID is not ours are forwarded here. See Migration postback.
  • Our server IPs — "Partner postbacks and migration postbacks are sent from these addresses — share them if the advertiser filters by IP."
  • Postback rules for this advertiser — "Approve, reject or hold this advertiser's conversions from adv1–adv5, amount, order id and more." See Conversion rules.

Portal users#

Add users on the Portal users tab; each gets an invitation link (e-mailed when outgoing e-mail is configured). Advertiser users see their own offers and conversions, with revenue as their cost — never partner payouts. What they can do is described in the Advertiser portal guide.

Something unclear or missing in this article?Tell us