- Correlation reports where only one variable fired: Correlation reports must account for every instance of that particular variable value. For example, if you tried breaking down prop1 by prop2 and these two variables don't fire in the same image request, you see a correlation report with a breakdown of "Unspecified." To remove unspecified from correlation reports, it's necessary to define all correlated traffic variables with a value on the same image request. In many situations, this expectation is unrealistic. Therefore, this line item can be ignored as long as the user is aware that it means that the first variable was defined without the second.
- Non-browser hits when viewing Technology reports: Adobe Analytics is heavily dependent on Javascript functions to retrieve Visitor Profile information. Unknown browser sources where JavaScript is not available contributes to this line item (for example, an executable program or a user-created browser). These Technology reports show unspecified to indicate that this information was unable to be gathered. "Unspecified" can also occur if your implementation code is placed into the
<head>tags of your web page. Adobe highly recommends that you don't use the <head> tags, as it affects many aspects of reporting. Placing your implementation within the<body>tags resolves this issue. - Hierarchy reports with different amounts of levels: Similar to correlations, hierarchies must account for all page views across all levels. For example, you have one page with a hierarchy two levels deep and another three levels deep. Viewing the level-three hierarchy report in marketing reports & analytics shows "unspecified" to account for the page with only two levels. It is not advisable to attempt to remove "Unspecified" from hierarchy reports. Doing so requires that every page on your site the same number of levels. Since this practice essentially defeats the purpose of implementing hierarchies in the first place, Adobe recommends that you ignore these breakdowns in reporting.
