Send custom tracking using Poool Access events
In Poool Access, custom tracking is based on the use of events exposed by the solution.
When the SDK loads and users interact with the paywall (paywall display, clicks, sign-ups, etc.), Poool automatically triggers events containing data related to each action.
Principle & How It Works
You can listen to these events from your integration in order to retrieve information related to the paywall and user actions and send custom tracking data to your analytics tools, dataLayer, CRM, etc. Poool automatically detects user interactions and lets you leverage this data according to your needs.
From your integration, you can subscribe to events using the .on() method.
This allows you to:
- detect paywall and user actions in real time
- retrieve data associated with these actions
- send custom tracking based on your requirements
Event Arguments
Each event returns an argument object containing data related to the triggered action.
These arguments are not the same for every event: they vary depending on the event type.
For example:
- a click event returns information related to the clicked element
- a registration event returns user-related data
- a display event returns contextual information (page, paywall, etc.)
Each event therefore has its own argument structure, which you can use to adapt your tracking logic.
Example: Tracking a Subscribe Button Click
access.on('subscribeClick', (event) => {
console.log('User clicked subscribe', event)
// Google Analytics (GA4) example
gtag('event', 'subscribe_click', {
label: event.button,
url: event.url
})
// Google Tag Manager (dataLayer) example
window.dataLayer = window.dataLayer || []
window.dataLayer.push({
event: 'poool_subscribe_click',
button: event.button,
url: event.url
})
})
The subscribeClick event is triggered when a user clicks a subscription button in the paywall.
It returns an event object containing information about the clicked button (e.g. label, URL).
Full List of Available Events
Here are the main events available in Poool Access:
- identity-available: triggered when a user lands on a page with the Poool tag (user identity available)
- paywall-seen: triggered when the paywall becomes visible in the browser
- ready: when the paywall is loaded and displayed on the page
- release: when the current article is unlocked
- click: click on a paywall button
- register: newsletter signup via widget or Discovery Pass
- formSubmit: form submission via a widget
- error: API error (triggers the configured default action)
For the full list of available events and their data structure, refer to the official documentation:
https://www.poool.dev/en/docs/access/javascript/events
Best Practices
- Make sure your tracking script is loaded before listening to events
- Test your events in a staging environment
- Use
console.logto validate received data before sending it to analytics tools
Updated on: 27/04/2026
Thank you!
