Service
Network QA
Package agreed exports and return a dated record of the checks performed before delivery.
Concept illustration · Service stage
QA belongs to a specific build and destination
A statement such as ‘QA passed’ is too vague to reproduce. The receipt identifies the master or variant, package, target network, build timestamp, file size, language, orientation, test environment, checks performed, result, and known limitations.
The checks
- Package structure, entry point, asset references, file weight, and accidental development files.
- Initial load, first interaction, input blocking, visible feedback, win and fail paths, end card, and restart behavior where scoped.
- Portrait and landscape behavior only where those orientations are in scope, plus representative viewport and safe-area checks.
- Audio start and stop behavior, focus or lifecycle changes, CTA timing, click destination, and MRAID use where the target requires it.
- Unexpected network calls, console errors, permissions, personal-data collection, and known third-party dependencies.
Illustrative receipt row
Check | Environment | Illustrative result | Evidence or limitation |
|---|---|---|---|
First interaction | Mobile browser, portrait | Pass | Drag registered and changed board state |
CTA before interaction | Local harness | Pass | No automatic redirect observed |
Target network preview | Not run | Not tested | Requires account access and exact export |
The row above shows the form of a receipt, not a claim about an actual delivered build. A real receipt is created only after the named package is tested.
Current requirements are checked at export time
Network specifications change and can differ by product, placement, account, or upload path. The brief therefore names the destination, the source link, and the date checked. When public documentation does not answer a requirement, the receipt marks it unknown or account-specific and uses the network's current upload or preview tool where access is available.
What QA does not mean
Internal QA is evidence of the checks More Playables performed. It is not certification, external network approval, or a promise of campaign performance. An accepted file can still be affected by a later platform change, account rule, policy review, or integration outside the creative.
Download the editable QA checklist and inspect the illustrative sample receipt.