Page tree
Skip to end of metadata
Go to start of metadata

The Salesforce Interactions SDK Launcher is a Google Chrome browser extension that includes the Visual Editor tool you use to add personalization features to your website. Using developer created templates, you can create personalization campaigns targeted to specific groups, individual users, or events. You can learn more about the relationship between web campaigns and templates in Web Campaigns and Templates.



Evergage Launcher Deprecation

The Salesforce Interactions SDK Launcher replaces the Evergage Launcher. The Salesforce Interactions SDK launcher has the same functionality as the Evergage Launcher for Interaction Studio customers and also includes a sitemap editor for Salesforce CDP customers. This article details how to use the launcher for customers that either own both Interaction Studio and Salesforce CDP or just Interaction Studio. Documentation for Salesforce CDP only customers is available on the Salesforce CDP documentation site. Customers who have the existing Evergage Launcher extension must remove the extension before downloading the new extension from the Salesforce store. The Evergage Launcher was removed from the chrome store on 12/31/21.

This Article Explains

This article details how and where to install and launch the Evergage Launcher extension.

Sections in this Article

Install the Salesforce Interactions SDK Launcher

Required Permissions

Your dataset must be on beacon version 16 or greater and your user account must be assigned a role with Campaign Create/Edit permissions to perform the actions outlined in this article.


  1. Launch a Google Chrome browser and navigate to chrome://extensions/
  2. Remove any previously installed Evergage extensions, such as the Evergage Visual Editor and Evergage Launcher
  3. Navigate to the Salesforce Interactions SDK Launcher chrome store page
  4. Click Add to Chrome
  5. Click Add extension to add the Salesforce Interactions SDK Launcher to your browser



Use the Salesforce Interactions SDK Launcher

Configuration Required

Before using the Salesforce Interactions SDK Launcher on your site, ensure that you have added it as a dataset in Interaction Studio. See Configure Interaction Studio for Multiple Sites for more information.

Detected Beacon

You can view the account, dataset, and beacon version currently detected and running according to your local browser.

  1. Navigate to your website (for example, northerntrailoutfitters.com)
  2. Click the Salesforce Interactions SDK Launcher Extension
  3. Select Interaction Studio & Salesforce CDP from the Product Type Drop-Down (if a beacon is detected, it should default to the IS & CDP option)
    1. Customers who own both Interaction Studio & Salesforce CDP or just Interaction Studio should use this selection
    2. Salesforce CDP Only is a sitemap editor that should only be used by Customers who do not own Interaction Studio
  4. The modal will show the following information about your site:
    1. Detected Beacon - if there is an orange X and no other information, this means that the Interaction Studio JavaScript beacon is not on the page. If there is a green check, you will see the account, dataset, and beacon version, in that order, of the Interaction Studio JavaScript beacon installed on the page
    2. Account - this is the account associated with the Interaction Studio beacon installed on the page. Typically, your account name is your company or brand name, but that may not always be the case
    3. Dataset - this is the dataset associated with the Interaction Studio beacon installed on the page. You may only have one dataset for your account, or you may have more than one. For example, you could have a dataset for different sites that are based on brand or geography. You could also have datasets for staging and production


Injecting the SDK

If the beacon is not present on your site, you can inject it using the Salesforce Interactions SDK Launcher. This simulates an asynchronous implementation of the beacon.

  1. Navigate to your website (for example, northerntrailoutfitters.com)
  2. Click the Salesforce Interactions SDK Launcher Extension
  3. Enter the account and dataset (for example, account = training and dataset = nto)
  4. Enable INJECT SDK
  5. Refresh the page
  6. Click the Salesforce Interactions SDK Extension
  7. Confirm that the modal shows a green check next to DETECTED BEACON, the correct account and dataset appear in the designated fields, and the orange INJECTED indicator is displayed after the beacon version, as shown in the lower image to the right. You may need to refresh the page several times to see the new settings applied due to cached data in your browser

Forcing the SDK URL

If the beacon is already present on the site, but you need to work on a different dataset, you can change the dataset used on the site in your local browser using the Force SDK URL option. This is commonly used to maintain a development/testing dataset and a production dataset that is live on the site.

Locate the SDK URL

  1. Log into Interaction Studio as an administrator
  2. Ensure that the dataset you want to simulate is selected at the top
  3. From the left navigation, select Web > JavaScript Integration
  4. On the Synchronous tab, copy the value for src (indicated by the red outline in the image at the right) and append it to https: so that the URL is in the format https://cdn.evgnet.com/beacon/account/dataset/scripts/evergage.min.js. This is the SDK URL you will use in the next section



Finding the SDK URL for your dataset.

Add the Force SDK URL

  1. Navigate to your website (for example, northerntrailoutfitters.com)
  2. Click the Salesforce Interactions SDK Launcher Extension
  3. Enter the account and dataset (for example, account = training and dataset = nto)
  4. Expand the Advanced dropdown at the bottom of the browser extension window
  5. Enable FORCE SDK URL
  6. Paste the SDK URL you created in step 4 of the previous section (For example, https://cdn.evgnet.com/beacon/training/nto/scripts/evergage.min.js)
  7. Refresh the page
  8. Click the Salesforce Interactions SDK Extension
  9. Confirm that the modal shows a green check next to DETECTED BEACON and the correct account and dataset appear in the designated fields. You may need to refresh the page several times to see the new settings applied due to cached data in your browser



Visual Editor

Once the browser extension displays the desired account and dataset in the Detected Beacon section of the browser extension window, you will be able to activate the Visual Editor.

  1. Navigate to your website (for example, northerntrailoutfitters.com)
  2. Click the Salesforce Interactions SDK Extension
  3. Ensure that the "Detected Beacon" section displays your desired account and dataset. (for example, account = training and dataset = nto)
  4. Enable VISUAL EDITOR
  5. Enter your login credentials when prompted

  

Campaign Debugger

The Interaction Studio Campaign Debugger gives you a snapshot of all Interaction Studio activity and data on a page with details, including actions, enabled and disabled web campaigns, and item data. You must be actively logged in to the account you wish to view this information about in your browser in order for this option to function. For more detailed information and instructions for using the Campaign Debugger, please visit the Interaction Studio developer documentation site.


Disable Evergage

While enabled, this option prevents Interaction Studio from initializing locally within your browser on the chosen site. Selecting DISABLE EVERGAGE replaces the existing JavaScript beacon with an empty JavaScript resource. All event receipt, analytics, and messaging will stop immediately and will propagate in minutes as viewers' browser caches expire.

  1. Navigate to your website (for example, northerntrailoutfitters.com)
  2. Click the Salesforce Interactions SDK Extension
  3. Enable DISABLE EVERGAGE. This action replaces the existing JavaScript beacon with an empty JavaScript resource. All event receipt, analytics, and messaging will stop immediately and will propagate in minutes as viewers' browser caches expire.