We load an internal analytics script only after a user action, so it was not detected during the scan. How can I make sure OptinStack governs it now?
Add the Tracker manually to your project inventory or mark the resource with data-optinstack-categories="analytics". Unknown, untagged resources cannot be universally blocked until they are scanned, classified, manually added, or explicitly tagged.
After updating the inventory, publish the project and test in a fresh private session. You can listen for script-blocked and script-unblocked events while validating the result.
Documentation: Install and manual category tagging and Blocking events.