Ads Session Feed: Start Here

Orientation for data analysts building a pipeline on the Conviva Connect Ads Session Feed: what it is, how the daily and hourly feeds behave, what one row means, the schema, metric SQL, and delivery setup.

Updated 2026-10-28 ads-ssd, ad feed, ads session feed, ssd, conviva connect

The Ads Session Feed is a session-level export of your Conviva Ads data. Each row describes one ad play or attempted play, with the ad, advertiser, device, network, and geo metadata alongside the experience metrics for that ad play. It is built for analysts who want to land Conviva ad data in a warehouse and build their own reporting, diagnostics, and models on top of it.

Daily and hourly delivery

The Ads Session Feed is delivered on a daily or an hourly schedule. Your Conviva Representative configures the schedule for each account. In both, each row describes one ad play, keyed on AdSessionID plus StartTimeMs; the hourly feed repeats an ad play once for each hour it is active.

  • Hourly: every hour, Conviva writes one set of files covering the ad plays active in that hour, with each play's totals up to the end of the hour. An ad play that spans an hour boundary repeats across files, so you must deduplicate before you aggregate across hours. Each hour typically arrives 4 to 6 hours after it ends, and the exact timing varies with traffic volume.

  • Daily: one set of files per day, with one row per ad play.

In the hourly feed, each file carries every ad play active in that hour. A short pre-roll usually appears in exactly one file. An ad play that starts at 09:59 and ends at 10:01 appears in both the 09:00 and the 10:00 files: its EndedStatus is 0 (not ended) in the first and non-zero (ended) in the second. A later hourly file never re-delivers or restates an earlier hour, so the latest row for an ad play carries its final totals.

Deduplicate the hourly feed before you aggregate. Partition by AdSessionID and StartTimeMs, order by dt descending, and keep the first row. Skipping this step double-counts every ad play that crossed an hour boundary. The SQL is in Build your first pipeline, step 4.

One row per ad play

AdSessionID identifies an ad session, which is a group of ad plays, not a single ad. Every ad play in the group carries the same AdSessionID, and StartTimeMs tells the plays apart. One AdSessionID can repeat on many rows within one content session, sometimes more than 100 in a day.

The unique key for one ad play is AdSessionID plus StartTimeMs. ContentSessionID is not part of the key. Never count or deduplicate on AdSessionID alone, because that collapses distinct ad plays into one. The schema page covers the identity fields in detail.

Feeds per account and switching to hourly

Ads feeds are configured per account (per c3 account). The folder names for each account under your delivery path are flexible, and you agree them with your Conviva Representative when the feed is set up.

To move an account from daily to hourly delivery, ask your Conviva Representative. You name the date to enable hourly delivery and the date to disable daily delivery. Both feeds can run in parallel until you confirm the cutover, so you can check your hourly pipeline against the daily one first.

Traffic rules are not currently supported for the Ads Session Feed. If an account receives its ad traffic only from child accounts through traffic rules, it cannot be the source of an Ads feed today. Set up a feed on each child account instead, and confirm the setup with your Conviva Representative.

Conviva Connect vs legacy Ads SSD

Conviva Connect is the current product: a new schema and a new delivery pipeline, and all new customers onboard to the Connect schema. Legacy Ads SSD is still maintained for existing legacy customers, but it keeps the legacy schema, so the field names and layout differ between the two.

The quickest way to tell which one you receive is the field naming. Connect delivers PascalCase names such as AdSessionID and StartTimeMs. Legacy delivers lowercase names with underscores, such as conviva_ad_session_id.

If you are onboarding today, use the Conviva Connect schema described on these pages. If you already receive legacy Ads SSD files and want to compare or migrate, see SSD Schema Comparison: Legacy vs Connect for the field-by-field mapping. The legacy reference remains at Ads Session Source Data, and its field table is at SSD Field Definitions.

Joining ads to video sessions

Every row carries both an AdSessionID and a ContentSessionID. The content session ID links the ad play back to its parent content session: it is the ConvivaSessionID of the video session the ad played inside, so it is the join key from the Ads Session Feed back to the Video Session Feed. Join the two feeds to measure ad experience against content outcomes, for example whether ad rebuffering changes content completion.

Next steps

Formats and delivery destinations

Choose the output file format: CSV, Avro, or Parquet. All three are available on the Ads feed, and the format is independent of the delivery schedule. See Get the Conviva Data Feed for the format and file-naming details.

Conviva Connect delivers the files to one of three destinations: