We consume two different types of files in the FTP/sFTP/s3: fullmeasure_student and fullmeasure_audience_<<name>> files. We populate the database with the fullmeasure_student file. This file has the headers of first_name, last_name, contact_id, mobile_phone_number, and email. Think of the fullmeasure_student file, with the headers and student contact information, as simply a way to populate the FME system with student data for search purposes in the interface. We do not run any communications based on this file alone, it is only to add student information to our system. The audience files are what we use to run communications. The audience files are produced from queries written by your institution, there is no interpretation by Full Measure. We then run our managed communications only to the contact_ids in those csvs.
There are two sample files below that I hope will help explain this concept. One is the fullmeasure_student file which has all of the detailed student information in it. The other is an example audience files: "last names that start with E".
The naming convention here is very important. The full student file must be named "fullmeasure_student.csv". The audience files can contain anything after "audience_" except punctuation besides underscores. Spaces, periods, and slashes will break the integration.