Overview
The RainFocus integration lets Certiverse confirm, in real time at checkout, that a candidate holds a qualifying event pass before they can book an exam. It is a live eligibility provider built on the same connector pattern as Docebo, Cornerstone and ClientAPI eligibility.
The Rainfocus integration is read-only. Certiverse queries RainFocus for the attendee record; nothing is written back to RainFocus. Exam history, results and retake rules stay in Certiverse.
Configuration
Configuration has two parts: create the RainFocus connector, then assign it to each Store Exam via Eligibility Configuration.
Part 1: Create the RainFocus eligibility connector
- Sign in to Certiverse as an Org Admin and open Admin > Connectors.
- Add a new Eligibility listed under Candidate Management Services connector and select RainFocus as the provider.
- Enter a connector name. Names must be unique within the org, across all providers.
- Enter the RainFocus API credentials: domain, token URL, client secret and clientId.
- Validate. Certiverse validates the credentials against RainFocus; the connector is created only if validation succeeds.
- Click Create.
Connector rules:
- A connector assigned to any Store Exam cannot be deleted. Unassign it first.
- Credentials are stored as secrets and are obfuscated after saving.
Part 2: Assign the connector to a Store Exam
- Open Deliver > Store > Store Exams and select the exam to gate.
- In the eligibility settings, choose RainFocus as the eligibility provider.
- Select the RainFocus connector created in Part 1.
- Enter the event code (for example, Conference Pass). Use the package names exactly as they appear in RainFocus.
- Save the Store Exam.
- Repeat for each exam that requires a RainFocus registration eligibility check.
Eligibility checks
A candidate is eligible only when RainFocus returns an attendee record for their email with registered = true and a package type containing a qualifying pass. Certiverse runs this check in real time during checkout.
Match key: the candidate's Certiverse account email is sent to the RainFocus attendee endpoint.
What the check does not do:
- It does not send bookings, results, or completion data to RainFocus.
- It does not replace Certiverse retake rules. A candidate who passes the RainFocus check is still subject to the exam's retake and attempt limits in Certiverse.
Candidate flow
- The candidate registers in RainFocus first
- Then books in Certiverse if eligible; the only RainFocus touchpoint is the live check at checkout in Certiverse.
Email is the only match key, so a candidate who registered in RainFocus with a different email is treated as not found. If the RainFocus API fails, booking is blocked and the error is logged. Be sure to communicate to candidates attempting to register that in order to book, they must use their RainFocus account email address.
Troubleshooting & FAQ
| Symptom | Likely cause | Resolution |
| Connector won't save | Credentials invalid or wrong RainFocus environment | Re-check credentials with the client's RainFocus admin |
| Candidate with a pass is told they're not eligible | Certiverse email differs from RainFocus registration email | Ask the candidate which email they registered with; update the Certiverse account email or the RainFocus record |
| Candidate with a pass is told they're not eligible | Pass name on the Store Exam doesn't match the RainFocus package name | Compare the configured qualifying pass with the package type in RainFocus |
| Candidate is blocked despite paying | Registration not complete (registered = false) | Client confirms registration status in RainFocus |
| All candidates blocked on one exam | Connector unassigned, wrong connector, or RainFocus API error | Check the Store Exam's eligibility settings and the Certiverse error logs |
| Can't delete a connector | Still assigned to a Store Exam | Remove it from every Store Exam first |
Contact Us
If you have any questions or need additional assistance, please contact us by either emailing support@certiverse.com or by submitting a ticket from this article.
Updated
Comments
0 comments
Article is closed for comments.