By integrating Fullstory with your OneTrust cookie banner, you can control data capture in Fullstory depending on the provided consent of users. This allows your organization to be in compliance with both your internal privacy policies as well as consent requirements for global privacy legislation such as the CCPA, GDPR, LGPD, etc.

Depending on the consent model you desire, Fullstory is fully configurable to be turned on, turned off, or take in consent values to expand capture of certain fields only in the case that the user has provided consent.


If you have enabled Cookie Auto-Blocking with OneTrust, the Fullstory javascript should be blocked automatically. Please test and confirm.

If Cookie Auto-Blocking is not enabled, the configuration will depend on the tag manager that you use.

Enabling Cookie Auto-Blocking in your OneTrust account is the easiest method. This will auto-block all key tracking technologies that are not categorized as strictly necessary until the user has provided consent. OneTrust has defined a list and will auto-block scripts from loading based on how you have categorized your cookies and your chosen consent model(s).

If you find that Cookie Auto-Blocking is not the best setup for your domain we have details below on how the same can be achieved using tag managers or using the Fullstory JavaScript API.

Tag Managers

If you have Fullstory deployed through a tag manager such as Google Tag Manager, you can simply add the OneTrust cookie category trigger to the HTML snippet. This will control Fullstory firing only when the user has provided consent.

Here is the guide from OneTrust on how to set this up within Tag manager: 


Non-tag Manager Deployment

If Fullstory is deployed through Segment, directly in the Header or through a mobile app, you may want to use the Fullstory API to control turning Fullstory on/off:

Need to get in touch with us?

The Fullstory Team awaits your every question.

Ask the Community Technical Support