visits is a metric. In the report you used for #1, at the top right of the part of the report that shows your columns and data, there's an "add metrics" button. Click on that and drag "visits" from the list of metrics to add it to your report.
sidenote: an eVar set to visit expiration will likely be more useful to you, especially when you want to start figuring out more complex things.
page views is how many times the dimension was popped (or persisted on, like an eVar rolling over based on expiration) a page view request (an s.t call). instances is how many times the dimension was popped on all requests (page view s.t and custom link tracking s.tl)
edit: from your followup question below...
pageview vs. instance metric
page views
is how many times the dimension was popped (or persisted on, like an eVar rolling over based on expiration) a page view request (an s.t
call). instances
is how many times the dimension was popped on all requests (page view s.t
and custom link tracking s.tl
).
Consider the following code:
<html>
<head></head>
<body>
<a onclick="s_trackThis();">click me!</a>
<script type='text/javascript'>
function s_trackThis() {
s.linkTrackVars='prop1';
s.prop1='foobar';
s.tl(true,'o','link click');
}
</script>
<!--simplified on-page global code-->
<script type='text/javascript'>var s_account='somersid';</script>
<script type='text/javascript' scr='s_account.js'></script>
<script type='text/javascript'>
s.pageName = 'some page';
s.prop1 = 'foobar';
s.t();
</script>
<!--end simplifed on-page global code-->
</body>
</html>
On first page load, the on-page code is triggered, and prop1
is recorded with a value of "foobar". So that's one page view and one instance hit. Then, when you click on the link, the wrapper function is invoked and prop1
is popped again with the same value. The function makes a s.tl
call which does not count as a page view, so now you will see 2 instances
and 1 pageview
for the value "foobar"