4 Replies Latest reply on Jan 24, 2018 6:48 AM by blasta86794993

    ADBINTERNAL:Lifecycle Custom Link Causing Phantom Pagename?

    blasta86794993 Level 1

      We recently launched Adobe Analytics tracking on an Android app. We set context data variables within the app, and are using processing rules in Adobe Admin to map them to the relevant variables. We're using the context data variables modularly, like puzzle pieces and doing a lot of concatenated values delimited by an underscore. For example pagename for category pages is:




      We saw some funny values in the pagename report during QA, but I chalked it up to something weird in the dev build. When we launched the production build, we found something unexpected: a phantom page that is a significant percent of traffic and almost all entries!



      When you break that "_" down by any other variable, the breakdowns always show "None." Clearly that "_" is showing up like that because somewhere there is a server call with no context data variables but the processing rule is still executing. When you see that the phantom "_" page is 99.3% of entries, it's clear that it is most likely related to the launch lifecycle event. To try to correct, we added another condition to our pagename processing rule specifying that <<page_type>> had to be set before setting s.pagename.


      Well the good news is after adjusting that condition, "_" is gone from the pages report. The bad news is that it was simply replaced by "Other."



      I have been debugging and QA'ing using the Charles debugger, and I never see an initial trackState server call that would explain this phantom page. That ADBINTERNAL:Lifecycle Launch Event trackAction is the only thing that fires before that home page.


      I also looked into when Adobe populates the "Other" value, and according to this Knowledgebase article (None, Unspecified, Unknown, and Other in reporting), "Other" happens when "Pages fire outside your internal URL filters". Not sure how URL filters work in an app, but for what it's worth there is one wildcard URL filter set up on this report suite for "."


      Any ideas on why this might be happening and how we can get this gremlin out of our reports?