There are several reason why Launch could be reporting numbers: Can you narrow it by browser type? This could be related to a specific browserIt could also be ad blockers allowing Google to fire but not Launch to fire. If possible, check to see if your numbers correspond to the same in Adobe Analytics. If you have the client ID available as a custom dimension, try to cross-reference it between the two properties and see if you can narrow down the type of user who is missing your Launch GA impeme...

How I work around this is by having a 2nd rule to listen to the 1st rule.

So Vimeo's library offered in that link is made specifically for Google Analytics which sends events. Easier solution: Very ugly workaround but what you can do is listen to those Google post events (more details here: https://stackoverflow.com/questions/48806235/listening-google-events) Harder solution:I, unfortunately, don't have a Vimeo premium account to see the Google Analytics library.js file but you would want to read how that library works, figure out and find their listeners, copy that c...

Here's a checklist when I experience this: Do a hard refresh on your browser. Clear all application data.Try IncognitoTry outside a different network (use cellphone network or another wifi not connected to same network) - This is incase it is a network caching issue.Check with your website/akamai cache

I like having more control over my global variables as some page views and some track links may have different variables set. So what I do is I have 2 rules.Global Variables - Page ViewGlobal Variables - Track LinkFor every page view and track link, I call a direct call to call the respective rule above then fire a pageview or track link beacon. Inside the rule, I set global variables over that. That way, I can clear variables when I need to and not have to clear when I don't need to.