Enters Viewport vs GTM Visibility Trigger | Community
Skip to main content
GabrielBE2
GabrielBE2
Level 2
October 2, 2023
Solved

Enters Viewport vs GTM Visibility Trigger

  • October 2, 2023
  • 1 reply
  • 949 views

Hello,

I create this topic because I'm looking to migrate from GTM to Adobe Launch as a tag manager.

On GTM I was using the visibility trigger with CSS selector to send print tags (see screenshot).

I tried to reproduce the trigger in Launch with "Core - Enters Viewport" and the same parameters (cf. screenshot).

However, Adobe's detection seems much less precise, accurate and efficient (cf. video), as it detects visible elements when they aren't, whereas GTM is much more precise in this matter.

 

Does anyone experience this case?

Is there a way to get the same result as GTM? Maybe in a custom code?

For the record, I found a Matomo documentation that tried to reproduce GTM visibility: https://github.com/matomo-org/tag-manager/blob/5.x-dev/Template/Trigger/ElementVisibilityTrigger.web.js

Thank you in advance!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by GabrielBE2

Also, in GTM I can have access to the element that is visible and target with the Selector CSS through the embed variable "Click Element" (cf. screenshot), is there such a variable for the Enters Viewport?

 

Thank you in advance!

1 reply

GabrielBE2
GabrielBE2AuthorAccepted solution
Level 2
October 2, 2023

Also, in GTM I can have access to the element that is visible and target with the Selector CSS through the embed variable "Click Element" (cf. screenshot), is there such a variable for the Enters Viewport?

 

Thank you in advance!

    Terms & ConditionsAccessibility statement

    Loading footer...