Best Practices

Recommended setup

Start with Trackings

Trackings is the most actionable entity for reporting. Set it up first and validate your data before adding Courses or Screen types to the same flow.

Join Courses and Trackings

Course IDs in the Trackings entity map directly to Courses. Use Coupler.io's Join transformation to enrich tracking records with course names and metadata — this makes your reports far more readable.

Use Append for multi-org setups

If you manage multiple Coassemble organizations, create one data flow per organization and use the Append transformation to consolidate all tracking data into a single destination table.

Data refresh and scheduling

Sync Trackings more frequently than Courses

Learner progress changes constantly, but your course catalog rarely does. Schedule Trackings to refresh daily or hourly, and Courses weekly — or only on-demand when you publish new content.

Run Screen types on-demand only

Screen types are a static reference table. There's no value in scheduling frequent refreshes for this entity — sync it manually when you need it for a content audit.

Performance optimization

Send high-volume tracking data to BigQuery

If your organization has thousands of learners, Google Sheets will hit row limits quickly. Route Trackings data to BigQuery or another database destination to handle the volume without issues.

Use AI destinations for instant insights

Pipe your Trackings data into ChatGPT or Claude to automatically generate completion summaries, flag overdue learners, or draft manager reports — without building a dashboard from scratch.

Common pitfalls

Don't rely solely on the completed_at field to measure completion. Learners who are 99% through a course but haven't hit the final screen will have a null value there. Always use progress and status together for an accurate picture.

Do

• Join Courses to Trackings so reports show course names, not just IDs

• Validate your data with a manual run before setting up a schedule

• Use separate data flows per Coassemble organization

Don't

• Assume empty Trackings means a connection problem — it may just mean no learner activity yet

• Schedule Trackings and Courses in the same data flow if you're hitting rate limit errors

• Use Screen types as a primary reporting entity — it's a reference table, not a metrics source