Integrate
Testing and go-live checklist
Before a slot goes live, check the label, the empty result, accounts under 18, and a phone-width layout. Ask for test ads during onboarding, and do not click your own live ads.
On this page
A slot is ready for live traffic when the placement is right, the label is intact, an empty result leaves no gap, and accounts marked under 18 see no ad. This page is that checklist. It is not a sandbox URL, and it is not a test flag.
The traffic check is a separate gate. Passing this list in a local build does not approve the app. Ads start after the check, as Publisher onboarding and The traffic check describe. No approval time is published.
Ask for test ads
Ask for test ads during onboarding when you need to see a real creative, open a landing page, or show review a labeled slot before you have live demand. How test traffic is marked is set in your integration docs. Those docs are issued after the traffic check, with the publisher ID and the snippet.
No test mode, query parameter, special publisher ID, or sandbox host is published. A made-up one will either do nothing or send traffic you did not mean to send. If the integration docs you received name a mark, use that mark. If they do not, ask through the contact page. We do not publish an email address or a response time.
You can still test the empty branch without a Visor flag. Build the UI so an empty result renders nothing, and exercise that branch with a stub in your own code. The stub is yours. It is not a Visor endpoint. Use it for layout. Use the test ads you were given when you need a real response.
Do not click your own live ads
Once the slot is live, you and your team should not click the ads in the production app. A click can be counted. Clicks from the people who run the app are not a person using the product. Use the test ads you asked for during onboarding when you need to open a landing page. If you must look at a live creative, look without clicking.
Do not ask users to click. Do not incentivize views or clicks. Do not refresh the slot in a loop. The terms of service forbid fake, bought, or incentivized traffic, and they forbid refreshing an ad in a loop to inflate views. The traffic check refuses the same patterns, including after you are live.
Checklist
Walk one thread as a person would, on the build you intend to ship. Then walk the failures on purpose. Each row is a pass or a fail. A fail means you are not ready for live traffic, even if the happy path looks fine.
| Check | What good looks like |
|---|---|
| Placement | The slot is under the finished answer. It is not between tokens and not between paragraphs. |
| Not inside the answer | The model’s words do not contain the ad. The slot’s node is not inside the answer’s node. |
| One ad | That answer has one slot. A second answer is a new turn. Neither answer grows a second ad. |
| Label | Ad · Sponsored, plain text, top-left. The middle dot is there. The words are not an icon. |
| No blank gap | You force an empty result and the thread closes up. No skeleton, no minimum height, no reserved box. |
| Under 18 | An account marked under 18 shows no slot and triggers no request. |
| Refusals and errors | A refusal, an error, or an empty answer shows no slot. |
| Mobile, 390px | At 390px wide, the ad is under the answer, full width of the thread, and not clipped. It is not a pop-up. |
| Dark mode | If you ship a dark theme, the words Ad · Sponsored stay readable. They are not the same color as the panel. |
| Screen reader | Moving from the answer, you hear an advertisement and the visible label. You do not hear the ad as the assistant. |
| Keyboard | The ad’s link or button comes after the answer in tab order. Focus does not jump to the ad. An empty slot has no tab stop. |
| Country | A live request is US traffic. You do not test the live integration with other countries. |
| Data | The request has no name, email, phone, precise location, payment data, or government ID. |
| Clicks | A test ad opens a real landing page in the system browser or an in-app browser. You do not click a live ad. |
How to look at each row
Placement is a check of the document. Select the answer text. The ad should not be part of that selection. In the inspector, the slot node should be a sibling after the answer, not a child of it. On a stream, watch the bubble grow and confirm nothing mounts until the stream ends.
For one ad, send two questions. Each finished answer has at most one ad. Refresh the thread and confirm you did not write a timer that re-requests the same answer. For the label, read the words. Do not trust a color chip or an icon. The words are Ad · Sponsored.
For 390px, set the viewport to that width or hold a phone of about that width. Scroll the answer, then the ad, then the next turn. Nothing should cover the answer. Nothing should sit in a sticky bar. For dark mode, switch the theme your app actually ships. We do not publish a hex color for your theme. The test is whether a person can read the label.
For the screen reader, use the platform’s reader. On the web, the region is an aside with aria-label="Advertisement", unless the snippet you were issued already renders that landmark. Do not add a second one. The placement page has the markup. On a phone, move from the native answer into the ad and confirm the same announcement.
Exercise the empty result
No-fill has to be a path you have seen, not a path you hope is fine. Stub an empty response in your own code and render the thread. The distance between the answer and the next real UI should be the same as a turn that never asked for an ad. Padding on the answer is fine. Padding that exists only because a slot component is mounted is a gap.
visibility: hidden and opacity: 0 fail this test. They keep the box. An empty container with no height, no padding, and no minimum height passes. Removing the node passes. A house ad fails. Placement states that rule, and the publisher guidelines state it too.
Go live
Go live only when every row above passes on the platforms you ship, and the account side is done. Local QA does not replace the traffic check.
Confirm the check has passed
Ads can be requested only after approval. If you are still waiting, keep the slot unwired to a live ID.
Use the issued publisher ID
The ID and the snippet come with the publisher agreement. Delete placeholders such as YOUR_PUBLISHER_ID and YOUR_SNIPPET_URL.
Set blocks, including under 18
The ad content policy stays the floor. Your extra blocks are on top. Ads are off for every account marked under 18.
Re-run the checklist on device
Web, and a phone at about 390px wide. Include dark mode if you ship it, and a screen reader pass.
Use test ads for any click
Open landing pages from test ads only. Do not click the live slot with a team account.
Turn the slot on for US traffic
There is no partial launch for other countries. A request that is not US traffic is not how you test a live integration.
After launch
Read the report for ad views, clicks, and US dollar amounts. A report does not describe a person, and it does not list a network rate. Reporting is the public page. Payouts follow the revenue share and the schedule in the agreement. Payments points at that document and does not quote it.
After each release that touches the thread, repeat the empty-result check and the label check. A CSS change is enough to leave a gap or to restyle the label away. The slot should still be outside the answer. The words should still be Ad · Sponsored.
You can pause ads. We can pause or end the relationship if traffic fails the quality bar or if the ad is no longer labeled. We will say the reason we can share. If a release hides the label, stacks slots, or requests on every token, pause and fix the release. If we paused ads, how they turn back on is in the agreement.
Watch the patterns the check refuses: bots, bought traffic, incentivized clicks, hidden slots. Do not “top up” a slow week with any of those. The traffic check is the ongoing bar, not only the first review.
Delivery events, if your integration uses them, are described for verified accounts on Webhooks. Event names and payloads are not public. The public count of what happened is the report, not a webhook catalog on this page.
When something looks wrong, start with Troubleshooting, then the contact page. We do not publish a support email, a phone number, or a response time.
What a test does not prove
- A test ad does not promise a fill rate. If nothing qualifies in production, you render nothing.
- A test ad does not promise a CPM. Up to $180 CPM is a ceiling, not a quote for your app.
- A passing checklist does not pass the traffic check. Approval is separate, and no approval time is published.
- A passing checklist does not open the matching method. That walk-through waits for an NDA. See Matching and targeting.
- Seeing one creative does not mean you chose it. Visor picks the card or the strip, and the campaign has its own review.