Two things make a venue's data useful: knowing who each driver is, and trusting the laps. The Drivers page is where in-game names become real people with an email address, so leaderboards, emails and Discord posts can address them properly. The Laps page is where you fix the data before it sticks: invalidate a cut lap, rename a typo, delete a test run.
Drivers
The Drivers page has three sections: Registered Drivers, Import Customers and Name Matching.
Registered Drivers
The table lists everyone with a driver record: first name, last name, email, birthdate, social handle and the date they registered. A search box filters by name or email as you type. The list shows 25 per page, newest first.
Beside an email you may see a chip. Subscribed means they gave consent and can receive marketing email. Unsubscribed means they opted out, or you suppressed them. No consent means they were added without agreeing to email; you can suppress them here, but consent can only be given by the driver.
| Control | What it does |
|---|---|
| Quick Add | Opens a form with first name, last name, email, birthdate and social handle. Names are tidied automatically (title case, and the right capitals in names like O'Brien or McLaren). Any in-game name that contains both first and last name is linked to the new record straight away. |
| CSV and Excel | Download the whole driver list. |
| Row click | Expands the driver's stats: total and valid laps, member since, games played, favourite car and track, their five best laps, and recent visits. |
| Edit | Edits the row in place. Changing a name updates the display name on every linked in-game name in every game. |
| Unsubscribe / Resubscribe | Suppresses or restores marketing email for that driver. Only shown when they have an email address. |
| Delete | After a confirmation, removes the driver and all their name links. Their laps remain under the raw in-game name. |
The registration page
Rather than typing customers in, put a tablet at the desk showing your-venue.mlttp.com/registration/. It carries your venue name and accent colour and asks for first name, last name, email, an optional birthdate and social handle, and a checkbox agreeing to receive email from the venue. Submitting creates the driver record with consent, links any matching in-game names, and shows a thank-you for five seconds before clearing for the next person. Birthdates feed the birthday email; the handle is there for your own use.
Import Customers
The import wizard brings in a list from your point of sale or a spreadsheet and shows you what it will do before it does it.
- Get the list in.
Either Pull from ROLLER with a date range (or Pull all customers), using the ROLLER credentials from Settings; or paste a list into the text box, or choose a CSV file, and press Continue. Column headings are recognised in most common spellings: first name, last name, email, phone, birthdate, social and a subscribed flag. A row needs an email or a full name.
- Review matches.
Every row is classified as New, Update (email) where the email already exists, Update (fuzzy) where the name closely matches an existing driver, or Skip (dup) where nothing would change. New rows and confident matches are pre-ticked. New only and High-confidence adjust the selection in one click; the checkboxes let you fine-tune.
- Commit.
Commit selected inserts new drivers and fills in blanks on matched ones without overwriting anything you already had. Consent is set only when the import says the customer opted in. The result line reads, for example, Inserted 42, updated 7, skipped 3. Afterwards, press Auto-Match All in Name Matching to link their in-game names.
ROLLER nightly sync
If you use ROLLER for tickets, Settings › ROLLER Integration takes a client ID and secret and a checkbox for Enable nightly auto-sync. Once a day Multitap pulls customers changed since the last sync, adds the new ones and fills blanks on exact email matches. Anything ambiguous is left for you to review in the wizard. A status line shows the last sync time and how many records it applied.
Name Matching
Laps arrive under whatever name is set in the game. Name Matching links those names to driver records. On the left, Unmatched In-Game Names lists every name that has driven and is not yet linked, with a driver picker and a Link button per row. On the right, Current Mappings lists existing links with an unlink button; links made automatically carry an auto badge.
Auto-Match All links every unmatched name that contains a registered driver's first and last name. The same check runs on every new name the first time it is seen, so a customer who registers at the desk and then types their full name into the rig is linked without anyone doing anything.
Once linked, the driver appears everywhere as F. Lastname, their laps count toward their stats and emails, and their laps can be published to the global leaderboard under that standard name.
Laps
The Laps page lists every individual lap recorded at the venue, newest first, fifty per page, with a tab per game. Each row shows the player, car, track, lap time, top speed, a valid or invalid mark, the number of cuts, the tyre compound and the date. Hover a player to see the raw in-game name, and a car or track to see its folder.
Finding laps
Type a name in Search player, choose All, Valid or Invalid, and press Filter. CSV and Excel download the filtered list, up to ten thousand laps.
Fixing a lap
| Control | What it does |
|---|---|
| Mark valid / Mark invalid | Flips the lap's validity. Invalid laps drop to the bottom of every board, faded and struck through, and never count as a record or personal best. |
| Delete lap | Removes the lap after a confirmation. |
| Rename player | Changes the raw in-game name on every lap by that player in this game. Use it when a regular mistyped their name on the rig. |
Tick several rows and a bar appears with Delete Selected, Mark Valid and Mark Invalid. Selection is per page and clears when you change page or filter.
The in-game app decides whether a lap is valid as the driver crosses the line: it must be clean by the game's own rules, with no cuts, and not start or end in the pit lane. The Laps page shows that verdict and lets you overrule it either way.