**Sample App:** Experience the ITG Library in Action.

1. Goal & Context

What we want

• Use AWS MediaTailor for SSAI (server-side ad insertion).
• Use ITG for client-side interactive overlays (Flexi creatives) on top of video.
• Drive ITG overlays using MediaTailor tracking data only (no Datazoom, no extra analytics SDK).

What is assumed

• ITG SDK is already integrated with your player:
  • There is an OverlayViewController in use.
• You have a MediaTailor config URL (from your backend or directly from AWS).

2. High-Level MediaTailor Flow

From ITG’s perspective, the MediaTailor integration is just three stages:

1. Fetch a config from your backend / MediaTailor:
   • Input: configUrl (your “content URL”).
   • Output: manifestUrl for playback, trackingUrl for ad info.
2. Start playback with the manifestUrl:
   • The player plays the SSAI stream (content + stitched server-side ads).
3. Poll the tracking endpoint:
   • Regularly query trackingUrl to discover non-linear ad avails.
   • For each new non-linear ad, fetch its static resource (Flexi JSON / HTML).
   • Pass that Flexi data into ITG to render overlays at the right time.

All details (coroutines, repositories, DTOs) are just an implementation of this simple loop.

3. Step 1 – Fetch MediaTailor Config

What happens

• Your app calls a config endpoint (your backend or AWS) with a contentUrl.
• The response contains at least:
  • manifestUrl – the HLS URL used by the player.
  • trackingUrl – URL for MediaTailor tracking / ad avails.

Responsibilities