Content Analysis DB > Fields > Field Types > > Page Views My List ♥ ()

Page Views

Page views are often the first thing to be added from an additional source, after the basic rows of content in the inventory/audit have been determined. Although not always the most useful metric for the value of content, it's often the most immediately tangible proxy.
General Usefulness: ★ ★ ★
Ease of Automation: ⚙⚙⚙
⚠ Gotchas ⚠

Dupes. Many times analytics returns a row per unique URL with parameters (100 page views for /blog?page=1, 20 page views for /blog?page=2, etc). Ordinarily content analysis is most useful at the level of listing pages as opposed to exactly what depth of pagination (so an inventory would just have a line for /blog). So when merging pageviews, these should be summed if there are multiple pagination urls for the same conceptual page.

Missing values. If an analytics tool indicates no value for pageviews for a URL, in most cases this can be considered as a 0 for the value (no pageviews). On the other hand, it may be an indication that the analytics package is misconfigued.

Source Types:
Analytics, Formula

Other closely related fields you may consider

Note that lower level fields may sometimes be needed to compute more useful fields. Also, sometimes the higher level fields may be more difficult to compute, so they are not always worth it.

↑↑↑ Consider this higher level field ↑↑↑
Page Views (you are here)
In Content Chimera

Chimera imports data from a variety of analytics vendors. It also correctly deals with URLs that are duplicate from the content analysis perspective (such as those with campaign IDs).