How does Coassemble track who takes my training?

# How does Coassemble track who takes my training?

It depends on whether learners are identified. Anyone can take a course as an Anonymous Recipient, and you'll see aggregate data like views, drop-off, completion and sentiment. If learners are captured as Identified Recipients, you also get per-person data: who started, who finished, how long they spent, and how they scored. Identifying learners is a paid-plan capability.

Coassemble splits the people who take your training into two kinds, and which one you're dealing with decides how much you can see.

## Identified Recipients and Anonymous Recipients

An **Anonymous Recipient (AR)** opens a course without their identity being captured. Their activity still counts, but it isn't tied to a real person. In your individual usage list they show up under a random name like "Brown Tiger" rather than a real identity.

An **Identified Recipient (IR)** has had their identity captured, usually an email address, when they accessed the course. Their activity is recorded against them by name, so you can see exactly what that person did. Coassemble uses Identified Recipients as the measure of who actually engaged with your content.

## What you can see for each

For Anonymous Recipients, you get the aggregate picture: the number of views, the progression funnel showing where people drop off, completion rates, and course sentiment. This is available on every plan.

For Identified Recipients, you also get per-person data: who started, who completed, how long they spent, and how they scored on any quizzes, and you can download it as a CSV for your records or to roll up into other systems. This individual-level reporting depends on identifying your learners, which is a paid-plan capability.

## How recipients get identified

There are a few ways to capture identity when you share a course, including asking for an email address before someone can open it, building a list ahead of time of who's allowed in, or capturing identity through Slack when you share that way. Once a recipient is identified by one of these, they become an Identified Recipient and their activity is tracked against them.

## Tracking Anonymous Recipients reliably

When recipients aren't identified, Coassemble works out unique people as best it can from their device, browser and session. That has limits worth knowing: there's no perfect way to count unique people while keeping them fully anonymous, especially on shared devices. If two people use the same device without separate identification, their activity can be counted together. The reliable way to tie activity to a specific person is to collect an email or identifier, which turns them into an Identified Recipient and by definition reduces anonymity.

## Tracking in your own product (Embed)

If you deliver learning through Embed, you identify each recipient with a stable identifier from your own system when you request the embed, so activity is tracked against your users without them needing a Coassemble account. A separate identifier can scope a recipient to a specific tenant. You can then read progress, completion and quiz data through the tracking API, and manage recipient identities through the identities API, to bring results into your own product.

## Frequently asked questions

### Can I track learners without identifying them?

Yes, at an aggregate level. You'll see views, drop-off, completion and sentiment for Anonymous Recipients on any plan. To see what specific people did, you need to capture them as Identified Recipients.

### Why do some recipients show up with names like "Brown Tiger"?

Those are Anonymous Recipients whose identity wasn't captured. Coassemble gives them a random placeholder name instead of a real one.

### How do I see per-person completion and scores?

Capture your learners as Identified Recipients when you share the course, then their individual progress, completion and quiz scores appear in your reports and can be exported as CSV. Per-person reporting is a paid-plan capability.

### Can I tie recipient activity to my own user accounts?

Yes, with Embed. You pass your own identifier when you load the embed, so activity is tracked against your users as Identified Recipients, and you read it back through the tracking API.

Learners & tracking

Course analytics

Link analytics

SCORM usage

Reporting FAQ

Quiz results

Sentiment

Collection analytics

Analytics overview

Report dashboard

Webhooks

API events

Write data back via MCP

Where results go

Getting started in 5 minutes

What is Coassemble?

Terminology

Workspace tour

Getting started FAQ

Sign up

Coassemble as an LMS

Migrate from other tools

Getting started

Supported file types

Create from a document

Create options compared

Cloud storage

Create from slides

Sources overview

Sources you build from

Folders

Creators

Transfer ownership of your workspace

Common questions: Workspaces

Managing account, workspace, and billing settings

Workspace management

Course Collections

Collections overview

Courses overview

End-user (learner) experience

Screens

Brand kit

Create from scratch

The Finish screen

Quizzes

Languages

Media: images

Which screen to use

Create a course

Course creation FAQ

Media: video

Publish a course

Themes

Manage & edit courses

Content curation

White-labeling

AI course creation

Custom fonts

Asset library

What you can build

Course links & access

Publish & share

Share to Slack

SCORM export

Sharing FAQ

Shareable templates

Email invitations

Custom domain

Embed in your product

Deploy via MCP

Where training goes

Flow

Pulse

Embed Core

Embed Automate

Embed Partner

Overage & rates

Usage limits

Payments & billing

Plans & pricing overview

Plan changes

Plans & billing

Explore best practices for sharing your knowledge.

Build the business case for Coassemble

Assessment: Best practice for quizzes

Best practices

SCORM files not loading

SCORM session errors on Apple devices

Why isn't my Embed screen working?

Common questions: Troubleshooting

What do I do if there is a bug?

Troubleshooting

Security & SOC 2

Accessibility

Our approach to AI

AI & data security

Trust

Loom

Stripe

Notion

YouTube

HubSpot

Arcade

Vimeo

Unsplash

360Learning

aNewSpring

Docebo

Integrations overview

Slack

Connect with the API

Connect your AI model

Integrations

Release notes

Updates

Resources specifically for Embed (previously referred to as Headless course creation). These are resources that previously lived on the Headless Resources Hub.

Coassemble Embed Partner Security, Data Protection & AI FAQ

Default usage caps for clients

Managing tenant caps

Accessibility guide

AI and Data Security for Coassemble Embed Partners

Coassemble vs. Articulate: Feature comparison guide for course authoring teams

Coassemble is WCAG 2.2 Level AA Conformant

Competitor analysis

Designing effective microlearning courses

How to access and interpret the Headless usage report

How to handle competitor objections when positioning your Embed solution

Guide to pricing models for Coassemble Embed and key competitor benchmarks

Sales enablement guide: Driving user adoption

Customer testimonials for Coassemble Embed course creation (sales enablement)

Our mission: Barrier-free knowledge transfer (partner-friendly positioning language)

Getting started guide

How to communicate Coassemble feature releases to your customers 

How to migrate courses from other authoring tools into Coassemble Embed

Guide to releases

Curate

AI Create

Customize

Learner experience

Self-hosting Coassemble Embed

Initial AWS requirements for self-hosting

Embed Partners

Coassemble's AI: how it builds courses, screens, quizzes, images and narration, and how you stay in control.