Well, try putting a simple `console.log` statement (or alert() for something more obvious) in that anonymous function and you'll notice that it isn't really called.

I basically updated `onDocHeightChange` to be `onLocationChange` which would check for changes to `location.href` every half a second and reset internal state, same as `onDocHeightChange` did.

Hi Kriya, thank you for the comment! This is very interesting to read. Though I'm not totally sure what to make of it, because it seems to work fine as is on the SPA sites I've tested it on, and when I remove the custom HTML tag from step 7, it no longer works. Do you have any suggestions for how to make this a more reliable scroll tracking script for SPA pages?

Those three statements are a copy of ScrollTracker class' `destroy` method from the plugin (which is never actually used in the plugin itself anyway).

To test it yourself, try removing that Custom HTML tag from step 7 and navigate around your site/app. The events will still be triggered for any page that has a different height than the previous one as the plugin has a method, `onDocHeightChange`, that checks for changes in the height of the document every half second, resetting internal state if it does.

However, that internal logic will not work for any site or app that has a fixed height for pages, so I've updated it to work on history change.

Sorry, good question but I don't know the answer as I didn't create the script myself. I would just test it out and see how it goes.

Thanks for letting me know! On my test site, it seems to work even on second page views, but I will update the post to note that it might not always work as expected.

It seems that the tag fires on A (first time), B, & C as expected but fails to fire when the user returns to page A for the 2nd time.

Awesome, I love to hear this 🙂 I was dealing with the same issue, so I totally get it...