Engage can be used to display a wall overlay on top of a video player in order to restrict access to video content.

The actual video playback restriction is entirely handled on your side, within your player implementation.

On the Poool side, an Engage element is displayed as an overlay on top of the player and can be triggered through an autocreate linked to a custom filter.

We recommend using a dedicated filter for this use case. This allows you to isolate your video-gating logic from the rest of your Engage campaigns while maintaining centralized management from the Dashboard (content updates, targeting, activation/deactivation, A/B testing, etc.).

How It Works

The integration relies on two components:

• Your video player, which handles playback and access restrictions.
• An Engage element displayed as an overlay on top of the player.

The Engage element can be triggered by a player event (click, video start, end of ad, etc.) using the autocreate method associated with your custom filter.

Once displayed, the Engage element can serve as a trigger for applying the access restriction rules implemented on your side.

Scenario 1: Video → Wall Displayed After a Delay

In this scenario, the user watches the advertisement and then starts the video. The wall is displayed after a predefined delay.

Using a Delay Configured in Engage

Video players expose various events, such as video clicks or end of ad.

You can use the event that best matches your desired behavior to trigger an autocreate associated with your custom filter.

Once the element has been triggered, you can configure a display delay directly in the Engage Dashboard (for example, 5 seconds).

When the delay is reached, the element is displayed as an overlay on top of the player and the Engage seen event is triggered.

Your code can then listen for this event and pause or block video playback accordingly.

Benefits

This approach keeps all timing logic within Engage.

As a result, business teams can adjust the delay directly from the Dashboard without requiring any technical intervention.

Scenario 2: Immediate Paywall

In this scenario, access to the video is restricted immediately.

Two approaches are available.

Option A: Block Playback on Click

When a user clicks on the video:

• The Engage element is triggered.
• Video playback is blocked by your code.

The video never starts and remains inaccessible until the required action has been completed.

Option B: Use a Fake Video

Instead of displaying the actual player, you can display a thumbnail or a "fake video" placeholder.

The Engage element is then displayed on top of this placeholder.

Two variants are possible:

• The Engage element is triggered when the user clicks on the placeholder.
• The Engage element is displayed immediately when the page loads.

In both cases, the actual video remains inaccessible in the background until the user completes the required action.

Note

In all of the scenarios described above, the video access restriction logic must be implemented on your side.

Poool Engage is responsible for displaying the wall and providing the associated events, while the player behavior (playback, pause, blocking, resuming, etc.) remains entirely under your control.

Updated on: 12/06/2026