Understanding MediaTailor skipped ad reasons - AWS Elemental MediaTailor

Understanding MediaTailor skipped ad reasons

AWS Elemental MediaTailor publishes a list of ads that were skipped in the FILLED_AVAIL event log message from the MediaTailor/AdDecisionServerInteractions log group. The reasons why each ad was not inserted are also provided and can be any one of the reasons that the following table describes.

Reason Description
NEW_CREATIVE The ad has not been transcoded yet.
PROFILE_NOT_FOUND The MediaConvert transcode profile associated with this session's configuration does not exist and the ad cannot be prepared for insertion.
TRANSCODE_ERROR The ad transcode is in an error state.
TRANSCODE_IN_PROGRESS The ad transcode is in progress.
INTERNAL_ERROR There has been an error handling the ad and it cannot be inserted.
AVAIL_DURATION_EXCEEDED The ad does not fit within the remaining duration of the ad break.
LEFTOVER_AVAIL_EXCEEDED_THRESHOLD The cumulative duration of all ads that could have been inserted does not meet the personalization threshold configured for this session, so this ad will not be inserted.

You can use the following query to analyze skipped ads and their reasons:

fields @timestamp, avail.availId, skippedAds.0.skippedReason, skippedAds.0.creativeUniqueId | filter eventType = "FILLED_AVAIL" and ispresent(skippedAds.0.skippedReason) | sort @timestamp desc

This information can help you troubleshoot issues with ad insertion and understand why certain ads are not being displayed in your streams.

MediaTailor also provides CloudWatch metrics for tracking the frequency of different skip reasons. For more information about these metrics, see Monitoring with CloudWatch metrics.