Go-Live Checklist

Follow this checklist when you are ready to move from test mode to live mode. Complete every item before enabling your program for real partners and customers. All endpoints reference API version v1.

1. Swap test keys for live keys

Replace all test API keys in your codebase and configuration with their live counterparts:

Replace	With
pk_test_* (in the tracking snippet)	pk_live_*
sk_test_* (in server-side code / env vars)	sk_live_*

Where to check:

• Tracking snippet data-merchant attribute in your HTML / template
• Server-side environment variables for the Conversion API
• CI/CD pipeline secrets or deployment configuration
• Any scripts or cron jobs that call the Selgeo API

danger

Never commit live secret keys (sk_live_*) to source control. Use environment variables or a secrets manager.

2. Verify Stripe live connection

1. In the Selgeo dashboard, go to Settings > Stripe.
2. Confirm that your live Stripe account is connected (not just the test account).
3. Verify the Stripe webhook endpoint. Selgeo provides a webhook URL that must be registered in your Stripe dashboard under Developers > Webhooks for your live mode. Ensure the following events are enabled:
   • checkout.session.completed
   • invoice.paid
   • charge.refunded
4. Send a test event from the Stripe webhook dashboard and confirm it appears in the Selgeo delivery log.

3. Remove test data

Test-mode data is isolated from live mode, so it will not appear in live reports. However, it is good practice to clean up:

• Remove test partners that should not carry over
• Archive or delete test programs that were used only for integration testing
• Clear test webhook endpoints if they point to localhost or development URLs

info

Test-mode data does not affect live-mode data in any way. This step is optional but helps keep your account tidy.

4. Verify webhook endpoints

1. Go to Settings > Webhooks in the dashboard.
2. Create (or verify) your live-mode webhook endpoints. Live endpoints must use HTTPS.
3. Subscribe to the events your application needs. At minimum, consider:
   • conversion.created — to sync conversions to your system
   • commission.created — to track new commissions
   • conversion.fraud_detected — to be alerted about fraud
   • participant.approved — to provision access for new partners
4. Click Send test ping for each endpoint to verify connectivity.
5. Store the signing secret (whsec_...) securely in your server's environment variables.
6. Verify that your server validates webhook signatures correctly.

5. Review rate limits

Confirm your integration stays within the API rate limits:

Zone	Limit
Tracking (POST /v1/clicks)	1,000 req/min per pk_* key
Conversion API (POST /api/v1/conversions)	120 req/min per sk_* key
General API	300 req/min per IP address

If you expect higher traffic volumes, contact support before going live.

6. Review commission rules

1. Go to Programs > [Your Program] > Commission Rules.
2. Verify that commission percentages, flat amounts, hold periods, and auto-approval settings are correct for production.
3. If you use net-basis commissions (commission calculated after Stripe fees), confirm that your Stripe live account has the correct fee structure.

7. Test the full flow one more time

Before announcing your program to partners, run through the complete flow in live mode with a real (but small) transaction:

1. Open your referral link in a browser.
2. Complete a real purchase (you can refund it afterward).
3. Verify that the click, conversion, and commission appear in the dashboard.
4. Verify that webhook events were delivered to your endpoints.
5. Refund the transaction in Stripe and confirm that the commission.refunded event fires.

8. Enable your program

1. Set your program status to Active in the dashboard.
2. Share program invite links or the application form URL with your partners.
3. Monitor the dashboard for the first real partner sign-ups and conversions.

Post-launch monitoring

After going live, keep an eye on:

• Webhook delivery log — check for failed or dead-lettered deliveries
• Attribution audit log — review attribution decisions for correctness
• Fraud alerts — monitor conversion.fraud_detected events
• Commission review queue — approve or reject commissions that require manual review (e.g., net-basis commissions flagged with needs_review)