Overview

An assessment session represents a single instance of a user completing the Begini Psychometric Assessment.

Each session is uniquely identifiable and is used to capture behavioural data, generate results and link those results back to a specific user within your system.

Sessions can be created using either a no-code approach (Link Generator) or via API integration.

Why sessions matter

Every assessment must be tied to a session to ensure:

• Results can be linked to the correct user
• Data can be tracked and analysed consistently
• Duplicate or conflicting records are avoided
• Outputs can be integrated into your workflow

A well-structured session setup is critical for reliable data and accurate decisioning.

Session components

Each assessment session typically includes:

Deployment

Defines how the assessment is configured, including:

• Assessment structure
• Branding and user experience
• Scoring configuration

You must select the correct deployment when creating sessions.

Unique ID

A unique identifier assigned to each user or application.

This is used to:

• Link results back to your system
• Track users across sessions
• Maintain consistency in your data

For more detail, see:

• Integration ID & Unique ID Guide

Session link

A unique URL generated for each session.

This is what the user interacts with to complete the assessment.

Creating sessions (No-code: Link Generator)

The Link Generator in Beacon is the fastest way to create sessions without any development work.

Steps

1. Navigate to the Link Generator in Beacon
2. Select the appropriate deployment
3. Enter the number of sessions you want to create
4. Assign Unique IDs (if required)
5. Generate the links
6. Download or copy the generated links

Each generated link represents a single assessment session.

Creating sessions (API integration)

For integrated workflows, sessions can be created programmatically using the Begini API.

This allows you to:

• Create sessions dynamically during your application flow
• Pass user identifiers directly from your system
• Control session creation at scale

A typical API-based session creation includes:

• Integration ID
• Unique ID
• Deployment reference
• Optional metadata

For full implementation details, see:

• Integration Overview

Best practices for session creation

To ensure clean and reliable data:

• Always use a consistent and unique identifier per user
• Avoid reusing the same Unique ID across different users
• Clearly separate test and production environments
• Ensure the correct deployment is selected
• Keep session creation aligned with your internal workflow

Common mistakes to avoid

• Using non-unique or duplicated identifiers
• Mixing test and production data
• Selecting the wrong deployment
• Generating links without tracking identifiers
• Creating sessions outside of your intended workflow

These issues can lead to mismatched results or unusable data.

What happens after session creation

Once a session is created:

1. The user accesses the session link
2. The user completes the assessment
3. Behavioural data is captured
4. Begini processes the session
5. Results are generated

Results can then be:

• Viewed in Beacon
• Retrieved via API
• Delivered via webhooks

Tracking and managing sessions

Sessions can be monitored within Beacon, where you can:

• View completion status
• Review individual results
• Track overall activity

This helps ensure your assessment flow is working as expected.

Next steps

Now that you understand how to create sessions, the next step is to understand what happens during the assessment and how data is captured.

See:

• How Behavioural Data is Captured
• Understanding Assessment Results