VPAID-and-simid-both-present
Both VPAID and SIMID creatives present in the same <MediaFiles>
The block contains both a VPAID and a SIMID . This is a valid dual-stack configuration used during migration: SIMID-capable players will use the , while older VPAID-capable players fall back to the . However, it may signal an incomplete migration rather than an intentional dual-stack, and the VPAID entry still carries all the platform compatibility risks. Once SIMID coverage is sufficient for your inventory, remove the VPAID entry.
Why this matters in production
Treat this as a cleanup signal. Even informational VPAID findings are useful because they help reduce legacy behavior before a platform removes support entirely. Migration rules exist to get legacy interactive tags onto supported primitives such as SIMID and OMID before platform support gets even narrower.
How to fix
If this is intentional, no immediate action required. Monitor VPAID delivery rate vs SIMID delivery rate. Once SIMID fill is sufficient, remove the VPAID <MediaFile> to clean up the tag.
VPAID-and-simid-both-present and other issues instantly.Validate a tag →