Sync data from Veracross

Market View 6, released in fall 2022, enables schools to sync admissions data from their admission software. This guide walks you through how to set this up.

Overview

Audience

This guide is for schools who are NAIS members, and use Veracross for admissions or application data.

After one person at your school completes this process, the integration will work for everyone at your school. Each user should use their own login. Any NAIS member school can have unlimited staff accounts. Add and manage your school's roster at my.nais.org.

Goal

This integration syncs two types of data from Veracross into Market View.

  1. Applicants. If it exists, we will sync names, grades, addresses, and student IDs for students who applied to your school. Note: applicants need to have an "application date" to be considered applicants for this process.

  2. Enrollments. If it exists, we will sync names, grades, addresses, and student IDs for students who enrolled in your school.

Market View is committed to the highest security of your data. We encrypt all data in transit from your admission software, and any time it is used. We encrypt the data within our database. Your data will never leave our database or be shared. We take data security and privacy extremely seriously. Read more about how Market View protects your data.

Instructions

Step 1: Add Market View to Veracross

This step must be performed by one of your school’s administrators of Veracross, someone with “Oauth_App_Admin” permissions. If you aren’t an admin, feel free to forward these instructions to someone who is. If your admin doesn't see the button to "start integration", they need to go into their permissions and give themselves “Oauth_App_Admin” permission.

Step 2: Add Scopes

Note: this integration doesn't require SSO permissions.

Step 3: Add Veracross details to Market View

Step 4: Connect

Next steps

How it works

Below describes what Market View does to import your data.

  1. Fetch all historical students, applicants, applications, and applicant households

  2. Discard students marked as "applicants" who haven't yet applied (these are usually just prospects)

  3. Match each applicant to an application and household

    1. If a matching application or household can't be found, an import failure is created

  4. Assign a grade level to each applicant

    1. If a grade level doesn't match our list of accepted grades, an import failure is created

  5. Match each student to an applicant

    1. If a matching applicant isn't found (e.g. if the applicant became an import failure), an import failure is created

  6. For each applicant, look up or geocode their address

    1. An applicant's corresponding student is also assigned this address

    2. If an address can't be geocoded, the student and the applicant become import failures

  7. Applicants are separated by year and saved into corresponding "applications" admissions lists

  8. A student can be saved in several "enrollments" admissions lists

    1. A student is saved in the enrollment list for the year of their "entry date", at the grade level from their application ("grade level applied for")

    2. Each year after that, until their "exit date", a student is saved in that year with the next grade level

    3. We assume students are promoted each year, since we don't have grade level information for a student for each year

Get an error? Need more help? Email marketview@nais.org.

Last updated