Integrations

Integration approach

Full Measure has a file based approach to our integrations. We accomplish our data exchange through an FTP, sFTP, or s3 folder. We can build this integration by leveraging Full Measure endpoints and an existing system, which is your CRM, SIS, or other system of record.

Here is an overview of the process-

• Your team creates queries from your CRM, SIS, or other system of record that we treat as a single source of truth
• Your team then exports these queries to a shared virtual folder that Full Measure has access to. This can be an-
  • S3
  • FTP
  • sFTP
• We then meet in the middle with your data
  • Full Measure has processes that pull data from that shared folder in a daily or on a more frequent basis to make sure our system is up-to-date with yours
  • This includes student information, as well as target audiences for communications
• This information displays in our staff and student UI, making this data relevant to you and your end users

File types

This integration consists of two types of data: contact information and audiences.

The contact file is a full list of students and their details. This file should be named "fullmeasure_student.csv" and contain, at a minimum, 5 data elements:

• first_name
• last_name
• contact_id (unique identifier)
• mobile_phone_number
• email

This is what populates student data in our system. Full Measure does not do any interpretation of this file for communication purposes. Those comes through in the audiences.

Audiences consist of contact_ids, or unique identifiers, that are queries run in the system to represent the intended audience. These should only contain one column that is the contact_id. We pull the other information about the student using the contact_id as the mapping, to know which number to send the communication too based on information in the fullmeasure_student.csv file. All students in the audience files must also exist in the fullmeasure_student.csv file. The naming conventions for audiences is "fullmeasure_audience_<name>.csv", i.e. "fullmeasure_audience_inquiries.csv". Please do not change the contact_id after you have established it for the students. If you change the contact_id, you could duplicate your students in our system. In the same way, please do not change the column headers after we have done our initial mapping. Our system may not be able to recognize data values if you continuously change their header names.

What we need from you-

If you're providing the FTP, we need the credentials to access your FTP, sFTP, or S3.

If we're hosting the sFTP, we can provide this information for you. You can add your own data elements to the fullmeasure_student.csv file if you like! However, this will only be for display purposes. For example, if you wanted to add address to your student file, that information will display in the interface. However, we won't deploy logic about this information to extract populations of students in communications. You could add "state" to your fullmeasure_student.csv file and we would display that in the interface, but we could not employ logic based on the values in the .csv to then send a communication targeting students from the District of Columbia. Your team would have to upload a separate audience representing "DC" as a state to run a communication to target that audience.

We also can run return files back to your system of record. These will contain a file of students created and updated, including opt outs. This file can also have two way messages and communication history. If you would like to set up a writeback, please contact your Account Manager to get this process started.

Attached is a file that has more screenshots and information about our integration!

We made a video! Check it out here 

If you have any issues or questions, please submit a ticket.