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 session. 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.
Hourly delivery
The Ads Session Feed is delivered hourly. Every hour, Conviva writes one set of files covering the ad sessions active in that hour.
Each hourly file carries every ad session active in that hour, with that session's totals up to the end of the hour. A short pre-roll usually appears in exactly one file. An ad session that spans an hour boundary appears in more than one, once per active hour, and the later row supersedes the earlier one. Before you aggregate across hours you must deduplicate.
Deduplicate before you aggregate. Partition by AdSessionID and StartTimeMs, order by dt descending, and keep the first row. Skipping this step double-counts every ad session that crossed an hour boundary. The SQL is in Build your first pipeline, step 4.
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 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:
Amazon S3 bucket (and managing the AWS role for KMS-encrypted uploads)