RELAYLead data audit
A K.I.T. Tool Managed by 3KeetStreet LLC

YOUR AUDIT WORKSPACE

See the gaps. Focus the fix.

Compare your uploaded reports, prioritize the findings, and prepare your next steps.

Audit setupUpload reports, check the suggested dates, and review the field map.

Start with the same reporting period

CSV files stay in this browser session

How dates and duplicate timestamps are handled

Dates are suggested from mapped Entry Date columns using the calendar dates written in the reports. A month containing at least 80% of dated rows is treated as the reporting month; otherwise, shared months with at least 10% per report are used. Suggestions cover full calendar months. You can edit either date. Export the same inclusive entry-date range from each platform. Uploaded rows are compared as supplied; dates are not filtered again. Timestamp offsets are honored when present; unzoned modified timestamps are interpreted in the browser’s timezone.

Review field mappings & saved maps

Field mappings

Defaults follow the confirmed LP/LC map. LC ZIP uses Postal Code first, then Zip-Codes.com Lookup Cbsa if the column or a retained value is missing. SRS_ID uses srs_id on both platforms. Choose the matching column in each report. Select “Not included” to leave a field out of the audit.

Save, import, or share a field map

Maps are saved in this browser on this address. Export a map to share it with Alan; uploaded lead data is never saved with it.

Entry Date defaults to LC Submission Timestamp and LP EntryDate. It is optional timing metadata, not an audited field. Field values retain their source format; use LP state abbreviations and LC product codes (e.g. WIB) as specified in the mapping guide. Choose the timezone represented by exported timestamps without an offset. Explicit offsets are honored; date-only entries support day-level comparisons.