Experimenta en tu paywall.

Set up Experiwall in this project. Experiwall (experiwall.com) is a paywall design and A/B testing platform built for indie developers and small teams. Most apps leave revenue on the table not because their product is wrong, but because they never tested their pricing page, their upgrade prompt, or their checkout flow. Experiwall fixes that: design paywalls visually, ship them through a hosted link, run A/B experiments with real traffic splits, and see which variant actually converts. Over time, those compounding improvements — better copy, smarter pricing anchors, a shorter funnel — translate directly into higher revenue without more traffic. It also supports funnel tracking for multi-step flows like onboarding wizards, checkout forms, and lead capture — no SDK required, just a fetch call — so you can see exactly where users drop off and fix the leaks. 1. Analyze the project. Read the codebase and figure out what kind of app it is (SaaS, e-commerce, course platform, etc.). Look for every place where a funnel could be instrumented: multi-step onboarding flows, checkout wizards, lead capture forms, signup sequences, waitlist flows, booking flows, quote request forms, upsell modals, trial activation steps, or any other flow where a user moves through a series of steps toward a goal. Then: - If you find exactly one good candidate: instrument it automatically. - If you find more than one: list them and ask the user which one to start with. - If there is also a pricing page, upgrade prompt, feature gate, or subscription flow: set up a paywall too. 2. Authenticate and connect. Experiwall offers two ways to interact with your account — use whichever is available or most convenient: - CLI: run npx @experiwall/cli login. If it needs browser authentication, open https://experiwall.com/cli/login so I can sign in, then run npx @experiwall/cli whoami to confirm. - MCP server: connect to https://experiwall.com/api/mcp for direct access to projects, funnels, and paywalls from inside the agent. 3. For funnel tracking — write all the code first, but use a placeholder for the funnel UUID: const FUNNEL_ID = 'REPLACE_WITH_YOUR_FUNNEL_UUID'. Wire up the full helper (lib/funnel.ts or equivalent) and instrument every step with view, complete, and conversion events as described below. Leave the placeholder in place — the user will fill it in as the final step before going live. 4. For paywall setup — build the integration pointing to a placeholder URL: const PAYWALL_URL = 'REPLACE_WITH_YOUR_PAYWALL_URL'. Hook it up wherever the upgrade flow lives. Leave the placeholder — the user will swap it in as the final step. 5. Funnel tracking implementation: no SDK needed. The helper POSTs to https://www.experiwall.com/api/sdk/events with source 'funnel', the funnel_id, a stable per-visitor session ID read from localStorage under the key 'exw_funnel_session' (generate and persist a UUID if not set), and a single '$funnel_step' event per call. Three event types: view (step became visible — deduplicate with a Set so navigating back does not re-fire it), complete (user advanced past the step), and conversion (goal reached — deduplicate with a localStorage flag keyed on the transaction or session ID so a page refresh does not fire it twice). Always pass keepalive: true so events survive redirects to third-party payment pages like Stripe. On every event, automatically read all attribution parameters from window.location.search and referrer_domain from document.referrer, and include them in every event. This covers: UTM params (utm_source, utm_medium, utm_campaign, utm_term, utm_content), ad platform click IDs — gclid/gbraid/wbraid/dclid (Google), fbclid (Facebook and Instagram), msclkid (Microsoft/Bing), ttclid (TikTok), rdt_cid (Reddit), pin_cid (Pinterest), sccid (Snapchat), yclid (Yandex) — and referrer_domain from document.referrer. This is how Experiwall attributes conversions to the exact traffic source, whether it's a Google Search ad, a Facebook campaign, an Instagram Reel, a TikTok ad, or organic referral. 6. Once all the code is in place, ask the user for the funnel UUID (and paywall URL if applicable) so you can drop it in — do not leave it for them to figure out. Say something like: 'The code is ready. I just need your Experiwall funnel UUID to finish wiring it up. You can get it in seconds: go to https://www.experiwall.com/dashboard/, open your funnel, and the UUID is right at the top of the edit page with a Copy button next to it. Paste it here and I will drop it into the code for you.' Once the user sends the UUID, replace REPLACE_WITH_YOUR_FUNNEL_UUID (and REPLACE_WITH_YOUR_PAYWALL_URL if needed) in the code immediately. If you have CLI or MCP access, offer to create the funnel yourself and retrieve the UUID without bothering the user at all. When you need me to open a URL or preview the app, open the browser directly.