How Can We Help?

Articles in this section

Tracking Snippet FAQ

Avatar
Andres Rincon
  • Updated
Follow

Frequently Asked Questions:

What do we use the values for in UserIQ?

  • user_id is a required value for UserIQ as it is the cornerstone of most of our analytics.

  • user_name is simply used for display purposes

  • account_id is used for associating users to accounts as well as accounts to organizations.
    This is a very critical variable for anyone wanting to leverage account segmentation

  • account_name is simply used for display purposes

  • signup_date is used for a number of pre-populated segments and require it to be in the “YYYY-MM-DD” format

  • user_email is used for a number of different segmentation options and to use the email engagements feature without importing lists.

Does it matter what type of value is passed to UserIQ?

Nope, we will cast all values to a string before sending it to our API which then converts them into proper formats depending on type.

What are Taboo Values?

Taboo values are essentially dummy values that are being passed into UserIQ for tracking purposes and this excludes any personal data like email, username, etc. For example, if you would not want us to know the username of the users that are associated with the account, you can pass in values like 'useriq-unknown' in your 'user_name' custom variable which will essentially hide the username from our view.

If you need to pass a dummy value as you do not want to know the user’s information, we will automatically parse the following strings into nothing on our end.

['useriq-unknown','insert_user_id','insert_user_name','user_name','account_id','account_name','guest','not logged in','insert_account_id','insert_account_name','Anonymous','null','user_id','nil','none','empty','visitor','unknown','INSERT_YOUR_APP_USER_ID_HERE','INSERT_YOUR_APP_ACCOUNT_ID_HERE','INSERT_USER_NAME_HERE','INSERT_ACCOUNT_NAME_HERE','INSERT_USER_EMAIL_HERE','INSERT_USER_SIGNUP_DATE_HERE_YYYY-MM-DD']

What if I want to exclude a page from tracking?

This is a question that gets asked quite a bit and we can handle this in more than one way. Let me first describe the current method used by UserIQ and a few others whose login page does not need to be tracked.

if(/sign_in/.test(window.location.pathname)){ 
   useriq.setDoNotTrack(true) 
}

The above line of JavaScript can be included inside your snippet at any point in time but you will need to change the bolded “sign_in” part to match your specific use case.

What if my application contains iFrames?

We highly recommend the tracking snippet be installed on all pages, including inside of all iFrames, for tracking and other feature functionality to work seamlessly between your application and UserIQ. 

What instances does UserIQ not track?

Below are the following instances where we skip events in our application.

1. useriq.js
This gets loaded at the end user's browser. If any of the c-vars include "impersonated", "impersonation", "impersonator", "impersonate"(case-insensitive) as the key and true as the value, we don’t track them.

 

2. IP or Domain blacklisting
Before the creation of visitors/customer_accounts, we skip the events that come from the domains/IPs blacklisted by your application.

 

3. Unknown Visitors
Before the creation of visitors/customer_accounts, we skip the events with no User_id c-var.

 

4. Data blacklisting
If any of the incoming data matches the key-value pair added in the site settings, we skip the event. 

 

 

Related articles

Comments

0 comments

Article is closed for comments.