NinaData Monetizer -- Rollout / Verification Checklist

Canonical URL: https://docs.ninadata.ai/rollout/

1. Customer preparation

Confirm before install:

• Approved production host(s) match what NinaData has on file (host only; no scheme, path, query string, or trailing slash).
• Agreed test URL is a real, loadable page (not a placeholder).
• Rollback owner is named on the customer side.
• CMS / template / tag-manager owner is named on the customer side.
• Consent Management Platform (CMP) is present and current if the site uses one; the runtime observes the CMP for diagnostics only, and does not display consent UI or store TC strings.

2. Install on the test URL first

• Add the snippet from the installation guide to the agreed test URL.
• Do NOT roll the snippet out to any other URL yet.
• Publish the change.

3. Verify on the test URL

In a fresh private / incognito browser session, open DevTools and confirm:

• The runtime script returned 200 OK.
• The collector endpoint received at least one POST and returned 204 No Content.
• No NinaData-related errors appear in the console.
• The page layout did not shift unexpectedly.

Visible ads may appear when the page is eligible and demand returns a bid. Absence of an ad on a given page load is not automatically a failure.

4. Send NinaData

Reply to NinaData with:

• The exact test URL (scheme + host + path).
• The timestamp of verification (date + time + timezone).
• The browser and device used (for example Chrome 121 / Windows 11 desktop).
• Optional screenshots that show layout, placement render, or console output -- only if useful for triage.

Do NOT send:

• Your CMP configuration.
• Any analytics or ad-server credentials.
• Any user-identifiable data.

5. Wait for NinaData confirmation

Do not roll out beyond the test URL until NinaData confirms the install is healthy on their side. Confirmation is a written note in the same channel used for onboarding.

6. Sequenced rollout

After NinaData confirms:

1. Template / content-type rollout. Extend the snippet from the single test URL to the agreed page template or content type on the production domain.
2. Full production rollout. Extend template coverage to the full production domain or section that NinaData has authorized.
3. Additional templates / domains. Each additional scope is agreed in writing with NinaData before it is enabled.

Either side may pause rollout at any stage.

7. Rollback

1. Remove the <script> block that sets window.NINA_MONETIZER_CONFIG.
2. Remove the <script async> block that loads the runtime.
3. If either block was injected through a tag manager, clear the tag manager or template cache.
4. Tell NinaData when the rollback took effect.

After the next page load, no NinaData runtime code runs, no telemetry is sent, and no placements are created.

The named rollback owner from Section 1 is responsible for executing the rollback and notifying NinaData.