Skip to main content
Version: v2

Google Ad Manager on live

With Google Ad Manager 360, Google decides which ads fill each break of your live stream. OptiView Ads announces the breaks to Google ahead of time, Google assembles the ads into a pod, and the pod plays when the break starts. Use this workflow when you sell your inventory through Google Ad Manager 360, and to reach platforms that need server-side ad insertion.

Google Ad Manager on live
Delivery modeServer-guided with Google Pod Serving (SGAI), server-side with Google DAI (SSAI), or both
Ad decisioningGoogle Ad Manager, ahead of the break
Break creationScheduled, punched, or detected from the ad markers in your stream
Your app needsThe OptiView Ads SDK; on Web also Google's IMA DAI SDK

Choose a delivery mode​

Delivery modeHow it worksUse it for
Google Pod Serving (SGAI)Google decisions the pod; the SDK inserts it into your untouched stream, guided by the Break Manifest.Web, mobile, and most connected TV apps. Required for the double box, L-shape, and overlay layouts.
Google DAI (SSAI)The Dolby Ads Proxy inserts the break cues into the stream Google reads; Google stitches the ads into the stream for viewers.Platforms where a client-side SDK is not an option, such as Roku and older connected TV devices.

One channel can serve both: the channel steers the delivery mode per device, and the SDK picks it up from the Break Manifest.

Before you start​

Schedule a break​

A Google break carries a vendor asset with vendor set to gam and vendorParameters.type set to pod. Google performs the decisioning, so the asset needs no URI. The same break serves both delivery modes.

curl -X POST 'https://us.ads.optiview.dolby.com/api/v1/channels/<channel-id>/breaks' \
  -u "$ADS_API_KEY:$ADS_API_SECRET" \
  -H 'Content-Type: application/json' \
  -H 'X-Org-ID: <org-id>' \
  -d '{
    "start": "2026-07-16T12:15:00.000Z",
    "duration": 60,
    "variant": {
      "format": "single",
      "assets": [
        {
          "type": "vendor",
          "vendor": "gam",
          "vendorParameters": { "type": "pod" },
          "assetParameters": {
            "description_url": "https://www.example.com/sports/live.html",
            "plcmt": "1"
          }
        }
      ]
    }
  }'
  • OptiView Ads announces the break to Google within the look-forward time before its start, so Google can decision the pod in time.
  • Create the break at least the decisioning margin before its start, or it is rejected.
  • The break starts in the PREPARING state, and becomes READY once Google has decisioned it. See How pod decisioning works.

Other ways to create the break​

  • Punch it live. Create the break without a start. Google decisions it ahead of time, and the break waits in the CUED state until you punch it.
  • Detect it. Add your stream as an origin and configure a marker rule whose template holds the Google vendor asset.

What your app needs​

The SDK reads the Google settings — your network code and the channel's Google asset key — from the channel's Break Manifest, and starts the Google stream session automatically when the session starts. You do not configure them in the app, so your app and the backend always agree on which Google stream the ads belong to.

PlatformRequirement
WebLoad Google's IMA DAI SDK on the page, before your application script (see below).
AndroidNothing extra: the SDK runtime includes the Google IMA SDK.
iOS and tvOSNothing extra: the runtime pod includes the Google IMA SDK. With Swift Package Manager, add the Google IMA packages as described in iOS.
React NativeNothing extra: the native SDKs include the Google IMA SDK.

On Web, add the IMA DAI loader to your page:

<script src="https://imasdk.googleapis.com/js/sdkloader/ima3_dai.js"></script>

If your channel also has VAST breaks, load ima3.js as well; the two scripts work side by side.

Server-side sessions​

When the channel steers a device to SSAI, the SDK requests the stitched stream from Google and loads it into your content player instead of your original stream URL. Your app keeps the same integration and starts the session with the same Break Manifest URL. On Web, use a content player adapter that exposes its video element, such as the HLS.js, Shaka, or native video adapter. In a server-side session, the SDK still plays the event-triggered breaks — pre-roll, pause, and post-roll — on the device.

Ad targeting parameters​

For Google, assetParameters are sent as Google ad tag parameters (adTagParameters). As a rule of thumb:

When the same key is set in both places, the value on the break wins. See Ad targeting parameters for the merge rules and platform examples.

Troubleshooting​

DiagnosticWhat it meansWhat to do
DA-GAM-CONFIG-RESOLVEDInformational: the Google stream session uses the network code and asset key in the diagnostic.Check that they match your Google stream.
DA-GAM-CONFIG-MISSINGThe Break Manifest carries Google breaks but no usable Google configuration.Check that the channel is connected to Google.
DA-GAM-SESSION-FAILEDThe Google stream session could not be started.On Web, load ima3_dai.js on the page. Otherwise, check the error message in the diagnostic.

Breaks that fail in the backend, for example because Google could not decision them in time, end up in the ERROR state and never reach the SDK. See Troubleshooting on the Google Pod Serving integration page for the possible reasons.

ResourceDescription
LiveLive channels: timebase, break creation, and delivery modes.
Google Ad ManagerOrganization-level prerequisites: network code and service account.
Google Pod Serving integrationGoogle Ad Manager setup, channel configuration, and pod breaks.
Google DAI integrationServer-side insertion: proxy, live stream, and channel configuration.
Ad targeting parametersPassing ad tag parameters to Google.
Google Ad Manager on VODThe same workflow for on-demand assets.