|
AgileInsight General Instructions - Sept 2024
AgileInsight Instructions AgileInsight allows users to run a matching process, between a client-provided file or files containing Institutions and/or Personnel data, and Agile's data on Institutions and/or Personnel. This provides the client with information such as available records about their target marketing audience. Use the following instructions to upload files, map fields and run data verification, and submit a match process to receive information on your data. Account Login: https://insight.agile-ed.com/ Enter a username and password provided by your Agile account manager. Once logged in, you will be sent a multi-factor authentication (MFA) code to your email, which then you will enter on the next page after entering a username and password. Once entered and valid, any match orders you create will be saved, and those orders will be available to you for reference and/or downloading of matched files.
Setup Order for Matching Order Setup Flow (Wizard) Use the wizard to walk through the steps of setting up your order for matching. The steps are detailed below. Basic Info Enter a description of the order. File Upload Select a Match Type for the order: Institution Match - Select this option if the single file you're uploading contains only Institution information. Personnel Match - Select this option if the single file you're uploading contains only Personnel information. Institution and Personnel Match (two related files) - Select this option if you're uploading 2 files: 1 containing Institution information, 1 containing Personnel information. Personnel Match - with institution information (single file) - Select this option if the single file you're uploading contains both Institution and Personnel information.
For ConnectLink matches: Match accounts and contacts together in an Institution and Personnel Match (two related files). If you use leads, match them in a separate Personnel Match, with institution information (single file).
There are 2 options for uploading file(s): Select and hold the file(s) from your machine, and drag the icon into the uploading box shown on the screen. Click 'Upload File(s)' to select the file(s) from your machine.
Once the file(s) are selected, a progress bar will display each file selected for upload, displaying the progress of uploading the file.
There is an option to remove the uploading file in progress, displayed with a red X. After the file(s) are uploaded, the following displays for each file: Filename Preview of parsed fields - a dropdown displays when clicked, a list of the fields in the file is shown. Delete - option to remove the file
There is also an Expiration Date field to set for the order. The expiration date is used for removing client data that has been in our system for over 30 days, in line with our data security policy.
Field Mappings Here the user will map the Agile fields (Required, Strongly Recommended or Recommended) with the fields found in the client's file(s) (list of fields displayed in each dropdown).
Two sections of fields display (one Institution, one Personnel), except for an order whose Content Type is Institution Only, in which case only the Institution fields will display for mapping. The user can also specify which file to use for each section for the list of fields in the client's file, namely for the case when the order's Content Type is Relational. The following fields in the file(s) are either required, strongly recommended, recommended or optional: The Required fields are required to be mapped to continue. The Strongly Recommended fields are not required, but are very helpful to the match process to return as many matched results as possible. The Recommended fields are not required but are also helpful to the match process to return extra matched results that would not be possible without mapping the field. The optional fields are not required, but the field is helpful to the match process to return even more extra matched results.
Institution Field Name | Description | Required |
| Institution Name | Name of Institution | Address Line 1 | First line of mailing address | State | Mailing state | Zip | Mailing zip | Strongly Recommended | Phone | Phone number for Institution | IPEDS ID | Integrated Postsecondary Education Data System Id | Website URL | URL for Institution's website | NCES School Id | School National Center for Education Statistics Id |
Field Name | Description | NCES District Id | District National Center for Education Statistics Id | Recommended |
| Institution Type | District, school, or college | Secondary Address Line 1 | First line of secondary address | Secondary State | Secondary mailing state | Secondary Zip | Secondary mailing zip | City | Mailing city | Secondary City | Secondary mailing city | Agile Institution UID | Provide if your data has been matched by Agile before | Agile Parent UID | Provide if your data has been matched by Agile before | Optional |
| Address Line 2 | Second line of mailing address | Secondary Address Line 2 | Second line of secondary address | Country | Mailing country | Email Domain | Email domain | Client Full Mailing Address | Full mailing address of the account | Client Full Secondary Address | Full secondary address of the account |
Personnel Field Name | Description | Required |
| First Name | First name of individual | Last Name | Last name of individual | Strongly Recommended | Client Personnel ID | Unique identifier for personnel | Email Address | Email address for personnel | Recommended |
| Phone Number | Phone number for personnel | Agile Personnel UID | Provide if your data has been matched by Agile before | Optional |
| Address Line 1 | First line of mailing address | State | Mailing state | Zip | Mailing zip | Institution Name | Name of linked institution | Prefix | Mr, Mrs, Dr, etc. | Middle Name | Middle name of individual | Suffix | Jr, Sr, etc. | Address Line 2 | Second line of mailing address | City | Mailing city |
Field Name | Description | Client Full Name | Full name of the individual | Client Account Full Address | Full address of the institution associated to the contact |
The following field has the below precedence depending on the order's selected content type: Client Institution ID - Client Supplied Unique Identifier for Institution Relational: Required - This field can contain relational keys which link the two files provided together. Institution-Only and Combined: Recommended
Verification The fields that were mapped will display on this step, along with data verification rules that will be applied when the user clicks 'Run data verification'. Once that is done, data verification will run on each of these fields, and return a status of the data verification result.
Below are the data verification result types: Failed - This field failed the data verification rule. The application will not allow the user to proceed until the data is corrected for the field. Warning - This field has a warning on the data verification rule to be corrected, but the application will allow the user to proceed. Passed - This field passed the data verification rule.
The message below the data verification rules will tell the user whether the overall validation has succeeded or failed.
Review All the selections made are displayed for review, as well as some sample data to show a preview of what will be included in the match.
Click 'Start Match' to start the matching process. A message will display stating the match process has started. The user will receive an email when the match process for the order is complete. This process can take from a few minutes to several hours, depending on the number of records the process is working with. Data Health Report
Once the match process is completed, a Data Health Report link will be displayed next to the order on the main page. When clicked, the user is taken to a page showing the data behind the matched records.
|
