Wait for TCF API

The Wait for TCF API feature ensures the player will wait for an event triggered by your Consent Management Platform (CMP) before firing any ad calls. Specifically, the player will delay making an ad request until it receives confirmation of user consent.

This functionality maintains compliance with data protection and privacy regulations and respects user preferences regarding data usage and advertising.

These are the default timeouts the player uses when this option is enabled. The following will be used by the player to wait before it fires an ad request and is important information to know especially if you utilize autoplay with pre-rolls.

• When enabled, once the player initialises, it will wait for 500ms for a response from the TCF API that your CMP provides. Always make sure to load your CMP as soon as possible. In most implementations, CMP are front-loaded on a page and the player does not need to wait at all.
• Once a user gets a prompt for consent, the player will wait for 4000ms for a response from the user before it starts firing an ad request. If the user does not interact with the CMP in these 4000ms, the player continues its functionality without sending any ad requests.
• As soon as a user either accepts or denies consent, the player fires an ad request with the appropriate consent string.