BrightDoor’s new Website Tracking feature “SiteTrack’ allows you to understand newly registered contacts’ behavior:  when they visit your site, specific pages they visit, and visit frequency. With BrightDoor’s Tracking Script installed on the pages of your website, you will have the ability for your BD Central users to see contact’s website session information and help assess their likelihood to purchase. See this article or more information about contact data.  



Within BDC, users (with appropriate permissions) can find “SiteTracker” option inside “Content & Apps section”.  Click on Website Tracker tile to open the tracker setting page.






Copy the entire Code snippet and paste to incorporate within your  website HEAD tag for reporting page visits. Once the tracking code is installed on the website, a GUID is generated; and allows activity on website to be tracked in BrightDoor. BrightDoor will store all anonymous tracking information and append the data when a contact registers.  

For example, by default the code will appear as:


<script type=’text/javascript’>var trackerOptions = { BDClientName: ‘yourcompany‘, };</script><script type=’text/javascript’ src=’’></script>



If required, add in additional configuration in the TRACKER OPTIONS:

  • Call API On: “CallApiOn” setting determines how often the tracking data is sent to BDC server for further processing. Valid options are:
    • Immediate : send the data upon user activity (Default)
    • Timer: This option enables us to send the data at timed interval in seconds. When using this option, we also need to configure “TimerInterval” setting.  You can do this by adding in a numerical designation (e.g. 10S for ten seconds). IClicksCount: This option is used to send the data after certain number of clicks on the page. When using this option, we also need to configure “ClicksCount” setting.
    • *If your prospects are in a remote area with slow service, this might be helpful.  More than likely, the default setting is best.*
  • Valid Elements: “ValidElements” setting is used to limit the tracking to select elements on webpage. User shall provide a comma separated list of element names to be tracked. *Especially helpful when using custom html tags.*

An Example entry would appear like this:


A.  API Users:

If you are an API user for registrations, you will need to update your methods to include the attribute for website tracking.   You will pass the value of the hidden field bdguid to the Contact Custom Attribute WebsiteTrackerID (automatically added into your database).  BrightDoor associates the anonymous log to the registered contact in BDC using this attribute.  

As with other Custom Attributes, this must be URL encoded.  An example looks like:


b. Email to Lead Users:

For sites that use email to lead (dropbox ) you must configure and add WebsiteTracker in 2 places:

  1. the email template that you pass via email in addition 
  2. the setup page in BrightDoor Central   

Note:  for WordPress site users: you will have to configure and add [bdguid] in the email template in addition to the javascript template


Known Restrictions:

  • SiteTrack will work only with newly registered contacts.  There will be no retractive association with contacts already in the database.
  • Different browsers have different sessions for tracking.  For example, if a user registers in Chrome but the browses in Firefox, there can be n association with the cookies placed between the browsers.
  • Multiple devices will also not cross tabulate visits to a website.  For example, if a user registers on a mobile friendly site via a phone, but then visits on a computer browser, there is no ability to cross reference the visits.
  • SiteTracker will track user’s only activities done after successful integration of tracking script and the feature is enabled in BDC.
  • In the event a user clears browsing data, user will be treated as a new users.
  • Dashboard and Contact views will show data of registered contacts only.
  • A page redirect may cause data loss in instances where advanced options are added (i.e. Timer/Clicks Count)
  • Javascript must be enabled on the browser.
  • Cookies must be enabled.
  • For existing clients using the BrightDoor API, the code must be updated to pass the bdguid through the registrations
Comments are closed.