Redirect health check — 5-step latency audit
Every hop in your redirect chain adds latency and a failure point. Audit monthly and after any infrastructure change.
— Count your hops. Open the offer link in a network inspector and log every 301/302. Target is 2 or fewer: tracker, then offer. Three-plus means you are leaking users.
— Measure time to first byte on your redirect domain. Over 200ms loses mobile traffic. Test from the GEO you actually run, not your home connection.
— Verify HTTPS end to end. One HTTP hop in the chain triggers a browser warning and kills conversion. Check every hop, not just the entry.
— Confirm the tracking domain is not on a public blocklist. A flagged redirect domain gets stripped by ad networks and antivirus. Check it before, not after, the ban.
— Test the fallback. Kill the offer URL and confirm your redirect rule sends traffic to a backup path, not a blank page or a tracker error.
Log the hop count and time to first byte each month. A redirect chain that grew from 2 hops to 4 over a quarter is the silent reason your conversion rate slipped.
Save this SOP. Run this before every launch.
—
Если тема зашла, посмотри @creator_playbook
Every hop in your redirect chain adds latency and a failure point. Audit monthly and after any infrastructure change.
— Count your hops. Open the offer link in a network inspector and log every 301/302. Target is 2 or fewer: tracker, then offer. Three-plus means you are leaking users.
— Measure time to first byte on your redirect domain. Over 200ms loses mobile traffic. Test from the GEO you actually run, not your home connection.
— Verify HTTPS end to end. One HTTP hop in the chain triggers a browser warning and kills conversion. Check every hop, not just the entry.
— Confirm the tracking domain is not on a public blocklist. A flagged redirect domain gets stripped by ad networks and antivirus. Check it before, not after, the ban.
— Test the fallback. Kill the offer URL and confirm your redirect rule sends traffic to a backup path, not a blank page or a tracker error.
Log the hop count and time to first byte each month. A redirect chain that grew from 2 hops to 4 over a quarter is the silent reason your conversion rate slipped.
Save this SOP. Run this before every launch.
—
Если тема зашла, посмотри @creator_playbook
Postback QA — 7-point pre-launch checklist
A broken postback means you optimize blind for hours. Verify before traffic, not after.
— Fire a manual test conversion from the network panel, confirm it lands in your tracker within 60 seconds
— Confirm the {click_id} / {cid} token in the postback URL matches the exact parameter your tracker reads (a tracker expecting
— Check the payout token resolves to a number, not
— Verify the status parameter maps correctly: approved vs pending vs rejected each route to the right event
— Confirm HTTPS on the postback endpoint; mixed protocol calls get dropped by some firewalls
— Test a duplicate fire — your tracker must dedupe on click_id, not double-count
— Check the postback IP isn't rate-limited or whitelisted-out on your server
Log the test conversion ID so you can trace it end to end if numbers disagree later.
Save this SOP. Run this before every launch.
A broken postback means you optimize blind for hours. Verify before traffic, not after.
— Fire a manual test conversion from the network panel, confirm it lands in your tracker within 60 seconds
— Confirm the {click_id} / {cid} token in the postback URL matches the exact parameter your tracker reads (a tracker expecting
cid ignores clickid silently)— Check the payout token resolves to a number, not
{payout} as literal text — a string breaks revenue math— Verify the status parameter maps correctly: approved vs pending vs rejected each route to the right event
— Confirm HTTPS on the postback endpoint; mixed protocol calls get dropped by some firewalls
— Test a duplicate fire — your tracker must dedupe on click_id, not double-count
— Check the postback IP isn't rate-limited or whitelisted-out on your server
Log the test conversion ID so you can trace it end to end if numbers disagree later.
Save this SOP. Run this before every launch.
Campaign naming convention — the 6-field framework
Inconsistent names make reporting useless after 30 campaigns. Lock one schema and never deviate.
Format:
— GEO: ISO country code, uppercase (US, DE, BR) — never "usa" or "United States"
— VERTICAL: fixed abbreviation list you write down once (NUTRA, GAMB, DATE, FIN)
— SOURCE: traffic source code (FB, GADS, PUSH, POP)
— OFFER: network offer ID, not the offer name (names change, IDs don't)
— ANGLE: your creative/funnel concept in one token (fear, social, discount)
— DATE: YYMMDD launch date for cohort tracking
Example:
Rules that keep it clean:
— Underscores between fields, never spaces or dashes inside a field
— Lowercase only for the ANGLE field so it's scannable
— Maintain the abbreviation list in a pinned doc; new verticals get added there first
This schema lets you filter "all DE push nutra" in two clicks across any tracker.
Save this SOP. Run this before every launch.
Inconsistent names make reporting useless after 30 campaigns. Lock one schema and never deviate.
Format:
GEO_VERTICAL_SOURCE_OFFER_ANGLE_DATE— GEO: ISO country code, uppercase (US, DE, BR) — never "usa" or "United States"
— VERTICAL: fixed abbreviation list you write down once (NUTRA, GAMB, DATE, FIN)
— SOURCE: traffic source code (FB, GADS, PUSH, POP)
— OFFER: network offer ID, not the offer name (names change, IDs don't)
— ANGLE: your creative/funnel concept in one token (fear, social, discount)
— DATE: YYMMDD launch date for cohort tracking
Example:
DE_NUTRA_PUSH_8841_fear_260613Rules that keep it clean:
— Underscores between fields, never spaces or dashes inside a field
— Lowercase only for the ANGLE field so it's scannable
— Maintain the abbreviation list in a pinned doc; new verticals get added there first
This schema lets you filter "all DE push nutra" in two clicks across any tracker.
Save this SOP. Run this before every launch.