A conference track is a group of sessions organised around a topic, audience or certification path, so attendees can follow a coherent route through the agenda.
A multi-day agenda with forty sessions is unreadable as a list. Tracks give it structure, so an attendee can see which sessions are for them without reading every abstract. The test of a good track is whether someone can pick theirs in about ten seconds.
Tracks named after your internal teams mean nothing to an attendee. Tracks named after the job someone came to do, the level they are at, or the credential they are chasing, do. Beginner, intermediate and advanced is a weak scheme, because almost nobody self-identifies as a beginner.
A track says which sessions belong together. Concurrency says which run at the same time. Scheduling two sessions from the same track against each other forces exactly the choice the track was meant to prevent.
Sessions are grouped into tracks in the agenda, and attendees filter by track to build a personal schedule rather than working from a printed grid. See event agenda builder.