Page
- A page is a visitor pageview connected to
a specific URL. When the visitor navigates to a different part of the
site, that is a new pageview. On each pageview units can be tracked.
Unit
- Think of a unit as part of a
page. It can be an ad, a video or simply an area. Each unit
is required to have a name and it’s possible to specify more
information for each unit.
Fill
- A unit can be filled or empty. This indicates the
state of the contents inside the unit. For example, only filled units will measure
visibility. Units of type ad
(the default type) will automatically and
asynchronously detect flash objects and images inside itself and become filled when these have loaded.
area
units are always filled.
Tracking key
- Tracking key is a
combination of a string of 12 upper case characters and numbers and the name of
the site. This information is provided by us and uniquely identifies your site.
If you use the wrong tracking key the data will not show up in your reports.
Category
- To enable the category drilldown
in the Burt reports, the category of the current page needs to be
specified. If the category is not set manually, the agent tries to
figure out a category automatically from the URL. Depending on the
site map structure, this can be either good or bad, so we always
recommend set the category manually. The
dev panel will show the category for each
page. Example categories are: sport
, motor
, economy
and article
Cloud key
- A cloud key is a string of 12
large characters and numbers. All cloud keys are provided by Burt.
Demographics provider
- You
might have a demographics provider, which collects demographic data
about your users, such as: age
and sex
.
Annotation
- An annotation is used to add
additional information to a page or unit. It
consists of a scope
, a name
and a value
scope
- A page and unit can be annotated several times, this is
a scope to differ between them. Some scopes trigger Burt specific
actions. Such scopes all begin with burt.
, for example
burt.campaign
. If the purpose is not to trigger a Burt event, the
scope can be anything, not starting with burt.
.name
- The name describes what the value
holds. For example
oas-campaign-id
or dfp-order-id
.value
- This is the value. For example 1234
or abcd
.values
- This is like the value, except that many values are
allowed. Each value is separated with a comma. For example foo,
bar, baz
.Connection
- A connection is much like an
annotation. The difference is that the connections does
not send a value, like annotations. Instead an ID is sent as value and
then that ID is connected using the backend API.
Activity
- A page is active when the user is
actively using it. If a user for example switches to another tab or
program, the page is considered inactive.