GTM Template for Browser SDK 2.0 ?

Hi @Rune Andersen. I’ve a feeling this could just be the documentation in the GTM tag template summary hasn’t been updated. You’ll see it states this…

However, some weeks ago, the name of the tag template was changed to what you see now in GTM (“Amplitude Analytics Browser SDK”). I updated the template in our GTM and am pretty convinced it’s using the Browser SDK 2.0 as values set in the Library property within Amplitude switched from “amplitude-js-gtm” to “amplitude-ts-gtm”….the giveaway being “ts” as the new Browser SDK I’m sure uses Typescript while the legacy one used Javascript.

Dan.

P.S. DET is default off in Browser SDK 2.0 so you’ll need to switch it on in your initialisation tag if you wish to use it.

Thanks @dangrainger 
I looked into it and the template i use have been named “amplitude-ts-gtm” since we started in April  2023 with version 3.1.3 - and that was before Browser SDK 2.0

And in the initialisation tag there are no config option for Default Tracking. 
https://www.docs.developers.amplitude.com/data/sdks/browser-2/#configuration

So i’m not sure the GTM Template are update yet,
But some input from either @Esther Trapadoux  or @Ye Rin Cha on this question would be appreciated.

Yeah, I agree we need some clarity. Our traffic has been coming through on amplitude-ts-gtm/3.3.0 since May 24th.

Just found this doc: https://www.docs.developers.amplitude.com/data/sources/google-tag-manager/. If it’s up to date it suggests the GTM template tag is still on the Amplitude Marketing Analytics SDK.

I have seen that. 
And also if you see under Client-side, they explicit note that Custom HTML is not recommended.
 

I dropped a line to support, seems the GTM template is to be upgraded to Browser SDK 2.0 pretty imminently…
 

Spotted this morning that Browser SDK 2.0 is being offered as an update in GTM to the Amplitude tag template :-)

Thanks. I have tried it out and it seems to work.
Also nice with better “in-template” documentation and links to full documentation.
Would still wish there where a easy way to add additional properties to Session Start, and other [Amplitude] events.