Loading custom integrations after the initial load

[theosamaperspective]

Hello,

is there a way we can load the custom integrations after we have already called load on AnalyticsBrowser? We want to anonymously track the users when they first load the page. This is where a cookie banner is shown. Once the user accepts, we want to load the 3rd party scripts like GTM etc.. Now the first load tracking is also done through analytics.js. Is there a way we can have this? We currently have this working with analytics.js core library.

Thanks!

[silesky]

Hey, I assume you looked at using Segment consent management? We have wrappers for OneTrust and TrustArc, and there’s a generic library in packages/consent/consent-tools.

Unfortunately, while we can block all events to specific destinations, analytics.js doesn’t support complete lazy initialization of individual destinations — it’s all or nothing when it comes to loading the actual scripts. If you’re rolling your own solution with our tooling, it sounds the closest thing we have to that is support for opt-in consent — which will only load Segment and any destinations once a consent decision is made. All events will be queued, but not sent until then.