Gaggle has been supporting student safety and well-being for more than 20 years. The pioneer in helping K-12 districts manage student safety on school-provided technology. This lesson provides the Business Rules for the Gaggle export Zap.
Before you Begin
Need a refresher on installing a Zap? Visit to Pre-Built Export Zaps learn more.
Business Rules
This is a single output file and will be named gaggle.csv and is a double quote csv.
The regular filters for School, Grade, Subject will be made available by default.
| Gaggle Headers | Comments as listed in Gaggle Document | eSD Comment |
|---|---|---|
| studentId | From Inside the SIS | Available and being sent |
| districtCode | From Inside the SIS | Blank being sent |
| districtName | Should be human readable | Yes it is a alphanumeric value |
| schoolCode | From Inside the SIS | Available and being sent |
| schoolName | Recommended | Available and being sent |
| studentFirstName | Recommended | Available and being sent |
| studentMiddleName | Recommended | If available being sent |
| studentLastName | Recommended | Available and being sent |
| studentStatus | We are sending the word "Active" since we only send active students | |
| studentGrade | Actual Student Grade - it can be alpha numeric | |
| studentBirthDate | Optional, but when given must be in this format mm/dd/yyyy | Date of Birth being sent in the format mm/dd/yyyy |
| studentEmailHome | Student in eSD has only one email that is being sent in the subsequent field which seems to be very important for Gaggle | |
| studentEmailSchool | Comment says: The only field that must match data in Gaggle is the student school email. | Student Email in eSD is not a required field, we cannot guarantee it will match data in Gaggle, we will send whatever is stored in the Student Email field. It will be up to the district to send appropriate information to Gaggle |
| studentPhone1 | Primary Phone Number for the student | This we consider in eSD to be the Cell Phone Number and if that number is blank this field will be blank |
| studentPhone2 | We are sending the Home Phone of the Student just as an additional information | |
| studentPhone3 | Blank being sent | |
| studentAddressLine1 | Recommended | Primary Residence Address being sent |
| studentAddressLine2 | Apartment number lot number etc | |
| studentAddressCity | Recommended | Primary Residence City being sent |
| studentAddressState | Recommended | Primary Residence State being sent |
| studentAddressZipCode | Recommended | Primary Residence Zip Code being sent |
| Guardian1AddressLine1 | Primary Guardian Address (deciphered as Contact Priority 1 or highest priority (for example the guardian itself has 2 and the guardian has both custodial and correspondence then the guardian with priority 2 will be considered as primary) | |
| Guardian1AddressLine2 | Apartment number lot number etc for the same person listed above | |
| Guardian1AddressZipCode | ZipCode for the same person listed above | |
| Guardian1AddressCity | City for the same person listed above | |
| Guardian1AddressState | State for the same person listed above | |
| Guardian1FirstName | Name for the same person listed above | |
| Guardian1MiddleName | Name for the same person listed above | |
| Guardian1LastName | Name for the same person listed above | |
| Guardian1Relationship | Relationship for the same person listed above | |
| Guardian1Email | Email for the same person listed above | |
| Guardian1PhoneCell | Cell for the same person listed above | |
| Guardian1PhoneWork | Work for the same person listed above | |
| Guardian1Phone1 | This might be repeated because in eSD phone types are stored and it may be a cell, work or Home, what we will be sending here is the Phone for the person above which has Priority 1 | |
| Guardian1Phone2 | This might be repeated because in eSD phone types are stored and it may be a cell, work or Home, what we will be sending here is the Phone for the person above which has Priority 2 | |
| Guardian1Phone3 | This might be repeated because in eSD phone types are stored and it may be a cell, work or Home, what we will be sending here is the Phone for the person above which has Priority 3 | |
| Guardian2AddressLine1 | Second Guardian Address (deciphered as Contact Priority 2 or highest priority (for example the guardian itself has 3 and the guardian has both custodial and correspondence then the guardian with priority 2 will be considered as primary and this will be considered second) | |
| Guardian2AddressLine2 | Apartment number lot number etc for the same person listed above | |
| Guardian2AddressZipCode | ZipCode for the same person listed above | |
| Guardian2AddressCity | City for the same person listed above | |
| Guardian2AddressState | State for the same person listed above | |
| Guardian2FirstName | Name for the same person listed above | |
| Guardian2MiddleName | Name for the same person listed above | |
| Guardian2LastName | Name for the same person listed above | |
| Guardian2Relationship | Relationship for the same person listed above | |
| Guardian2Email | Email for the same person listed above | |
| Guardian2PhoneCell | Cell for the same person listed above | |
| Guardian2PhoneWork | Work for the same person listed above | |
| Guardian2Phone1 | This might be repeated because in eSD phone types are stored and it may be a cell, work or Home, what we will be sending here is the Phone for the person above which has Priority 1 | |
| Guardian2Phone2 | This might be repeated because in eSD phone types are stored and it may be a cell, work or Home, what we will be sending here is the Phone for the person above which has Priority 2 | |
| Guardian2Phone3 | This might be repeated because in eSD phone types are stored and it may be a cell, work or Home, what we will be sending here is the Phone for the person above which has Priority 3 | |
| Guardian3AddressLine1 | Third Guardian Address (deciphered as Contact Priority 2 or highest priority (for example the guardian itself has 4 and the guardian has both custodial and correspondence then the guardian with priority 2 will be considered as primary and guardian with priority 3 will be considered 2 and this will be considered third and so on the logic is repeated for the numeric guardians) | |
| Guardian3AddressLine2 | Apartment number lot number etc for the same person listed above | |
| Guardian3AddressZipCode | ZipCode for the same person listed above | |
| Guardian3AddressCity | City for the same person listed above | |
| Guardian3AddressState | State for the same person listed above | |
| Guardian3FirstName | Name for the same person listed above | |
| Guardian3MiddleName | Name for the same person listed above | |
| Guardian3LastName | Name for the same person listed above | |
| Guardian3Relationship | Relationship for the same person listed above | |
| Guardian3Email | Email for the same person listed above | |
| Guardian3PhoneCell | Cell for the same person listed above | |
| Guardian3PhoneWork | Work for the same person listed above | |
| Guardian3Phone1 | This might be repeated because in eSD phone types are stored and it may be a cell, work or Home, what we will be sending here is the Phone for the person above which has Priority 1 | |
| Guardian3Phone2 | This might be repeated because in eSD phone types are stored and it may be a cell, work or Home, what we will be sending here is the Phone for the person above which has Priority 2 | |
| Guardian3Phone3 | This might be repeated because in eSD phone types are stored and it may be a cell, work or Home, what we will be sending here is the Phone for the person above which has Priority 3 | |
| ec1AddressLine1 | Emergency Contacts - in eSD Emergency contacts are contacts who are not guardians (sometimes they will be guardians depending on what the school decides), will be the person who has the highest priority in terms of contact priority for the type Emergency Contacts. In eSD addresses are NOT required for EC, so sometimes if it is not entered in the system these fields will be blank | |
| ec1AddressLine2 | In eSD addresses are NOT required for EC, so sometimes if it is not entered in the system these fields will be blank | |
| ec1AddressZipCode | In eSD addresses are NOT required for EC, so sometimes if it is not entered in the system these fields will be blank | |
| ec1AddressCity | In eSD addresses are NOT required for EC, so sometimes if it is not entered in the system these fields will be blank | |
| ec1AddressState | In eSD addresses are NOT required for EC, so sometimes if it is not entered in the system these fields will be blank | |
| ec1FirstName | First Name of the same person listed above | |
| ec1MiddleName | Middle Name of the same person if available | |
| ec1LastName | Last Name of the same person listed above | |
| ec1Relationship | Relationship for the same person listed above | |
| ec1Email | Email for the same person listed above | |
| ec1PhoneCell | Cell phone if available | |
| ec1PhoneWork | Work for the same person listed above | |
| ec1Phone1 | This might be repeated because in eSD phone types are stored and it may be a cell, work or Home, what we will be sending here is the Phone for the person above which has Priority 1 | |
| ec1Phone2 | This might be repeated because in eSD phone types are stored and it may be a cell, work or Home, what we will be sending here is the Phone for the person above which has Priority 2 | |
| ec1Phone3 | This might be repeated because in eSD phone types are stored and it may be a cell, work or Home, what we will be sending here is the Phone for the person above which has Priority 3 | |
| ec2AddressLine1 | Emergency Contacts - in eSD Emergency contacts are contacts who are not guardians (sometimes they will be guardians depending on what the school decides), will be the person who has the second highest priority in terms of contact priority for the type Emergency Contacts. In eSD addresses are NOT required for EC, so sometimes if it is not entered in the system these fields will be blank | |
| ec2AddressLine2 | In eSD addresses are NOT required for EC, so sometimes if it is not entered in the system these fields will be blank | |
| ec2AddressZipCode | In eSD addresses are NOT required for EC, so sometimes if it is not entered in the system these fields will be blank | |
| ec2AddressCity | In eSD addresses are NOT required for EC, so sometimes if it is not entered in the system these fields will be blank | |
| ec2AddressState | In eSD addresses are NOT required for EC, so sometimes if it is not entered in the system these fields will be blank | |
| ec2FirstName | First Name of the same person listed above | |
| ec2MiddleName | Middle Name of the same person if available | |
| ec2LastName | Last Name of the same person listed above | |
| ec2Relationship | Relationship for the same person listed above | |
| ec2Email | Email for the same person listed above | |
| ec2PhoneCell | Cell phone if available | |
| ec2PhoneWork | Work for the same person listed above | |
| ec2Phone1 | This might be repeated because in eSD phone types are stored and it may be a cell, work or Home, what we will be sending here is the Phone for the person above which has Priority 1 | |
| ec2Phone2 | This might be repeated because in eSD phone types are stored and it may be a cell, work or Home, what we will be sending here is the Phone for the person above which has Priority 2 | |
| ec2Phone3 | This might be repeated because in eSD phone types are stored and it may be a cell, work or Home, what we will be sending here is the Phone for the person above which has Priority 3 | |
| ec3AddressLine1 | Emergency Contacts - in eSD Emergency contacts are contacts who are not guardians (sometimes they will be guardians depending on what the school decides), will be the person who has the third highest priority in terms of contact priority for the type Emergency Contacts. In eSD addresses are NOT required for EC, so sometimes if it is not entered in the system these fields will be blank | |
| ec3AddressLine2 | In eSD addresses are NOT required for EC, so sometimes if it is not entered in the system these fields will be blank | |
| ec3AddressZipCode | In eSD addresses are NOT required for EC, so sometimes if it is not entered in the system these fields will be blank | |
| ec3AddressCity | In eSD addresses are NOT required for EC, so sometimes if it is not entered in the system these fields will be blank | |
| ec3AddressState | In eSD addresses are NOT required for EC, so sometimes if it is not entered in the system these fields will be blank | |
| ec3FirstName | First Name of the same person listed above | |
| ec3MiddleName | Middle Name of the same person if available | |
| ec3LastName | Last Name of the same person listed above | |
| ec3Relationship | Relationship for the same person listed above | |
| ec3Email | Email for the same person listed above | |
| ec3PhoneCell | Cell phone if available | |
| ec3PhoneWork | Work for the same person listed above | |
| ec3Phone1 | This might be repeated because in eSD phone types are stored and it may be a cell, work or Home, what we will be sending here is the Phone for the person above which has Priority 1 | |
| ec3Phone2 | This might be repeated because in eSD phone types are stored and it may be a cell, work or Home, what we will be sending here is the Phone for the person above which has Priority 2 | |
| ec3Phone3 | This might be repeated because in eSD phone types are stored and it may be a cell, work or Home, what we will be sending here is the Phone for the person above which has Priority 3 |