Sample Device Data Best Practices

Updated May 2026

Well-managed sample device data makes a utility site more useful and reduces the risk of leaking real customer identifiers into test environments.

That includes IMEIs, model names, device colors, asset tags, and mock account records used in screenshots or demos.

Separate production and test data

Production records and sample records should be kept separate in screenshots, exports, support workflows, and training material.

Synthetic identifiers reduce privacy, compliance, and operational confusion.

Use structured and repeatable samples

Testing is easier when sample values are valid format, labeled clearly, and reused consistently across QA cases and help content.

This makes debugging easier and reduces ambiguity during demos or internal reviews.

Document the purpose of sample values

Teams should explain why sample device identifiers are present and where they should or should not be used.

That improves handoff quality between engineering, support, operations, and training teams.