- Updates and Announcements
- Introduction
- Purchase Guide
- Console Guide
- Practical Application
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Channel Management APIs
- CreateStreamPackageChannelEndpoint
- BindNewLVBDomainWithChannel
- CreateStreamPackageChannel
- DeleteStreamPackageChannelEndpoints
- DeleteStreamPackageChannels
- DescribeStreamPackageChannel
- DescribeStreamPackageChannels
- ModifyStreamPackageChannel
- ModifyStreamPackageChannelEndpoint
- ModifyStreamPackageChannelInputAuthInfo
- UnbindCdnDomainWithChannel
- HarvestJob Management APIs
- Data Types
- Error Codes
- StreamPackage Policy
- Updates and Announcements
- Introduction
- Purchase Guide
- Console Guide
- Practical Application
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Channel Management APIs
- CreateStreamPackageChannelEndpoint
- BindNewLVBDomainWithChannel
- CreateStreamPackageChannel
- DeleteStreamPackageChannelEndpoints
- DeleteStreamPackageChannels
- DescribeStreamPackageChannel
- DescribeStreamPackageChannels
- ModifyStreamPackageChannel
- ModifyStreamPackageChannelEndpoint
- ModifyStreamPackageChannelInputAuthInfo
- UnbindCdnDomainWithChannel
- HarvestJob Management APIs
- Data Types
- Error Codes
- StreamPackage Policy
StreamPackage SSAI service uses server-side reporting. When the player requests the ad URL in the manifest, the SSAI service will directly report the ad usage to the ad tracking URL.
Ad URL format in HLS:
GET <StreamPackageURL>/v1/ssai/segment/<uniq_id>/<session_id>/<asset_id>/<seq_num>
When the player requests playback through the ad segment URL (/v1/ssai/segment path), StreamPackage will send the tracking data to the ad server through the ad tracking URL, and at the same time, redirect to obtain the actual *.ts ad segment and distribute it to the player.
Yes
No
Was this page helpful?