Expand my Community achievements bar.

SOLVED

Safari in Browsers Report

Avatar

Level 1

Is there a reason there is a line item titled "Safari" without a version number within the default Browsers Report in Adobe Analytics? I received this question from IT - since there are other line items featuring Safari with a version number, I'm confused as to why this exists. See screenshot for visual and I appreciate any/all information you can provide. Thanks!

1 Accepted Solution

Avatar

Correct answer by
Level 10

The Browser value is a result of the http user agent header parsing (lookup) that may look as follows:

  • Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_8; de-at) AppleWebKit/533.21.1 (KHTML, like Gecko) Version/5.0.5 Safari/533.21.1
  • Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_6; en-us) AppleWebKit/528.16 (KHTML, like Gecko)

You may recognize the version only for the first example. "Safari" without a version will likely be returned for the second.

View solution in original post

3 Replies

Avatar

Level 10

It's likely used as a placeholder in case the version can't be determined.

Avatar

Level 1

My question would then be in what circumstances would Adobe be unable to determine the version number and why that is the case.

Avatar

Correct answer by
Level 10

The Browser value is a result of the http user agent header parsing (lookup) that may look as follows:

  • Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_8; de-at) AppleWebKit/533.21.1 (KHTML, like Gecko) Version/5.0.5 Safari/533.21.1
  • Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_6; en-us) AppleWebKit/528.16 (KHTML, like Gecko)

You may recognize the version only for the first example. "Safari" without a version will likely be returned for the second.

The following has evaluated to null or missing: ==> liql("SELECT id, subject, body, depth, post_time, author.login, author.id, author.rank, metrics.views FROM messages WHERE topic.id = '${topicId}' AND is_solution = true").data.items[0] [in template "analytics-container" at line 82, column 31] ---- Tip: It's the final [] step that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign acceptedAnswer = liql("SELECT... [in template "analytics-container" at line 82, column 5] ----