Skip to content
Browse documentation

Go-live checklist

The dashboard checklist explained item by item, plus the manual checks to run before you send paid traffic.

Last updated 3 min read

On this page

The Go-live checklist card on the dashboard (https://app.trackcrown.com/app) is computed from your data: an item is crossed out as soon as the condition is true. Each item links to the page where you complete it.

The seven automatic items#

#ItemDone whenWhere
1Tracking domain activeA tracking domain of your workspace (or the brand's shared domain) has status activeTracking domains
2Allowed destinations setAllowed destination domains in workspace settings is not emptyWorkspace settings
3First offerThe workspace has at least one offerOffers
4First partnerThe workspace has at least one affiliatePartners → Affiliates
5Partner postback firedAt least one outgoing postback was sent (including a test from the postback's page)Reporting → Postback log
6Test conversion receivedAt least one conversion is storedReporting → Conversions
7Google Ads template testedA transparent (/c/) click was logged in the last 90 daysTracking → Google Ads

Item 7 only matters if you run Google Ads; networks without Google traffic can ignore it.

Manual checks before paid traffic#

The automatic items prove that each part exists. These checks prove the whole flow works.

  1. Open each partner's tracking link once from the offer's Tracking tab. You must land on the destination with a 32-character click ID where {click_id} was.
  2. In Reporting → Clicks, open the click: status redirect, the right offer and partner, sub IDs filled.
  3. Pause the offer for a moment and open the link again: you should reach the offer's fallback URL (status fallback, reason paused). Activate it again.
  4. If you use landing pages, open the link with url_id=<id> for each page.

Conversions#

  1. Call the postback URL with &test=1 and a real click ID. The JSON answer validates token, click, event and money without storing anything.
  2. Send one real test conversion (without test=1) and check revenue, payout and status in Reporting → Conversions.
  3. Send the same postback again: it must be stored as a duplicate (when One conversion per click is on, or with the same txid).
  4. Check that the partner's postback fired in Reporting → Postback log with HTTP 2xx.
  1. The tracking domain shows certified in the Certification column (or you use the Final URL suffix + SDK setup).
  2. Run the Transparency tester on Tracking → Google Ads with a real final URL: HTTPS, one hop, exact Location, no cookie.
  3. Use the Test button in Google Ads on the ad's tracking template.
  4. After the first clicks, Reporting → Clicks shows link type transparent with click mode parallel or sequential.

Caps, targeting and money#

  1. Open the offer's Caps tab: limits as agreed with the advertiser; check Caps pacing in Reporting.
  2. Targeting tab: use Test a click for one allowed and one blocked country.
  3. Revenue & payout tab: the example conversion shows the expected revenue, payout and profit.
  4. Custom payout rules: use Conflict test if several rules could match.

Team and security#

  1. Every staff member has two-factor authentication (Settings → Users shows a warning otherwise).
  2. Postback tokens are only shared with the advertisers that need them (Settings → Postback tokens).
  3. Invoice details are filled in if you bill advertisers or pay partners (Settings → Workspace → Invoice details).

Partner experience#

  1. Use View as partner on a test partner to see the portal exactly as they will.
  2. Check the offer's marketplace text (Description, Restrictions) and creatives with {tracking_link}.
  3. If offer terms are required, accept them once as the test partner.
Something unclear or missing in this article?Tell us