Gracefully fail on window.dataLayer name conflict

[Peripheral1994]

I'm updating the body of this PR to do some testing, don't mind me - Carlos

[f2prateek]

I think we can do this.debug - https://github.com/segment-integrations/analytics.js-integration-bronto/blob/391bf8bbbedb7d63e1104fc4ac8821daa00a766d/lib/index.js#L37

[f2prateek]

I wonder if GTM allows us to use something other than dataLayer - that would allow us to keep the integration running even if there is a conflict.

[Peripheral1994]

I believe that we should simply allow the data layer's name to be passed in as a flag here for the &l args instead and default to dataLayer. Adding to the ticket so we can evaluate the best way to support this.

analytics.js-integration-google-tag-manager/lib/index.js

Lines 21 to 22 in f661ed6

	.tag('no-env', '<script src="//www.googletagmanager.com/gtm.js?id={{ containerId }}&l=dataLayer">')
	.tag('with-env', '<script src="//www.googletagmanager.com/gtm.js?id={{ containerId }}&l=dataLayer&gtm_preview={{ environment }}">');

[Peripheral1994]

We SHOULD still keep this no-op if the chosen data layer name is taken.

[SegmentDestinationsBot]

Hi @Peripheral1994, as part of the monorepo migration, this issue has been moved to new issue. Our engineers have been notified and will prioritize and work on it ASAP. Thank you!

For more information, see README.md.