Hey @Rune Andersen ! Happy to help! I believe the Browser SDK is the preferred method to use with the GTM Template. What are you using for a trigger to fire the Tag Template?

similar issue. 

trigger is all pages

@r0bbieWa11ace 
Trigger for the Init event is a cookie-consent-accepted trigger, but similar to a “All Pages” trigger.

For the other events it’s different but normal GTM “Custom Event” triggers.
I had to move the setup to a EU account, but it’s the same issue.
The event are not recognized as either HTTP API or Browser SDK. And the GTM option are stuck as listening for events.

@Rune Andersen : Another customer has raised this issue and we are working to resolve. Can you send a ticket to support within the Amplitude UI (Click the Icon on the Bottom Right to open up the options)

In the short-term if you need some data, you can leverage the Legacy Tag Template. Please let me know if you experience the same outcome with the Legacy Template.

-Robbie

@Rune Andersen : Have you set up a tag to initiate the SDK? If you haven’t yet, create a new Tag, add your API Key, change event type to “init” and add a trigger to enable on all pages. 

This was a change in the newest version of the tag template to allow you to initiate the tag based on user consent requirements. If a user declines to be tracked, then the sdk will not initialize and no data will be collected. If they accept cookies OR do not set their consent to block, then it will allow your data to be collected and sent to amplitude.

Let me know if this resolves the issue.

Best,

Robbie

@r0bbieWa11ace 
To answer both your replies.
Yes i have a Init tag, firing on all pages before any other Amplitude event tags.

I tried to add the legacy tag and it instantly creates the “Google Tag Manager” source and is auto-named.

Is this actual an issue from a data-collection perspective ?
What do I miss by the source being  “unknown” ?. Are any functionality broken or is it primarily a visual issue ?

I’m still on a Trial account while the client im working for decides what plan to go with.
So it does not seem like im able to create a support case. 

@Rune Andersen : If you are wanting to track the specific GTM Container it will have to be hardcoded. This has been recommendation I have been providing customers so if they have multiple GTM containers to help give yo this level of validation within the UI.

FYI @r0bbieWa11ace i don’t consider this bug fixed.
The new GTM template is still not recognized as a valid source in the Amplitude Data UI. 

FYI @r0bbieWa11ace it’s now fixed and events are automatic detected as “amplitude-js-gtm” 

Thanks @Rune Andersen ! I appreciate the follow up. Apologies on my end. I did hear that engineering was aware of this issue and was actively working on it last week. Glad to see the change was successfully released!