Pre-Launch Campaign QA and Creative Trafficking for Regulated Media

A trafficking pass on a live igaming account usually returns somewhere between fifteen and forty defects, and only two of them ever cost real money: a creative serving into a market where the operator holds no licence, and a third-party click tracker that swallows the DSP click macro so every click lands on the homepage instead of the deposit flow. Both are caught before the first impression serves, or they are not caught at all. What gets checked before launch: The ad server build in Campaign Manager 360 or Flashtalking, placement-to-creative mapping, and every click string tested end to end with the macro expanded rather than assumed. HTML5 payloads against polite-load weight and initial file limits. In-app creative through the Open Measurement SDK rather than the VPAID paths some vendors still ship. VAST wrapper chains counted and timed, because four hops is where video error rates start climbing and where we stop and ask the exchange why. Cache-busting on every 1x1. The conversion event firing on the confirmation step rather than on the button click, which is the single most common reason a client's numbers and the platform's numbers never agree. The regulated-market pass: Brazilian fixed-odds betting has operated under a licensing regime since 1 January 2025, and the advertising obligations travel with the creative, not with the media plan. We check the age mark and the responsible-gambling line for legibility at the smallest size the creative will actually serve, not in the master artwork where everybody looks at it. We check that the landing domain matches the licensed property the operator actually holds. We check that no market in the geo tree receives creative the operator is not licensed to advertise in, including the markets that arrive quietly through a broad LATAM run-of-network line nobody remembered to fence. Discrepancy reconciliation: Ad server against DSP, daily, for the first fortnight. Two to five percent is latency and we will not bill you to chase it. Above ten percent something is structurally wrong, usually a mismatched counting method, a tag firing twice, or a wrapper timing out, and we open it with the exchange and see it closed rather than footnoting it in a report. Outside igaming: For gaming and energy advertisers the licence check falls away and the discipline does not. The same wrapper counting, the same macro expansion, the same refusal to launch against a plan nobody has read. Energy campaigns in Brazil carry their own claim exposure: a tariff or savings percentage in a creative needs a source that survives a regulator's question, and we will not traffic a number we cannot point at a document for. What this does not include: Creative production, resizing or design. Media buying and in-flight optimisation. Landing page or tag manager development beyond specifying what must fire and where. We hold no ad server contract in our own name. We do not work in accounts where we cannot get named seat access; a shared login is a refusal rather than a negotiation, and it is the only thing we are inflexible about at the contracting stage. Who this is not for: Teams shopping for a per-creative trafficking rate. Advertisers who want QA to run after launch as a reporting exercise, which is auditing, not QA. Anyone who needs a large creative matrix live on Friday. The volume is never the problem; the review is, and a review compressed into an afternoon is theatre that produces a signed launch and the same defects. How the work runs: One named person owns the account, reads the media plan and the licence position before touching the ad server, and signs the launch. Findings arrive as a defect list with severity, owner and the exact string or setting to change, in English or Portuguese.