Plan your integration - StudentPulse documentation

Choose the method that matches your task. Check-in links pass context into StudentPulse. Data exports send feedback data to your reporting tools.

Prerequisites

Access to the target Organization in StudentPulse.
A description of the data you need to send or receive.
A contact who can configure your institution’s source system or reporting tool.

Get started

Your task	Method	What to prepare
Add context before a student opens a Check-in	URL parameters	A Check-in URL and the agreed segmentation keys and values
Analyze feedback with institution data	Data export	Export access for the target Organization and an agreed data mapping
Build a Power BI report	Power BI and Fabric	Power BI Desktop, an export URL, and access to a Fabric workspace
Manage Check-ins from another system	Draft API reference	An API key and confirmation of the current API contract

Confirm the data mapping

For Check-in links, agree which values represent a course, campus, semester, or other reporting category. Your source system can then generate the links. For exports, agree which identifiers connect the feedback data to your institution’s data. Ask StudentPulse about any additional identifier you need.

Test with example data

Use a test Check-in and synthetic data.
Open a generated link and confirm the intended Check-in context.
Submit a test Reply.
After the export refresh, confirm that your reporting tool receives the expected context.

Use your StudentPulse contact to confirm support for integrations that are not described here, including Group synchronization and student identification through UniLogin or Aula.