Hey @harry w​ 👋

One additional quirk about the 'update' method is that we de-dupe calls that don't actually update user data in a 60-second window. So if no user data is being updated and customers just send in Intercom('update') then those will only register once every 60 seconds. Hope this helps 🙌

Thank you Lisa I appreciate the help! I do think this might have been tangentially at play.

I think the root issue was the History Change event may fire occasionally before the URL has actually changed in my Single Page Application framework. If this happens and I call Intercom('update') then the URL hasn't changed the update event gets de-duped. My SPA framework had another event `gatsby-route-change` I could use as a GTM trigger. I believe using this is leading to more consistent Intercom('update') firing. I still feel there might be an undocumented rate limit on how often you can trigger Intercom('update') in a short period of time, that being said, any normal user won't rapidly click around pages. They'll dwell on a page for 5 - 10+ seconds I would imagine before switching pages.