- TLC Home Home
- Discussions Discussions
- Documentation Documentation
- Knowledge Base Knowledge Base
- Education Education
- Blog Blog
- Support Desk Support Desk
Have you ever sat down to write something, or draw something and find yourself just staring at the empty page trying to force inspiration into being just by sheer will?
I call it “Empty piece of paper syndrome” - it’s like the blankness is somehow contagious and gets into your head making everything seem foggy.
It can be like this when it comes to thinking about data too, if there’s nothing to look at, it’s hard to think of what could be there.
This is one of the reasons why AudienceStream, out of the box, comes with a whole bunch of useful attributes that are already configured. There are both Visit and Visitor attributes, and typically contain statistical information that may be useful to determine useful information about the visitor or visit. They don’t need any additional information from the visitor, just the standard web traffic data from the collect tag.
Here is a list of all of the preloaded attributes (including the slightly contradictory “Unbadged” badge) as they are listed in the user interface.
Visitor Attributes |
ID |
Type |
Description |
Average visit duration in minutes |
26 |
Number |
Average visit duration in minutes |
Average visits per week |
29 |
Number |
Average visits per week |
Fan |
30 |
Badge |
More than two total visits and more direct visits than refers |
First visit |
23 |
Date |
Date of first visit |
Frequent visitor |
31 |
Badge |
Two or more average visits per week |
Last event URL |
17 |
String |
Last event URL for visitor |
Last visit |
24 |
Date |
Date of last visit |
Lifetime browser types used |
57 |
Tally |
Tally of how many times each type of browser is used |
Lifetime browser types used (favorite) |
56 |
String |
Captures the favorite metric for Metric Set: Lifetime browser types used |
Lifetime browser versions used |
63 |
Tally |
Tally of browser versions used |
Lifetime browser versions used (favorite) |
62 |
String |
Captures the favorite metric for Metric Set: Lifetime browser versions used |
Lifetime devices used |
55 |
Tally |
Tally of devices used |
Lifetime devices used (favorite) |
54 |
String |
Captures the favorite metric for Metric Set: Lifetime devices used |
Lifetime event count |
22 |
Number |
Total number of events triggered by user |
Lifetime operating systems used |
59 |
Tally |
Tally of operating systems used |
Lifetime operating systems used (favorite) |
58 |
String |
Captures the favorite metric for Metric Set: Lifetime operating systems used |
Lifetime platforms used |
61 |
Tally |
Tally of platforms used |
Lifetime platforms used (favorite) |
60 |
String |
Captures the favorite metric for Metric Set: Lifetime platforms used |
Lifetime visit count |
21 |
Number |
Total number of times user has visited site |
Returning visitor |
27 |
Badge |
Return visitor |
Total direct visits |
15 |
Number |
Total direct visits |
Total referred visits |
16 |
Number |
Total referred visits |
Total time spent on site in minutes |
25 |
Number |
Sum duration of all user visits |
Unbadged |
32 |
Badge |
The visitor has not been assigned any badges |
Weeks since first visit |
28 |
Number |
Weeks elapsed since first visit |
Visit Attributes |
ID |
Type |
Description |
Active browser type |
44 |
String |
The browser actively being used by the visitor |
Active browser types |
49 |
Set of strings |
Deduplicated list of browser types used this visit |
Active browser version |
48 |
String |
The browser version actively being used by the visitor |
Active browser versions |
53 |
Set of strings |
Deduplicated list of browser versions this visit |
Active device |
46 |
String |
The device actively being used by the visitor |
Active devices |
51 |
Set of strings |
Deduplicated list of devices this visit |
Active operating system |
45 |
String |
The operating system actively being used by the visitor |
Active operating systems |
50 |
Set of strings |
Deduplicated list of operating systems |
Active platform |
47 |
String |
The platform actively being used by the visitor |
Active platforms |
52 |
Set of strings |
Deduplicated list of platforms |
Direct visit |
14 |
Boolean |
The user navigated directly to the site |
Entry URL |
5 |
String |
URL of the first page visited |
Event count |
7 |
Number |
Total number of events in visit |
Exit URL |
6 |
String |
URL of the last page visited |
Referred visit |
13 |
Boolean |
The user was referred from another site |
Visit duration |
12 |
Number |
Visit duration in minutes |
Visit end |
11 |
Date |
Visit end date |
Visit start |
10 |
Date |
Visit start date |
Well, you can use them like any other attribute, in rules and enrichments for other attributes.
So for example, you could use the frequent visitor badge directly to drive an audience to send an email saying “Thank you for being a regular visitor” or you could use “Total Direct Visits” and “Total Referred Visits” to work out the ratio for direct/referred visits for a user, and therefore how they engage with the site.
You could potentially use the favorite lifetime operating system to perhaps alter the placement of specific downloads, making more relevant apps appear first.
Or of course you can always just fire the data out for reporting purposes.
We sometimes like to think of attributes like lego bricks to build whatever you need.
Well, for preloaded attributes the lego bricks are kind of glued down so that the models can’t be broken.
However - although the preloaded attributes themselves are fixed solid, you can duplicate them. The duplicate then contains all the enrichments and rules for you to modify as you need.
For example here is a copy of the Frequent visitor badge:
As you can see the rules are now visible, and you can modify them as you need to.
If you have any questions or perhaps you’ve done something spectacular using just the preloaded attributes - please let us know!
Copyright All Rights Reserved © 2008-2023