What do we track in UserIQ by default?

What do we track in a Pageview?

action_name: “UserIQ —” // This is the title of the page, we pull it via the standard DOM api as follows: documentAlias.getElementsByTagName(‘title’);

cvars: {1: [“user_id”, “chris@useriq.com”], 2: [“user_name”, “Chris Morgan”], 3: [“account_id”, “1”]}

event_ts: 1517515767078 // This is the unix timestamp pulled from the local browser timestamp

res: “1920x1200" // This is the screen resolution as reported by the browser

site_id: “1” // This is your site id from UserIQ

type: “pageview” // This is our event type specified by UserIQ

uid: “chris@useriq.com” // This is the user id specified by your user_id cvar

url: “http://dev.useriq.com:3000/#!/home” // This is the current browser URL

url_ref: “” // This is the referrer url from the browser

visitor_id: “049bb0d6c166f4f2" // This is a custom sha1 hash made by UserIQ for anonymous id tracking. Hash is generated by combining the user agent, platform, browser features, current timestamp, and math.random(). We then hash the combination and pull the first 16 characters.

_idts: “1512700852” // This is the unix timestamp of when we generated the visitor_id

_idvc: “54" // This is the naive visit count for this visitor_id

What do we track in a Click Event?

className: “health-kpi green ng-binding” // This is the classlist of the event target

cvars: {1: [“user_id”, “chris@useriq.com”], 2: [“user_name”, “Chris Morgan”], 3: [“account_id”, “1”],…}

event_ts: 1517519802064 // This is the unix timestamp pulled from the local browser timestamp

res: “1920x1200" // This is the screen resolution as reported by the browser

site_id: “1” // This is your site id from UserIQ

type: “click” // This is our event type specified by UserIQ

uid: “chris@useriq.com” // This is the user id specified by your user_id cvar

url: “http://dev.useriq.com:3000/#!/home” // This is the current browser URL

url_ref: “” // This is the referrer url from the browser

useriq_scheme: “H1 className: health-kpi green ng-binding textContent: 43%” // This is a custom scheme built by a combination of nodeName, id, classList, and text content. Please keep in mind you can disable text tracking and id tracking in the snippet as needed.
visitor_id: “049bb0d6c166f4f2” // This is a custom sha1 hash made by UserIQ for anonymous id tracking. Hash is generated by combining the user agent, platform, browser features, current timestamp, and math.random(). We then hash the combination and pull the first 16 characters.

_idts: “1512700852" // This is the unix timestamp of when we generated the visitor_id

_idvc: “54” // This is the naive visit count for this visitor_id

** Additionally, we provide the option to stop tracking id and/or textContent of a tagged feature. The ID can be stopped from being tracked by enabling the highlighted toggle in site settings.

For textContent, you can disable it by calling this piece of code as soon as the page is loaded or whenever required.