Skip to main content
Answered

Create GTM tag for Logged In users

A

Hello!!

We have been trying to create Intercom GTM tags for logged out and logged in users.

  • For logged out users it was easy enough as we’ve followed the Intercom documentation and all good.
  • However, when it comes to Intercom Logged In users tag, we’ve followed this documentation but are not too sure of that we should add in the variables (please see picture below) for it to track the correct values for each user.
  • Is there some additional stept that’s not in the documentation that we should follow? Any data layer we should implement? Just to be sure we’re not missing anything.

We’d be super gratful for any insight on how exactly this tag implementation should be done.

Thanks a million!

Best answer by Jacques Reynolds

Hey ​@anaivicuo 👋 Jacques here from Intercom Support. I hope all is well today!

To create Intercom GTM tags for logged-in users, ensure you include the user's details in the 'Install' method when the website loads. If users log in later, trigger the same tag again with the 'Update' method, including the user's details.

For identifying logged-in users, you should provide variables for 'User ID' or 'User Email' in the 'Data attributes' section. Avoid entering specific user IDs or email addresses directly to prevent incorrect user identification.

Additionally, you can include variables for standard attributes like the user's name, phone number, and a unique user hash if using identity verification.

Hope this helps!

View original
    Did this topic help you find an answer to your question?

    4 replies

    Jacques Reynolds
    Intercom Team
    Forum|alt.badge.img+4

    Hey ​@anaivicuo 👋 Jacques here from Intercom Support. I hope all is well today!

    To create Intercom GTM tags for logged-in users, ensure you include the user's details in the 'Install' method when the website loads. If users log in later, trigger the same tag again with the 'Update' method, including the user's details.

    For identifying logged-in users, you should provide variables for 'User ID' or 'User Email' in the 'Data attributes' section. Avoid entering specific user IDs or email addresses directly to prevent incorrect user identification.

    Additionally, you can include variables for standard attributes like the user's name, phone number, and a unique user hash if using identity verification.

    Hope this helps!

    Jacques Reynolds
    A
    • anaivicuo
    • Author
    • New Participant
    • 2 replies
    • March 20, 2025

    Thanks so much ​@Jacques Reynolds!

     

    Sorry if I wasn’t clear! If I want to identify logged-in users, what are the variables that I should add to retrieve the user’s information? And what changes should I apply to the data layer to give the brief to our developer? Could you give me an example, please?

     

    Thanks so much!

    A
    • anaivicuo
    • Author
    • New Participant
    • 2 replies
    • March 24, 2025

    Hey ​@Jacques Reynolds! Just following up on my question above!

     

    If I want to identify logged-in users, what are the variables that I should add to retrieve the user’s information? And what changes should I apply to the data layer to give the brief to our developer? Could you give me an example, please?

     

    Thanks so much!

    catjack
    • catjack
    • New Participant
    • 1 reply
    • April 13, 2025

    Thanks for the message! You're on the right track. For logged-in users, you’ll typically need to pass user-specific data (like user ID, email, or name) through the data layer so GTM can push that into Intercom properly (More Information). If the Intercom docs don’t cover that part clearly, you may need to work with your dev team to ensure those variables are available in the data layer. Happy to take a look at the variables or setup if you want to share more details!

    Reply


    Most helpful members this week

    Terms & ConditionsCookie settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings