It is a requirement from our trading team to measure the real impressions for DY injected content. This means separate impression events must be fired once a piece of content appears in the viewport.
The GTM element visibility trigger appears to be just what we need:
- It can listen to changes in the DOM, so DY async content will still be picked up
- It can be set to fire only after some content has been visible in the viewport for x milliseconds, which will mean that we can minimise the impact of double counting content for 'replace' campaigns.
This all sounds great, my only concerns are around performance. Has anyone on this forum used this trigger before? Are there any performance issues with DY injected content?
Visibility trigger: https://support.google.com/tagmanager/answer/7679410?hl=en
Suggested implementation (with products instead of content): https://www.simoahava.com/analytics/element-visibility-trigger-google-tag-manager/
Please sign in to leave a comment.