TapAppLinkProduct
Sandbox and production
Every app has two environments from day one. Clicks, installs, codes, customers, and payouts stay in the environment that recorded them. Test a creator program in sandbox. Live invoices stay on production.
Switch environments in the dashboard. Sandbox uses an amber accent so you can see you are in sandbox. Creators invited in sandbox stay on the sandbox portal. Live payouts stay on production.
| Production | Sandbox | |
|---|---|---|
| SDK key | Store / TestFlight / Play production builds (etk_live_) | Simulators, debug, internal builds (etk_test_) |
| Links | go.tapapplink.com | sandbox.go.tapapplink.com |
| Store redirect | App Store / Play / desktop fallback | Stays on a test confirmation page |
| Billing webhook | Live provider project. Provider setup | Provider sandbox / test store. Provider setup |
| Live Attribution Debugger | Sandbox only | Sidebar, then Debugger. How to use it |
What is shared
Store destinations, creator-portal branding, and payout cadence are app-level. Configure them once. They apply to both environments. Clicks, attributions, revenue, commissions, and invoices stay per environment.
Test in sandbox first
After the SDK is in a development build, open Sandbox, then Debugger. Start a link session, scan the QR, launch the app, and watch click, install, and billing customer land on a live timeline. Sandbox links stay on a confirmation page. Live store listings stay unused.
Full walkthrough: Live Attribution Debugger.