Cannot give you an exact answer without debugging the scenario, but i suspect that there is a problem with Processing Rule Setup.
If you have process rule setup say,
Copy Context Data "Mobile_PageName" to "Page Name", then for the life cycle server calls, the Page Name will be empty and it may bucket everything under Other.
So change the rule to Copy Context Data "Mobile_PageName" to "Page Name" if "Mobile_PageName" is set. This should eliminate these gaps. If you are already using this coniditon, sorry, i need to debug the scenario to give the answer.
You can ignore Internal Filters, because these will not affect Page Name.
Hi PratheepArunRaj, thanks for your response! We already did try something similar, which was to add a condition to the pagename processing rule to only run if "content type" was set. That only resulted in turning our "_" pages into "Other."
What is the best way to share the company/report suite info with you privately so you can debug? Can I just send a private message here in the forums, or do I need to open a Customer Care ticket and ask them to have you assigned to it?
Following up to share the resolution and mark this resolved: we inadvertently had a processing rule setting page_url. (This was not intentional.) We learned from Client Care that "When manipulating pagename and page_url via processing rules it causes the custom link to be counted as a pageview."
The Lifecycle Launch event is normally a custom link, but because the processing rule was trying to give it a URL it forced it to fire a pageview, which then caused a value of "Other" to appear in the pages report.
Once we removed that processing rule, the "Other" page dropped off: