CustomerData report mapping

If you're currently consuming the CustomerData CSV export from Auditdata's AuditdataCloud admin UI, this page shows how every column in that report maps to a field on the new API/Event surface (Sessions API + Service Bus events).

The new API exposes a strict superset of the report's useful columns, plus a handful of fields the report never carried — see the Data schema for the complete API payload. A small number of report columns are deliberately not exposed on the API; they're flagged below.

Conventions

• API/Event field names are camelCase.
• "—" in the API/Event column means the report column is not exposed on the new API; the row's Notes column says why.
• Audiogram thresholds reference the new schema — see Audiograms.

Column-by-column mapping

The order below follows the report's natural column order so a CSV parser can be migrated row-for-row.

Report column	API/Event field	Notes
StoreName	officeName	Office display name.
Device	deviceType	Free-form device type, e.g. "iPad".
ResultId	id	Listo's session id. Use as application idempotency key on the API.
TestDateTime	testTime	RFC 3339 UTC. The Sessions API filters on this field.
Title	title
Firstname	firstname
Lastname	lastname
Birthday	birthday	RFC 3339 date-time at midnight UTC.
Email	email
Phone	phone
TestResultLeft	leftTestResult	Coded outcome — see Test result codes.
TestResultRight	rightTestResult	See Test result codes.
LeftHL125	—	Always null. Not exposed on the API.
LeftHL250	leftAudiogram.f250	dB threshold at 250 Hz.
LeftHL500	leftAudiogram.f500
LeftHL750	—	Always null. Not exposed on the API.
LeftHL1000	leftAudiogram.f1000
LeftHL1500	—	Always null. Not exposed on the API.
LeftHL2000	leftAudiogram.f2000
LeftHL3000	—	Always null. Not exposed on the API.
LeftHL4000	leftAudiogram.f4000
LeftHL6000	leftAudiogram.f6000
LeftHL8000	leftAudiogram.f8000
RightHL125	—	Always null. Not exposed on the API.
RightHL250	rightAudiogram.f250
RightHL500	rightAudiogram.f500
RightHL750	—	Always null. Not exposed on the API.
RightHL1000	rightAudiogram.f1000
RightHL1500	—	Always null. Not exposed on the API.
RightHL2000	rightAudiogram.f2000
RightHL3000	—	Always null. Not exposed on the API.
RightHL4000	rightAudiogram.f4000
RightHL6000	rightAudiogram.f6000
RightHL8000	rightAudiogram.f8000
BackgroundNoise	noiseLevel	Coded ambient-noise level: "1" Silent, "2" Some noise, "3" A lot of noise. See Noise level codes. The report displays the raw string.
Transducer	transducerName
StoreId	officeId	Listo internal office id (integer).
OfficeExternalId	officeExternalId	Tenant's primary external office id.
OfficeExternalAltId	officeExternalAltId	Tenant's alternate external office id.
DeviceName	deviceName
EmailSentDateTime	emailSentDateTime	null on the Service Bus event — email sending is async and runs after the event is published, so it hasn't happened yet at emit time. The Sessions API returns the accurate value once the email has been dispatched.
EmailStatus	emailStatus	null on the Service Bus event for the same reason. The Sessions API returns the accurate value once the email has been dispatched.
TestFlowName	testFlowName

Phantom audiogram frequencies

The report exposes 22 audiogram columns — 11 frequencies on each ear. Listo only measures and stores 7 frequencies per ear: 250, 500, 1000, 2000, 4000, 6000, 8000 Hz. The other four — 125, 750, 1500, 3000 Hz — are always null on the report. The API/Event drops these entirely rather than emitting permanently-null fields.

Fields new on the API/Event

The API/Event payload also carries a small number of fields that the CustomerData report never exposed:

• stimulusType — coded stimulus presented to the patient (pure tone, warble, narrowband noise).
• noiseCorrection — ambient-noise baseline applied to the raw measurements. Same 7-frequency shape as leftAudiogram / rightAudiogram.
• Consent flags — consentAgreeWithTermsConditions, consentContactEmail, consentContactPhone, consentCustom1/2/3. Nullable ints: 0 refused, 1 granted, null not asked.

See Data schema and Screening completed for the exact field shapes.