A MEDIARAZZI tracking endpoint follows this basic pattern:
https://ads.mediarazzi.com/track/COMMERCIAL_KEY/impression
https://ads.mediarazzi.com/track/COMMERCIAL_KEY/start
https://ads.mediarazzi.com/track/COMMERCIAL_KEY/complete
https://ads.mediarazzi.com/track/COMMERCIAL_KEY/skip
The live VAST XML may append ?ctx=..., which carries a server-generated signed attribution context. Always use the exact tracking URL provided by VAST. Do not strip, fabricate, or re-sign it yourself.
Player responsibilities
For client-side ad insertion, the player/SDK typically fires the beacons when the corresponding playback event occurs. A tag fetch is not an impression. A native MP4 preview may play a video while never firing VAST beacons.
Testing
The MEDIARAZZI VAST Testing Lab can inspect XML. Signed test mode for supported account tags is intended to keep simulated lab traffic out of production reporting. External player testers generally don't automatically use this special signed mechanism; their playback may generate real tracking events.
Trust boundaries
Do not treat unvalidated sid or subid from a public URL as an authenticated publisher identity. Use account-scoped server configuration and treat caller-supplied attribution as reporting metadata, subject to validation.