Debug Vidyard in Chrome DevTools

What Vidyard traffic looks like

Vidyard is a B2B video platform, and its purpose shapes its traffic: the interesting output is not how many people watched, it is which known person watched how much. The analytics calls are built to be joined to a contact record in a CRM or marketing automation platform.

Endpoint pattern

Player embeds load from play.vidyard.com, usually keyed by the video's UUID; viewing analytics post to analytics-api.vidyard.com, with additional analytics and tracking paths on Vidyard hosts matched by pattern

Transport

Event posts during and after playback, reporting watched position rather than a single completed view

Key parameters

The video UUID identifies the asset, and a viewer identifier ties the session to a person. That identifier is what the marketing integrations resolve against a contact record

Notes

Vidyard is commonly deployed alongside a marketing automation platform, and in email campaigns the viewer identity arrives through the link the recipient clicked rather than through anything on the page

The two halves of a Vidyard embed, as they appear:

play.vidyard.com/<uuid>          player embed (asset identified by UUID)
analytics-api.vidyard.com        viewing analytics (matched, named Vidyard)

Debugging Vidyard with Event Watcher

• No dedicated parser. Requests are matched by hostname and URL pattern, named Vidyard, badged with the Video category, and shown with parsed query and body parameters plus cookies set and sent.
• The question to answer on any Vidyard page is whether the viewer is identified or anonymous. Open an analytics request and look for an identifier travelling alongside the video UUID. Its presence is the difference between aggregate video statistics and named viewing records.
• Grouping by Endpoint separates the embed load from the analytics posts, which makes it obvious whether a page has a player that never reports.
• Script Tree attributes the embed to the site's template, a tag manager, or another script. On B2B sites Vidyard usually arrives through the same tag manager as the rest of the demand-generation stack.

Vidyard and consent

Event Watcher checks Vidyard against the analytics consent category.

The analytics classification is the floor rather than the ceiling here. A platform whose stated value is attributing video views to named individuals and passing them to sales is doing more than measuring, and on many implementations a marketing gate is the more defensible position. The practical check is the one above: watch what the analytics call carries. An anonymous view is an analytics question, an identified one is not, and the request body is where that gets settled rather than in the vendor's category label.

Common debugging scenarios

• Views are not attributed to contacts. Check whether an identifier accompanies the analytics call at all. Anonymous traffic means the identity never reached the player.
• The player renders but nothing reports. No analytics-api.vidyard.com traffic during playback points at a blocker or a content security policy.
• Which video is embedded here? Read the UUID from the play.vidyard.com request and match it in the Vidyard dashboard.
• Duplicate view records. Check for two embed loads on the same page, typically the result of the script being present both natively and through a tag manager.
• Vidyard fires before consent. Filter to Vidyard and read the consent verdict on the first request of the session.