GAM ads
Configure Google Ad Manager (GAM) to deliver your ad inventory through the Experiences SDK and into the Experiences player.
If WSC Sports manages ad delivery for your integration, start with the GAM MCM connection.
GAM guides
- GAM MCM connection: Link your GAM inventory to WSC Sports through Multi-Customer Management (MCM).
- GAM mobile custom native: Custom native ads built from the WSC Sports native template.
- GAM web custom format: Custom display ads built from the WSC Sports web template.
- GAM VAST format: VAST video ads served from GAM, with no WSC Sports creative template.
- GAM VAST macros: Dynamic parameters you add to VAST ad tags to pass language, consent, device, and placement data.
- GAM banner format: 320×50 display banner served from GAM, with no WSC Sports creative template.
- GAM ad campaigns: Campaign types, with JSON examples for the publish parameters used in Rules or Clipro.
Considerations
- WSC Sports creative templates:
- Required for GAM mobile custom native and GAM web custom format.
- Not used for GAM VAST format or GAM banner format.
- Creative requirements: See Ad specs for safe zones, file sizes, and creative limits.
- Single VAST only: The Experiences SDK serves one VAST wrapper per ad request. Playlist and VMAP wrappers aren't supported. See GAM VAST format.
- vpos is always mid-roll: The Experiences SDK sends
vpos=midrollon every ad request, including pre-roll and post-roll. Don't usevposto target or report by placement. See GAM VAST macros.
Updated 23 days ago
Did this page help you?
