Keep the history. Keep the identity at your shop.

Your report needs to recognize repeat visits by the same customer. Replace the customer’s identity with one stable anonymous ID, and keep a separate private bridge that connects that ID to the original customer key in your shop software.

Download the preparation pack

• Private customer bridge template — keep this at your shop. Never upload it to ReviveMetrics.
• Synthetic bridge example — shows one mapping per customer.
• ReviveMetrics upload template — only the de-identified history goes here.
• Synthetic upload example — the same customer ID appears on more than one visit.

1. Start with the original customer key

Export your shop software’s stable customer ID with the repair-order history. Use the customer key, not the repair-order number, a name, an email address, or the row number. Work with one shop location at a time. Keep this working export private.

Import customer keys as text so leading zeros stay intact. For example, 00042 must not silently become 42. Use the same customer-key format on every export.

2. Create the private bridge once

1. Copy the original customer-key column into a separate private sheet.
2. Remove duplicate customer keys there, so each customer has exactly one row.
3. Assign one new anonymous ID to each unique customer. A sequence such as anon_001 is acceptable in this unique-customer bridge, never in the repair-order sheet.
4. Save the assigned IDs as fixed values. Sorting or inserting rows must never recalculate or renumber them.
5. Keep the bridge securely with the shop’s records, with access limited to authorized staff.

3. Look up the saved ID for every repair order

Join the repair-order history to the bridge using an exact match on the original customer key. Every visit by the same customer must return the same anonymous ID. Do not assign IDs again in the history sheet.

If a lookup is missing, stop and fix the bridge. Never fill missing matches with one shared ID, a blank, or a new row number. Check that each original key maps to one anonymous ID and each anonymous ID maps back to only one original key.

4. Reuse it on future exports

Open the existing bridge for that same shop location. Keep every previous mapping unchanged. Append mappings only for genuinely new customer keys, using IDs that have never been assigned. Do not restart at 001, renumber after sorting, or delete old mappings because a customer is absent from this export.

If the bridge is lost or customer keys change after a software migration, stop and reconcile the records before sending another file. A fresh numbering pass would break the connection to earlier reports.

5. Export only the upload file

Copy the matched anonymous IDs into the upload template as fixed values. Use one row per completed repair order, unique de-identified repair-order IDs, and broad service categories. Remove original customer keys, names, emails, phone numbers, addresses, VINs, license plates, payment information, and free-text notes. Review the entire file before uploading.

The bridge and original export stay at your shop. Upload only the completed de-identified CSV through your order. Check the exact accepted columns and file limits.

Use the report without losing the connection

When a report refers to an anonymous customer ID, use your private bridge to find that customer’s original key, then open their record in your shop software. Check your current records and contact permissions before taking action. The report does not send customer messages.

Need help preparing your file? Describe the software and column names you have. Do not attach or paste customer identities or your bridge.