Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
28 Cards in this Set
- Front
- Back
another name for s.prop
|
custom traffic variables
custom insight variables |
|
where to find the s.props in omniture
|
custom traffic -> custom traffic 1-10 etc
|
|
s.props used for
|
1. counting instances of a specific value - how many times a value was recorded
2. measuring traffic for a specific segment |
|
tip for preventing duplicate search terms
|
force all user-inputted values to lower case (so hat, Hat and HAT are all recorded as the same search term...)
|
|
s.prop scope of search in terms of internal site search
|
whether visitor has searched whole site or just a section of the site
|
|
examples of segments of traffic
|
logged in and non-logged in users, language pages etc.
|
|
s.props and page grouping
|
can see how much traffic has gone to sections and sub-sections
|
|
examples of an s.prop having different values
|
e.g. to identify the type of page a visitor is on, such as 'category page' or 'product page'
|
|
s.props and registered users/different types of members
|
on every page that the member/registered user touches, the s.prop populates on each page
|
|
list prop - description + example
|
- want to capture many separate values from a single page, but want to see them separately
- e.g. survey with radio buttons on a question - use regular s.prop to record survey submissions, would see a list of the combinations of options people had chosen and how many had chosen each - if use list prop, would see a separate and would get all options separately and how many had picked each as one of their options |
|
internal search example
|
using three sep s.props, can record nb times a term is searched, nb results and the section that you're searching within
|
|
what type of variable to use when tracking internal search
|
s.prop
|
|
type of variable to use to segment visitor traffic by demographic
|
s.prop
|
|
type of variable to use to count values on a page/function
|
s.prop
|
|
type of variable to use to understand visitor traffic by navigation or category
|
s.prop
|
|
example of a pre-defined event (s.event)
|
track a product as it moves through the checkout process
|
|
example of a possible custom event
(s.event) |
e.g. adding whether shipping is required on a product purchased at the checkout
|
|
event (definition)
|
verb
any logged or recorded action that has a specific time and date associated to it by browser or server activities that happen within a page e.g. ad impressions, starting a transaction, finishing a transaction, changing form fields, starting multimedia views |
|
s.products
|
- only exitsts on relevant pages
- used to track products and product categories, purchase quantity and price - tells you: category, product, Qty, price, Incrementor, Merchandising |
|
s.zip
|
allows to track amount of conversion from a particular US zip code
|
|
s.campaign
|
identifies marketing campaigns which bring traffic to the site
|
|
e.var (another name)
|
custom conversion variables
|
|
e.var - use
|
used to identify how well specific attributes or actions contribute to success events on your site
|
|
conversion variable
|
noun
describes what lead to the conversion who, which or what affected success |
|
conversion variables and events in the following sentences:
which campaign drove the most orders? which user type had the most form completions? |
conversion variables: campaign, user type
events: orders, form completions |
|
how do conversion variables get tracked/recorded to the success event?
|
tie conversion variables into the success events so can see e.g. that 50% of orders today came from the '3 for 2 Today Only' campaign
|
|
tracking codes
|
A piece of code that tracks a user’s interaction and movement through a web site
|
|
how to record that visitors come from a certain ad campaign?
|
the s.campaign variable populates with the tracking code e.g. google_ad_7'. This stays with the visitor throughout their visit.
|