Automated Subscriber Uploads allow your institution to securely sync subscriber data — typically students — from your Student Information System (SIS) into uConnect. This integration allows your team to:
Email students directly from uConnect
Segment communications
Track student engagement with career-related content
While most institutions upload student data, you may also include alumni, faculty, and staff in your file. Manual uploads remain available at any time and are not impacted by automation.
Lastly, you can manage the entire SIS file set up process within the uConnect platform itself so you have full control over your file's mapping, syncing, and additional settings.
Overview of the Setup Process
Setting up automated uploads includes:
Confirm if SIS is already enabled in your uConnect platform
Coordinate with IT to prepare your file
Begin the automated upload process in uConnect
Upload the file to your secure S3 bucket
Complete field mapping and activate the sync
Step 1: Confirm Whether SIS Is Already Enabled
Navigate to:
Engage > Subscribers > Subscriber Upload Log. Check the User column and follow the next steps below:
If you see “System-SIS Bridge” under the "User" section of your Subscribers Upload Log section, automation is already active. If you need to make changes to this existing SIS file, coordinate with IT and submit a support ticket. The uConnect support team will help you make any additional changes.
If there is not an active SIS within this section, continue reading and follow the remaining steps!
Important: If you already have an active SIS integration with uConnect, our support team has to help you make edits to the file configuration or sync settings on your behalf. For any new SIS integrations that are set up moving forward, they can now be managed within uConnect.
Step 2: Coordinate With Your IT Team
Your IT department (or data team) must generate a recurring SIS file in CSV format.
They will need to:
Review formatting requirements
Determine which fields to include
Configure automated recurring uploads
Overwrite the existing file with each upload (when applicable)
Combine multiple populations (undergrad, grad, alumni) into one single file if applicable
uConnect processes only one file. If uploading multiple user populations, include them in a single list and add a field (e.g., USER_TYPE or STUDY_LEVEL) to distinguish them. A user may only appear once in the file. Duplicate records (same email or ID) are not allowed.
Use the below email template to reach out to your IT Contact to get started!
Email Template to IT
Subject: Request for SIS Integration Setup for uConnect
Hi [IT Team / Name],
Our office uses uConnect to power our career center website and manage targeted student communications. We are implementing an automated Student Information System (SIS) integration. We are requesting assistance creating a recurring student subscriber file in CSV format that meets uConnect’s formatting requirements. Here is uConnect's documentation (share this article!).
Required fields include:
FIRST_NAME
LAST_NAME
EMAIL
USER_ID or USER_LOGIN (if SSO is enabled or email is not persistent)
GRADUATION (4-digit year format, e.g., 2025)
STAKEHOLDERS (e.g., Undergraduate, Graduate, Alumni — one value per user)
Optional fields may also be included. Once the file is ready, I will initiate the automated upload process in uConnect and forward secure S3 bucket credentials for submission. Please let me know if you have any questions!
Thank you,
[Your Name]
Step 3: Begin the Automated Upload Process
Navigate to:
Engage > Subscribers > Automate Subscriber Uploads
Select Begin Automatic Subscriber Uploads Process
This will:
Create a secure Amazon S3 bucket
Send you an instructional email that you can forward to your IT team
Provide a secure link to generate S3 credentials (valid for 7 days)
Note: Automating uploads does not prevent manual uploads.
Step 4: IT Uploads the File to S3 Bucket
Your IT team will:
Generate S3 credentials
Configure automated uploads to your assigned S3 bucket
Ensure each upload overwrites the previous file
Important:
The file must include a header row and at least one data record
If the file is empty, it will not be processed
The sync runs weekly (Saturday night) by default but you can choose daily.
You cannot complete setup until the first file is uploaded.
Step 5: Configure Automation Settings in uConnect
Once the first file has been uploaded, return to:
Engage > Subscribers > Automate Subscriber Uploads
Configure the following items:
Status
Toggle to Active to enable ongoing syncs.
File Name
Select your SIS file.
Sync Frequency
Weekly (recommended)
Daily
Auto Deprovision
If enabled, users not included in the latest file are removed.
Email Frequency
Optionally auto-enroll subscribers in a selected email cadence.
Academic Year Start Date
Select the month/day your academic year begins. This determines class year progression.
Step 6: Map Your SIS File Fields
After selecting your file, map your CSV headers to uConnect fields.
Required Fields
Your CSV must include:
FIRST_NAME
LAST_NAME
EMAIL
USER_ID or USER_LOGIN
GRADUATION
STAKEHOLDERS
Optional fields will appear if included.
Once required mappings are complete and Status is set to Active, your automated SIS sync is live. Please refer to our SIS sample file template below!
How to Format Your SIS File
Your file must:
Be in CSV format
Meet RFC 4180 standards:
Comma-separated values
One row per line
Fields containing commas enclosed in double quotes
Example:
student_id,first_name,last_name,email,major
12345,Alex,Morgan,alex.morgan@example.edu,Biology
67890,"Taylor, Jr.",Lee,taylor.lee@example.edu,Chemistry
Field Overview
Required Fields
Field | Example | Notes |
FIRST_NAME | Michael | Required |
LAST_NAME | Scott | Required |
Required | ||
USER_ID or USER_LOGIN | mscott or 920182232 | Required unless EMAIL is persistent and matches SSO |
GRADUATION | 2025 | 4-digit year. Required if using class year segmentation |
STAKEHOLDERS | Undergraduate | One value per user |
Unique Identifier Requirements
Each user must have a persistent unique identifier.
If SSO is enabled:
USER_ID or USER_LOGIN must match the SSO attribute passed during login
This prevents duplicate users
EMAIL may serve as the unique identifier only if:
It is persistent
It matches the email passed via SSO
A user may only appear once in the file.
Optional Fields
Field | Purpose |
EMAIL_OPT_OUT | Opt user out of all email (YES, TRUE, or 1) |
DELETE | Delete an existing user (YES, TRUE, or 1) |
PROGRAM | Used to map programs of study to Career Communities |
AFFINITY | Example of additional community mapping field |
Community Mapping Rules
Community fields allow subscribers to be associated with uConnect Communities.
Important rules:
1 extra column per Community Group
One field can map to only one Community Group
Multiple values must be separated by a semicolon
You cannot map combinations of values to a single community
If headers or values don’t match existing Community names, provide a mapping document
Example:
INDUSTRY | AFFINITY | ACADEMIC_COLLEGE |
Manufacturing | FirstGen;Military | College of Engineering |
Graduation Field Notes
Provide a 4-digit year (e.g., 2025)
If full date is provided, uConnect defaults to 8/31 as cutoff (customizable)
Required only if class year segmentation is used
Stakeholders Field Notes
Required if you segment users by study level or audience type.
Each user may only have one value (e.g., Undergraduate OR Graduate OR Alumni).
Email Preference Behavior
If a user has previously:
Opted out of email, or
Customized their email preferences
Those settings remain unchanged during SIS sync.
Additional Technical Notes
Only one file can be processed
Each upload must overwrite the previous file
File must contain at least one data record
Sync runs weekly by default (Saturday night)
Need Help?
If you have any questions or need assistance with setup, feel free to contact the uConnect support team—we’re here to help ensure a smooth and successful SIS integration.