Table of Contents

Colleges: Scoir Audience Integration with Slate

Customer Support Updated by Customer Support

With the Scoir Audience Integration, your team gains early visibility into student interest well before they inquire or apply. By mapping these behavioral insights directly into Slate, you can personalize engagement, identify stealth audiences, and improve campaign performance with more accurate first source attribution.

This integration protects student privacy while giving you access to stealth audiences you’re not reaching through other channels. It also unlocks the opportunity to message your Scoir followers directly from Slate — offering non-partner institutions a pathway to explore the value of Scoir engagement.

Plus: No separate Scoir subscription is required to activate the integration.

Setup time: Approximately 30 minutes.

📹 See Scoir + Slate in Action

Watch this webinar to discover how Scoir and Slate work seamlessly together to help you engage both stealth and known students, all without leaving Slate.

Connecting your Scoir account in Slate

Navigate to Deliver Configuration in the Database. 

Click Add Account.

Select Scoir from the drop down menu and click Continue.

Give your account a name, like Scoir. Then select the appropriate Scoir Account from the drop-down menu.

Colleges that manage more than one campus account in Scoir in the same instance of Slate will have multiple Scoir Account options and will need to add each campus separately as a new account. Be sure to name each campus account so it’s clear which campus each account relates to.

Select the user who will be the point of contact for Scoir messaging. This can be the same person who is activating the integration, or someone else.

Click Save. 

Activating the Account in Scoir 

After you’ve added your Scoir Account in Slate, you'll be prompted to click through to activate the account in Scoir. This step turns on the flow of data from Scoir to Slate via the Scoir Audience source format; however, you’ll still need to activate the source format to begin receiving the data (see the next step). 

If you’re not already a Scoir user, you can follow the steps on the screen to Request Account. 

Once logged into Scoir, click the Enable Your Follower Import button in Engage > Integrations.

Click Continue.

Enable follow import

If you happen to land on this page before you’ve added your Scoir Account in Slate, you’ll be prompted to go back to Slate to add the account first.

Activate Scoir as a new device type
Colleges that manage more than one campus account in Scoir in the same instance of Slate will need to follow the steps to activate each Slate Account separately in Scoir.  

Mapping and Activating the Scoir Audience Source Format

The Scoir Audience source format is the automated import that contains information on all of the students who have expressed interest in your college in Scoir. When you add the Scoir Account in Slate and activate it in Scoir, the source format is automatically added to your database with some pre-set default mappings.

Navigate to Source Formats in the Database.

Click on the Scoir Audience source format. 

Click Remap.

The pre-set default mappings are shown below. 

The ‘scoirID’ and ‘scoirCollegeID’ source fields are brought in as a new Device on the person record. This Device is one way you’ll be able to identify your Scoir inquiries in Slate, and also serves as the delivery mechanism for Scoir Messages, similar to an email address for an email message, if you decide to send Scoir messages through Slate. 

The ‘engaged’ source field is the field that sets whether the Device value is active or inactive. If one of your interested students decides to unfollow you in Scoir, then the integration will bring in that update as ‘engaged’ = ‘false’ and the Device Priority will be set to Inactive.

If you do not already have a custom field for Scoir ID, you will need to create one and return to the source format Field Mappings to map this field. The custom field must be person-scoped, free text, and unique for merging.

Some of the default mappings are required for the integration to work as intended. Do not adjust the mappings for the following fields:
• scoirID
• scoirCollegeID
• engaged

For matching to work as intended, scoirID must be mapped to your custom Scoir ID field in addition to Device Value.

The source file will also contain an ‘engagementStage’ value for each record. This value lets you know whether the student has indicated in Scoir that they are following, planning to apply to, or have already applied to your college.  

You will need to create a custom field and custom prompts in your database to store Scoir Engagement Stage. 

Scoir Engagement Stage prompt values are Following, Applying, and Applied.

The Scoir Engagement Stage field should be person-scoped and a single-value type.

Navigating back to the Scoir Audience source format, you will then be able to update your source format mapping with the newly created Scoir Engagement Stage field and prompt values. 

You can Append Values and add each of the Scoir Engagement Stage source values to map each to the appropriate destination value as shown in the mapping example above.

Since your followers, including stealth, are true hand-raisers on Scoir, we recommend including a static mapping of the Person Status so that new records are created as Inquiries instead of Prospects.

Then, activate the source format by selecting Active as the status and marking the Remap Active status to Active. It’s critical for the Remap Active status to be Active when activating the source format to avoid records landing in Consolidate Records. 

Once activated, imports will be sent from Scoir to Slate overnight as new followers are added or existing followers are updated.

Record Matching and Creation

In addition to Scoir ID, the import will also look to match to an existing record based on the combination of First/Last/DOB or First/Last/Email. 

Personal information is sent in a hashed format to protect the student’s identity for any record not already known to you. Slate can read the data to identify matching records in your system, but the end user will not be able to decipher it in the file. This is because all of your interested students in Scoir are sent to you, including those who aren’t able to be matched to a record already in your database.

Note: The order of matching logic is:

  • Scoir ID
  • Email address + first + last hash
  • First + last + birthdate hash

This means you’ll have records created by the import for prospective students previously unknown to you. These are created with the name “unknown.” A Scoir ID and a Scoir Device are attached to the record to facilitate identification of Scoir followers and Scoir Messaging, but no other personal information is provided. 

When an unknown person record is created, Slate will store the hashed values for those unknown records, which can then be used for matching purposes by future regular known-value imports and form submissions, and to allow them to then become known records.

Unlocking Scoir Audience Insights

Key to the integration is the ability for you to share information back to Scoir about your Scoir records so that Scoir can provide a more detailed engagement analysis, including accurate first source attribution and demographic insights on your stealth records. 

Data sent includes Deliver Account ID, Person ID, Person Created Date, and a Stealth/Known indicator. 

Add the Scoir Audience Match Results query from the Slate Template Library.

You will need to refresh the Slate Template Library first. 

Navigate to the query and click Edit Query. 

Click on Edit Permissions.

And Edit/Add a Grantee.

Click on the Web Service link. 

Select User Token - Scoir from the Service Account dropdown and copy the complete URL that’s displayed in the box. 

Return back to your account in Scoir, and paste the URL into the box as shown below. Click Unlock Stealth Insights. 

Unlocking stealth insights
Colleges that manage multiple Scoir campus accounts in the same instance of Slate will need to make a copy of the Scoir Audience Match Results query for each campus and paste the unique Web Service URL into each Scoir account separately. 

Once completed, your point of contact at Scoir will send your institution’s Scoir Audience Insights Report.

Working with Scoir Data in Slate

We’ve created a number of pre-built filters and exports you can use to identify and track Scoir inquiries in Slate. You can import these into your Query Library via this Suitcase ID: 

bb84b23b-343e-4d6f-8485-9c9a32cdb9f8:sco

You will need to configure the “Scoir Account Device Type is Active” filter to select your Scoir Account Device Type and Scoir ID to your custom Scoir ID field.

Creating a Scoir Message in Slate

The Scoir Audience integration opens the opportunity to send Scoir messages right from Slate. This is particularly useful for  colleges that aren’t yet using Scoir’s full suite of tools but want to engage with their Scoir students.

Navigate to Deliver and click New Mailing. 

Name your mailing and file it in a folder as with other mailings. Select Scoir as the Deliver Method. Click Save. 

Click Edit Recipient Lists to specify who you want to send the mailing to and to pull any exports you’ll use as merge fields in your message. See Messaging Stealth Records

Click New Query. 

At a basic level, any record with an active Scoir Account Device Type can be messaged in Scoir via Slate. To get started, you might simply filter on the existence of an active Scoir Account Device Type to identify the records in your system that are eligible to be messaged in Scoir. 

You might also want to identify and distinguish between the followers that were matched to records already in your system vs. the stealth followers that are otherwise unknown to you. See the Working with Scoir Data in Slate section above for help with the use of filters when building a recipient list. 

When configuring your recipient list query, Scoir Recipient must be an included export. This is the Scoir Account Device that will be used in the ‘To’ field when building your message. You may wish to include additional exports if you plan to include merge fields in your message for personalization. See Messaging Stealth Records

The Scoir Recipient export will require configuration. This is because some colleges may have multiple Scoir Account Devices if they manage more than one campus in the same instance of Slate. Everyone must specify the Scoir Account Device for the Scoir Recipient export even if you only have one. 

After you’ve configured your recipient list query, you can begin drafting your message.

You’ll find a simplified message editor that supports all of the capabilities for building a Scoir message. The Recipient field is a drop-down menu that will include each Scoir Account Device included in your recipient list query exports. The Account you choose corresponds with the Scoir profile you wish for the message to be sent from. Most colleges will only have one. 

If you included additional exports in your recipient list query, the message editor does support the ability to add merge fields. See Messaging Stealth Records 

Insert a pair of double brackets anywhere in your message where you wish to insert a merge field. For the subject line, you must manually type in the brackets and name of the field export as it appears in your recipient list query. Click Save. 

When you go back into the message editor, you’ll be able to double click on each set of brackets in the message body and select your merge field from the dropdown.

Messaging Stealth Records

Use caution when including merge fields in messages that include stealth record recipients. In most cases, you will only know the Scoir ID, high school information, and Scoir Engagement Stage for these students. Including merge fields for data not available for a record will result in blank content being displayed in the message for that student. 

Inserting a Message in a Campaign

Scoir messages can be built as stand alone messages or be included as part of your existing campaigns. To include Scoir messages in a campaign, simply insert the message in the mix wherever you’re interested in utilizing this channel. It’s not necessary to create separate campaigns for Scoir followers. Folding these messages into existing campaigns reduces the risk of sending duplicate or overlapping messages to the same students. 

Fast forward to 30:10 in this webinar for practical tips on setting up Scoir campaigns in Slate

Questions?

Email Scoir Product Manager and Slate expert, Ashley Murphy with any questions about the integration: amurphy@scoir.com.

How did we do?

For Colleges: Troubleshooting Slate integration with Scoir

Contact