This isn't related to Tessitura Analytics but I'm hoping someone may have insight regardless...
We're preparing to launch cookie consent via OneTrust for compliance with privacy law and have hit a big hurdle re TNEW.
We host TNEW (v7) on a subdomain of our site. For a long time we've used Google Tag Manager to load Google Analytics (now v4) onto our sites; TNEW and our main marketing domain share a property ID. We've built OneTrust to load via GTM as well -- it seemed the logical thing to do, since all our other tags are inside that container and OneTrust can fire the appropriate trigger to match a user's cookie preferences.
With the last TNEW release we started noticing a conflict between our GA property ID loaded via the TNEW admin interface and the (same) property ID loaded via GTM. Using both blew up our purchase & revenue tracking, so we started suppressing the GTM version of GA4 on TNEW pages. Revenue tracking returned and all was well...until we realized that doing so would break the link between OneTrust and GA4. If OneTrust sets consent triggers via GTM and GA4 loads outside of GTM, they can't talk to one another.
We feel stuck between tracking purchases and revenue and respecting our users' privacy choices. Has anyone run into this same issue and solved it?
(Cross-posted to Marketing forum as well.)