Experimenta en tu paywall
Encuentra el mejor paywall científicamente 💙.
Empieza ahora con este prompt en tu Claude Code o Codex
I want to use Experiwall (experiwall.com) to A/B test my app. First, analyze my project. Look at the codebase, figure out what kind of app it is (B2B, B2C, SaaS, e-commerce, etc.), and recommend which pages or UI elements I should be experimenting on: pricing pages, onboarding flows, CTAs, upgrade prompts, sign-up forms, feature gates, whatever makes sense for my product. Then set up Experiwall in my codebase. Prefer the Experiwall CLI over the MCP server: start with npx @experiwall/cli login. If the CLI needs browser authentication or an API key, open https://experiwall.com/cli/login directly for me so I can sign in and generate the CLI login command. After login, run npx @experiwall/cli whoami or the equivalent command to verify authentication. Use the CLI for setup, experiment creation, and verification whenever possible. Only connect to the Experiwall MCP server if the CLI is unavailable or you need AI-native project management. The MCP endpoint is https://experiwall.com/api/mcp. For most websites, install the lightweight Experiwall script snippet and add conversion goals or events where needed. Only use @experiwall/react if this app needs React component-level A/B tests. Create my first A/B experiment with at least two variants based on your analysis. I want real conversion tracking so we can see which variant actually performs better. When you need me to open a website or preview the app, use the appropriate command to open the browser directly so it is easy for me to review. Set everything up end-to-end so it's ready to go live.
Compatible con