From first sign-in to the first useful signal.

Developer path

1. Sign in and create your workspace from the onboarding screen.
2. Save the secret key once; keep it in a password manager and never put it in browser code.
3. Open Developer setup to configure the extension, allowed origin, and first zone.
4. Create tester tiers and invitation links in Tester pools.
5. Configure the customer-side MCP server and let your own agent pull threshold-met feedback.

Tester path

1. Install the extension from the download page.
2. Sign in from the extension when a developer has invited you.
3. Redeem the invite link, then open the target site in Tester mode.
4. Submit feedback or vote only where the zone’s audience rules allow it.
5. Review memberships and server-recorded points in the Tester center.

The implementation loop

Feedback reaches the developer workspace when its threshold is met. The developer’s MCP-connected agent retrieves the metadata, implements and tests changes locally, and reports status, commits, pull requests, logs, and deployment links back to ADapptive.

Troubleshooting

• Reload the extension after changing a site configuration.
• Confirm the current tab origin exactly matches the configured site.
• Use a publishable key for browser feedback; use the secret key only in the MCP or one-time studio-token flow.
• Check the dashboard deployment detail and logs for customer-side pipeline status.