General Information

How do I install a script in Campus Suite?

Campus Suite has many options for installing third-party scripts ranging from pixels to chat boxes and more. Scripts can be installed site-wide, department-wide, or only on a single page. This article will explain how to install scripts for each of these scenarios.

Getting Started

Obtaining the code and instructions

The first step is to obtain a script from the third-party vendor. This should come with both the script itself as well as any instructions on where inside the website's code the script should be placed. Some scripts are highly dependent upon being placed in the correct area of a website's code, and may not function correctly if they are misplaced. It is important that the vendor be clear on which area of the code the script needs to be placed.

The code areas of a website explained

  • Head Scripts: These scripts will usually have instructions to place them within the <head></head> tags of a website’s code. The head section of code is not the website’s 'header' wherein the logo and primary navigation is placed, rather the <head> area is a structural component of code composition that comes before any actual page content.

  • Top Scripts: These scripts will usually have instructions to be placed 'as close to the opening <body> tag as possible.' These scripts want to be loaded by the visitor as soon as the page content starts. The <body> tag is the start of actual page content, such as the header with logo and primary navigation.

  • Bottom Scripts: These scripts will usually have instructions to be placed at the bottom of the page content so that the script is loaded after the page content.

Placing your script

Campus Suite's HTML Overrides

The HTML Overrides feature in Campus Suite enables script addition. HTML Overrides can be found for site-wide placement, department-wide placement, or page-only placement. The HTML Overrides interface contains three distinct box areas corresponding to the aforementioned page code areas: Head Scripts, Top Scripts, and Bottom Scripts. Script codes can be copied from the third-party vendor’s document and pasted into the specific box referenced by the script’s instructions. Scroll down on the HTML Overrides page to see all of the available script areas.

Where to find the HTML Overrides

Next, we'll take a look at how to access the HTML Overrides for the three scenarios mentioned: site-wide, department-wide, and page-only.

  • Site-wide:

    This will place the script on every page of your website automatically.

    Accessing site-wide HTML Overrides:
    1. Select Websites in the Campus Suite Dashboard

    2. On the following screen click the Gear Icon next to the title of the website

    3. Once the next page loads, choose the HTML Overrides tab near the top.

    4. Paste the code into the specified area, scroll down and click on Save.

  • Department-wide:

    This will limit script placement to only a single department and its sub-departments. This is helpful for when only one school needs a particular tracking script, or when only the Admissions department needs to feature a live chat box for example.

    Accessing department-wide HTML Overrides:
    1. Select Websites in the Campus Suite Dashboard

    2. Navigate to and select the department to enter it

    3. Click on the name of the department at the top to access a drop-down menu

    4. From the drop-down menu, select the Edit Department option

    5. From the tabs at the top, choose HTML Overrides

    6. Paste the code into the specified area, scroll down and click on Save.

  • Page-only:

    This limits script placement to only the specified page and no others.

    Accessing page-only HTML Overrides: 
    1. Navigate to the specific page

    2. Edit the page and click on Content Settings on the left-hand control panel. 

    3. Select the HTML Overrides tab

    4. Paste the code into the specified area, then click Save Content --> Submit for Publication

Support for third-party scripts

Our support for third-party scripts can be limited. This is because we do not control the scripts and our ability to modify them is limited to none. While we will do our best to troubleshoot issues that scripts may cause, we are unable to guarantee that we can alleviate all issues or modify script functionality.