Finalsite offers a data integration with Ravenna admissions software that pushes constituent data (applicants, prospects) from Ravenna into Finalsite on demand or on a scheduled basis. This enables targeted communications to admissions families using Messages and Workflows.
đź’ˇQuick answers
- What does the Ravenna data integration do? It pushes applicant and prospect data from Ravenna into Finalsite's Constituent Manager, enabling targeted communications to admissions families using Messages and Workflows.
- Is the Ravenna sync one-way or two-way? One-way; data flows from Ravenna into Finalsite only. Changes in Finalsite are not pushed back to Ravenna.
- How often does the Ravenna data sync run? The sync can be configured to run on demand or on a scheduled basis; contact Finalsite Support for the specific configuration options for your integration.
- Is the Ravenna integration available to all Finalsite clients? It is an available integration for schools that use Ravenna; contact your Client Success Manager to set it up as part of your integration configuration.
Finalsite offers a data integration with Ravenna. With this integration, data can be pushed on demand to Finalsite from the Ravenna Admin console.
In this article
Data mapping
The mapping of the data that is imported from Ravenna is detailed here. We make some default mapping decisions, but the integration is highly customizable based on your specific needs.
Important Note
Users from the Ravenna integration will not match on users already in Finalsite. If a user from Ravenna already exists in Constituent Manager, a duplicate user will be created.
An important aspect of the integration is managing the admissions status of users to facilitate filtering and proper Workflow behaviors. For that reason, this aspect is not customizable. When the integration is configured, the following group structure will be generated:
These groups are not editable, and should not be modified in any way. You are able to build out groups utilizing filters based on these generated groups, but these groups serve as the “base” of being able to track an applicant (and their contacts) as they progress through the admissions process.
Managing Ravenna users in Finalsite
We do not expose the users created from the integration for manual management in Constituent Manager, because these users are intended for communication purposes only via Messages/Workflows. These users should not be given accounts to log into for portal access, for example. Users who exist in other roles in Finalsite will not be linked to these users (e.g., a teacher who is already in Finalsite who is also the parent of an applicant will not have the existing account updated via the integration). It is also expected that these users would be purged each “admissions season.”
Ravenna best practices
- Use your Finalsite website to drive interested parties to your Ravenna inquiry form, where they will be “picked up” by the integration.
- Nurture those inquiries using Workflows or Messages and get them to apply using your Ravenna application.
- Follow up with those applicants using Messages or Workflows.
- Create targeted segments with the data you have available to tailor information specifically to the recipient.
Comments
Please Sign in to leave a comment if you don't see the comment box below.