This article will review the types of beacons available and how to select the right one for your site, how to determine if you need to make any configuration changes to track additional information, and how to integrate the beacon into your site.
Beacon Installation Checklist
- Use Evergage beacon version 4 or later (adjust it in SETTINGS > Beacon Version)
- Point the integration to the right protocol (https or http). You can also omit the protocol and include //cdn.evergage.com...
- Insert the synchronous integration script
- Insert any other _aaq.push() calls needed before the script
- Review the differences in page load events
There are two types of integrations that can be done with the Evergage beacon:
- Synchronous–recommended for most customers, this integration loads the beacon before the page loads so Evergage can prevent page flicker, a momentary flash of the original page content
- Asynchronous–this integration loads the beacon after the page has loaded. With this integration, Evergage cannot protect against flicker
For more specific details, please refer to the article on Synchronous vs. Asynchronous Integration.
Integrating the Beacon
- Log into Evergage as an administrator
- Select SETTINGS
- If you have more than one dataset, select the one you want from the dropdown at the top left of the screen before copying the beacon code
Copy the code as directed on the screen and place it into the header of your site to ensure that the beacon is loaded on every page of the site. It will be similar to
Tracking Additional User Information
Depending on what additional information you would like to collect, you may need to adjust the beacon code before you place it in your site. Typically, there are three additional pieces of information you may want to gather about logged in site or product visitors.
3. Account Type/Subscription Level
You will need to include two script tags if you adjust the beacon code to capture other variables, like UserID. In the first script tag, define these variables and in the second, define the beacon, in that order as user info must be loaded before the beacon. For example, if you are defining the UserID in a variable called mySitesUsername, it would look something like this:
This page has no comments.