Test Mode

Test Mode allows you to preview and validate your feedback forms before deploying them to production.

It helps ensure that everything works correctly across different devices, browsers, and trigger configurations—without polluting real feedback data.

---

Why Use Test Mode?

• Keep production reports clean: Test submissions won’t appear in your production analytics or reports.
• Save credits: Actions performed in test mode (such as viewing or submitting feedback or pipelines) do not consume production credits.
• Validate end-to-end flows: Test all trigger types, integrations, and UI behavior before a public launch.

---

How to Enable Test Mode

1. Generate a Test API Key

   • Go to your project’s API Keys section.
   • When creating a new key, select Test in the Environment dropdown.
   • Use a clear Application Name to identify test instances (e.g., test-app-1, test-app-2, etc.).

2. Configure Feedback Form (Auto Trigger)

   • In the feedback form configuration, map the application names associated with test keys.
   • This ensures that forms can be auto-triggered in test environments.

3. Set Up SDK Configuration

   • For both Auto and Manual triggers, use the test API key in your SDK setup.

Rate Limits in Test Mode

Refer to the Rate Limits guide for specific limits applied in Test Mode.

---

What Is Covered in Test Mode?

• Feedback form configuration (Auto trigger) mapped to test application names
• Summary and reports for feedbacks received via test applications
• Feedback reports (Audience Overview, Response Summary, Individual Reports, Export, Destinations)
• Data pipelines enabled under test mode (not counted toward usage)

---

Switching Back to Production Mode

1. Go to your project’s API Keys section.
2. Generate a new API key and select Production in the Environment dropdown.
3. Update your Feedback Form Configuration to map production application names.
4. Update your SDK configuration to use the production API key.