Interaction Studio Classic Only
- The contents of this article are intended for customers using Interaction Studio (formerly Evergage Classic).
- The Visual Editor Chrome Extension will no longer be available starting January 1, 2023. For more information, see this knowledge article.
Beacon Installation Checklist
- Use Interaction Studio 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.evgnet.com...
- Insert the synchronous integration script
- Insert any other _aaq.push() calls needed before the script
- Review the differences in page load events
- Synchronous–recommended for most customers, this integration loads the beacon before the page loads so Interaction Studio can prevent page flicker, a momentary flash of the original page content
- Asynchronous–not recommended because this integration loads the beacon after the page has loaded. With this integration, Interaction Studio cannot protect against flicker
The hybrid beacon integration is no longer supported by Interaction Studio.
Add Campaign Request Security
Campaign Request Security is an option in your Interaction Studio integration which makes campaigns and other tracking more secure. This option requires you to write code for your site to properly encrypt userIDs with an API token. If a user's ID cannot be properly decrypted, then Interaction Studio will not process events for this user.
Enable Campaign Request Security requires custom code to Encrypt userIDs on your site.
Encrypted Fields is an option in your Interaction Studio integration to make field tracking more secure. This option requires code to be written on your site to encrypt values so they are not readable by the browser or browser's cache. If a field value cannot be properly decrypted then Interaction Studio will not send this field value to Interaction Studio for this user.
Enable Encrypted Fields requires custom code to Encrypt user fields on your site.
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.
If the account of the logged in user is visible in your site or product or if you include the account name in the subdomain of your URL when logged in (i.e.
Account Type/Subscription Level
Sample Code Block
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: