CSS Selector for Enters Viewport

[Herder]

Hello Adobe Experts,

I hope everyone is doing well.

I would like to get your insights regarding the usage of Enters Viewport. Currently, it is working perfectly for my implementation, but it turns out that when I go back to the previous CTAs, the rule is no longer firing.

Steps:
I clicked the CTA 1 and the rule with "Enters Viewport" fires

I clicked the CTA 2 and the rule with "Enters Viewport" fires

I go back to the CTA 1, but the rule is no longer firing.

Sample web appearance:

Sample Rule setup:

Question:

From this release note, it seems like enter viewport would only trigger once time per page, but I am just wondering if someone has a way to retrigger the rule when I go back to CTA 1?

https://experienceleague.adobe.com/en/docs/experience-platform/tags/extensions/client/core/release-n...

Thank you in advance.

[EurosIMS]

Hi @Herder,

You say 'click the CTAs', so is there a reason why you are using Enters Viewport instead of the Click/Mousedown events? 

[Herder]

Hello @EurosIMS,

Thanks for your reply.

Basically, the page is a single page application (SPA), so every time the user clicks the CTA, the content of the page is changing which should be considered as pageView.

Currently, the Enter Viewports gave us 1 pageview across all views, but if we go back to the previously selected CTA, the rule is no longer firing, but thank you for the Click/Mousedown events, but it seems like that won't work for us, because when the user tries to spam the CTA, click events will gave us multiple beacons instead of 1, and using max frequency to limit the results won't work on the page.

Thank you for your insights, appreciate it.

[Jennifer_Dungan]

You're right, the Enters Viewport should trigger on each use if this is an SPA... However, I don't have an SPA to test on at the moment... would you be willing to share a URL to your site to see if I can spot anything? (you can send via a private message so as to not share it publicly) 

[yuhuisg]

@Herder , I appreciate that you want to track the page view when the content (red box in your diagram) is shown visibly to the user. However, in my experience, the Enters Viewport is not a reliable method to perform such tracking. The reason is that you're really dealing with HTML.

I think what is happening in your website is like this: When I click CTA 1, then content 1's HTML is loaded and the browser recognises that HTML. Then when I click CTA 2, content 2's HTML is loaded and the browser recognises that HTML. When I click CTA 1, content 1's HTML is not loaded again, so there's nothing for the browser to recognise, and so the Enters Viewport event does not get triggered in Launch. I could be wrong about this process, but to me, that sounds the most plausible.

Assuming that you can safely assume that every CTA click always results in the content being refreshed, then you can assume that 1 click = 1 page view. In that case, I think what @EurosIMS would be the most suitable: track your page view with the click.

Having said that, if you also notice that the browser URL changes when you click a CTA, then that means your website is modifying the browser's history (in addition to updating the content). In that case, you can try using the History Change event to detect the browser's history update and track your page view with that.

Hope the above helps somehow!

[Jennifer_Dungan]

This is why I wanted to see the website.. is the URL changing, what is happening in the HTML, etc.

Normally, in an SPA, content would be unloaded and new content loaded, but it's not always the case... you are right, it might just be hidden, and thus not triggered the viewport.

Some SPAs don't change the URL (those sites should be abolished honestly, I have had to deal with a few of them, and they suck).

Sometimes triggering on the click means the new page's info hasn't yet loaded and can cause tracking issues... in that case, you can trigger a rule that has a delay, then that rule calls another rule to trigger the tracking (so that the content should be available).

Sometimes you have to get creative with your solutions.

[Herder]

Hello @Jennifer_Dungan and @yuhuisg,

Thank you for your help.

We dropped the usage of Enter Viewports due to its limitation. Instead, we used the Direct Call event. Appreciate your insights and you're all awesome.

Have a great day.

[Jennifer_Dungan]

I'm so glad you found a solution!