Without seeing your implementation or your sites this will be hard... but I'm going to provide a few suggestions.
1. If your applications are a Single Page Application, it's possible your s.t call isn't using something like "DOM Ready" or "Window Loaded" cause that would only work on the first page and nothing else... in this case you are likely using some other custom trigger designed to work with the SPA.... however, what may be happening is that the initial load of the site isn't triggering that action, and so the tracking isn't firing.
This may mean asking the developers to properly ensure the trigger is fired correctly, or (I don't really like this... but your hands may be tied on this) create a second trigger for a standard DOM Ready or Window Loaded in order to capture the initial load of the content...... (the problem here is if the main trigger starts to work on the initial page, you will get two page views....)
2. Regardless of whether or not the site is an SPA, you may need to do some digging... There is a good Chrome extension called "Launch Switch" which when enabled turns on logging... so you can see which rules are firing, or if conditions are applied to rules, which rules aren't firing because of said condition.... This can be invaluable in debugging your implementation to see what is happening in your console log.
If you don't want to install another extension (or can't for some reason, or just hate Chrome ) you can also throw a custom code block as the first item in your rule and just have it write some debugging code to your console:
console.log("page view rule should be firing") and see if that text appears in your console or not.....
Good Luck!
