Write a recipient-specific field contract
For each tag, define required, optional and prohibited fields and when it may run. Do not assume every tag needs the same object. Internal debugging information should not automatically become advertising data.
A fictional case can include an allowed event category and an explicitly prohibited marker. Never use real messages or customer information to demonstrate filtering. Define the outcome when a required field is missing too.
Test positive selection and new unknown fields
Send the allowed event and verify the recipient receives necessary information. Then add a new unknown property. Blocking one known field name is different from a resilient contract for future changes.
An allowlist also needs technically required parameters. An empty outgoing request may reduce data while making measurement unusable. Accept only when intended function and approved exclusions both hold.
| Test | Check | Expected evidence |
|---|---|---|
| Allowed fields | Normal receipt | Necessary function retained |
| Prohibited marker | All affected tags | No unapproved onward transfer |
| New unknown property | Future field extension | Approved default rule respected |
| Missing required field | Failure model | No false accepted outcome |
| Parallel browser route | Direct transfer outside container | Same data requirements respected there |
Inspect actual requests and rule scope
Compare the preview event object with what the tag actually sends. Check whether transformation scope, conditions and order cover the right tag. A similar event outside the matching condition can have a different outcome.
Also test another destination and a direct browser request where those routes exist. Server filtering cannot independently remove information already sent around it. Inventory operational logging separately from outgoing analytics requests.
Keep the boundary as a repeatable check
Record configuration version, test event, tag, recipient and observed outgoing content. Repeat the matrix after tag template, source or transformation changes. Restrict access to test evidence and avoid raw private data.
State exactly which boundary was verified. If the receiving side is unobservable, leave that part open. A technical pass does not certify legal compliance or establish that every real event can be measured.