Production rollout
Going live is a coordinated handoff. There are partner-side steps you own, CoinTracker-side levers you don't, and a ramp window where both sides watch their dashboards.
Before the launch window
Partner-side
Send CoinTracker your production parent origins (every domain where the iframe will load in prod). CoinTracker registers them server-side. No wildcards.
Swap to production credentials in your environment config — token-issuance credentials for CoinTracker's production Auth0 tenant (
https://auth.cointracker.com/), production webhook signing secret, production webhook receiver URL. Tokens issued by the staging Auth0 tenant will fail validation in production.Point your webhook receiver at production CoinTracker. Confirm DNS, TLS, and reachability from the CoinTracker prod environment if possible.
Confirm
options.mode: 'production' is set in your prod build. Easy to leave on 'alpha' accidentally and ship a broken integration.Verify the SDK version matches the version CoinTracker confirmed (the one with your partner enum value). Older versions may not recognize your slug.
Set up monitoring on your webhook receiver for webhook latency (p50, p95, p99), 5xx rate, signature-verification failure rate, and idempotency-skip rate.
Run a final end-to-end test against staging the day before launch. Walk a real user through onboarding, confirm webhook delivery, confirm cost-basis appears in your partner UI.
CoinTracker-side (what they handle, not you)
These happen on CoinTracker's side. You don't act on them, but knowing they exist explains why launch is a coordinated handoff:
- CoinTracker registers your production parent origins in the iframe's allowlist (server-side deploy).
- CoinTracker's on-call and embedded team will be watching the launch window with you.
During the launch window
Rollout pacing is coordinated with your CoinTracker integration owner — there is no public on/off switch you can flip yourself. The typical sequence:
- Deploy on your side, gated behind your own feature flag at a low rollout percentage (e.g. 5% of eligible users).
- Watch dashboards on both sides for ~15–30 minutes:
- Your webhook latency and 5xx rate.
- Your signature-verification failure rate.
- CoinTracker's iframe error rate, auth failure rate, and tax-flow completion rate.
- Ramp up your feature flag if metrics are clean. A common pattern is 5% → 25% → 50% → 100% with at least an hour at each step. Confirm each step with your CoinTracker contact.
What to watch on your side
The signals that matter most in the first hour:
| Metric | Healthy | Investigate |
|---|---|---|
| Webhook p95 latency | < 1s | > 5s — your receiver may be saturated |
| Webhook non-2xx rate | < 0.1% | > 1% — something in your receiver path is failing. Note: CoinTracker does not auto-retry on 4xx/5xx (only on network errors / timeouts), so a non-2xx is a missed delivery for that run. |
| Signature-verification failure rate | 0% | Any sustained failures — likely a secret mismatch |
| Idempotency-skip rate | A few % | High — repeated deliveries (cross-page or manual replay); confirm dedup logic is correct |
| Partner-side imports per webhook | Matches expected user volume | Lower than expected — deliveries failing somewhere upstream |
When to alert CoinTracker
Page or message the CoinTracker embedded team during the launch window if:
- Your webhook 5xx rate spikes above 1% for more than a few minutes.
- Signature verification fails on every delivery (likely a secret/env mismatch).
- The iframe fails to load for users in production (CORS or origin allowlist issue).
- Any
TaxKitErrorother thanMissingConnectionsappears at notable volume.
CoinTracker can roll back the launch gate to 0% from their side, giving you breathing room to fix without forcing you to deploy a partner-side hotfix.
After the launch window
Keep monitoring for the first week — odd edge cases (long transaction histories causing webhook pagination, specific exchange OAuth failures) usually surface within the first few days.
Tune your retry / alerting thresholds based on observed baselines.
Hand off operational ownership to your support team if your launch team isn't the long-term owner.
Schedule a post-launch review with CoinTracker within ~2 weeks to cover anything surprising in metrics.
Rollback
If something goes wrong and you need to back out:
- Fast partner-side rollback: flip your feature flag off. Users stop seeing the kit.
- CoinTracker-side rollback: coordinate with your CoinTracker on-call contact — they can disable your partner integration server-side if needed.
Both are reversible — a botched launch isn't a one-way door. The credentials and config stay valid; you can re-launch after fixing the issue.