Add TTL Validation for Suppressing Expired Ads

[pm-azhar-mulla]

Type of issue

Feature

Description

Currently, the ttl (Time-to-Live) property is not utilized when rendering an ad. This results in ads being displayed even after they are technically expired. By leveraging the ttl property, we can determine whether an ad has expired and suppress its rendering if needed.

Proposed Enhancement:

Introduce functionality to validate the ttl property before rendering an ad. If the ad has exceeded its ttl value and the suppressStaleRender property is enabled, the system should suppress the rendering of the expired ad. This would function similarly to the adId validation mechanism.

Publishers can enable the suppressStaleRender property to prevent expired ads from being displayed, ensuring a better user experience and avoiding potential compliance or quality issues.

[patmmccann]

Stale render has a different meaning; I believe it suppresses ads from rendering twice

[pm-azhar-mulla]

@patmmccann
If TTL has reached for the bid, we can consider it as stale.
if not, Can we add a new flag to perform ad-rendering on basis of valid TTL.

[patmmccann]

yes, i would suggest a new flag. I think stale bids are poorly named, as one would naturally think they are bids past their shelf life, but for whatever reason they indeed have a different definition here. Perhaps we could improve the verbiage in the messages.

[patmmccann]

@pm-azhar-mulla is this a dupe of #11270 ?

[patmmccann]

I propose suppressExpiredRender ; marking ready for dev and closing the dupe

we'll emit an event EXPIRED_RENDER similer to STALE_RENDER that publishers can listen to and either render a different ad, call for a new auction, or call the ad server again with the targeting for this bid removed depending on their preference