Avoid editing imported Figma Prototypes - Preserve data integrity

When conducting usability tests with Session Recordings, Click Tracking, and User Flow analytics, maintaining the integrity of your prototype(s) is essential. Modifying an imported prototype in Figma can disrupt data collection and lead to incomplete or inaccurate insights.

---

Once a prototype is imported into Useberry, it becomes the foundation for how we:

• Track user clicks and tap events
• Monitor navigation between screens
• Generate user flow maps
• Record and replay user sessions

These systems depend on the structure and identifiers in your Figma file — such as frame names, layer IDs, component hierarchy, and flow links. If you modify that file after import, it can result in:

• ❌ Missing or broken click data
• ❌ Inaccurate screen transitions in flow analysis
• ❌ Incomplete or unusable session recordings
• ❌ Lost insights due to disconnected paths

Even seemingly minor changes — like deleting or updating a component from your library, changing its variant or even importing a new one — can affect how data is collected and interpreted.

---

To protect your research integrity, we strongly recommend the following workflow:

1. Duplicate your working prototype in Figma
2. Move the duplicate to a new, standalone file (e.g., "Prototype – Usability Testing")
3. Import that file into Useberry
4. Do not edit this file once testing has begun

This separation ensures your test data remains reliable and that ongoing design changes don’t interfere with your live research.

---

If you must make changes — for example, fixing a broken flow or updating copy:

• Edit the original design, not the imported file
• Duplicate the updated version into a new testing file
• Re-import the prototype and use it in a new study
• Clearly label and archive older tests if needed

This creates a clean break between test rounds, preserving past results and ensuring consistency moving forward.

---

Maintaining a stable prototype is critical for collecting clean, actionable research data. By keeping your testing prototype separate and untouched, you ensure that every click, tap, and transition is captured accurately — and that your insights reflect true user behavior.