Staging & QA Access

GoWit provides a dedicated staging environment for safe integration testing before going live.

Staging environment uses a separate base URL for API calls and has its own credentials/API key.
At the start of integration, GoWit will issue you:
- A staging API key

Multiple test ad placements in the staging system (covering different ad formats)

You’ll also receive login access to GoWit’s staging dashboard to view and manage test data.

⚠️ When using staging, none of the data or actions impact real users or advertisers—it’s a sandbox.

Point your development or QA environment to the staging API endpoints.

Best Practices for Testing in Staging

Use sandbox data: Integrate the advertisers/products from your own staging or test environment. Sync those to GoWit staging and use them in test campaigns — this data will drive the rest of the integration flow.
Mirror real placements: Configure staging placements to mimic production ones (e.g., search banner, product page native ad).
Activate dummy campaigns: Create test campaigns (or request GoWit team setup) for your test advertiser and placements.
Trigger test impressions and clicks: Manually browse in test mode, click ads, and verify impressions/clicks are logged (via logs or GoWit dashboard).
Send sample conversion events: Simulate purchases and validate attribution based on the attribution types configured for your integration (e.g., post-click, post-view).
- Test both direct sales (same promoted product) and indirect sales (different product from same advertiser).
- Always send all completed orders—GoWit will handle attribution logic.
Utilize QA tools: Use Data Sources console or Auction request logs to debug (e.g., feed errors, missing events).
Coordinate with GoWit: Stay in touch with integration support to confirm impressions, conversions, or troubleshoot misconfigurations.

Once staging validation is complete: