Product proof
Inspect the evidence, including what is not proven yet.
This public fixture demonstrates the detection contract for four deliberate tracking problems. It is not presented as a customer case study or as completed independent provider validation.
Run identity
- Run date
- 2026-08-19
- Application
- 0.1.0-beta
- Environment
- Controlled fixture workspace
- Access
- read_only
Four deliberate problems
| Fixture | Observed evidence | Level | Result |
|---|---|---|---|
| TG-001: Purchase value missing Revenue value cannot be attributed from the observed request. | purchase request observed; value parameter absent | Browser request observed | Detected |
| TG-002: Duplicate purchase firing A single checkout may be counted more than once. | two purchase requests share the same transaction identifier | Browser request observed | Detected |
| TG-003: Incorrect currency Revenue reporting may be normalized incorrectly. | currency EGP conflicts with controlled fixture expectation USD | Browser request observed | Detected |
| TG-004: Required UTM parameter missing Campaign traffic cannot satisfy the configured naming policy. | utm_source and utm_medium present; utm_campaign absent | Configured | Detected |
Reproducible method
- Load the four sanitized fixtures used by the automated detection suite.
- Run the audit classifiers without a provider credential or write permission.
- Compare each actual finding with the expected detection contract.
- Confirm that each evidence label matches what was actually observed.
- Keep provider acceptance and platform-reported outcomes marked unverified until a live controlled tool records them.
Current validation gap
A full recording that compares these findings with Tag Assistant, GA4 DebugView, Meta Test Events, and TikTok test tools is still required. GTM and UTM apply-verify-rollback controls remain restricted to explicitly enabled test workspaces; this page does not claim that controlled-account acceptance testing is complete.
Evidence vocabulary
- Configured: a setting or resource was read from configuration.
- Browser request observed: a network request was captured in a browser test.
- Platform accepted: the provider returned a successful acceptance response.
- Platform reported: the provider later exposed the event or metric in reporting.
- Unverified: the available evidence cannot support a stronger claim.
Next review
Read the capability matrix before connecting an account, or start the paid beta .