Ads and UX

Frequency and UX guidelines

One labeled ad after the answer is the rule Visor states in public. How often you ask is a recommendation, not a published frequency cap.

Last updated · 8 min read

On this page

The hard rule is short. One ad per answer, after the answer, labeled Ad · Sponsored. Everything else on this page about how often to ask is a recommendation. Recommendations are for your product. They are not Visor frequency caps, and they are not a list of rejection reasons.

Visor does not need an ad on every answer. A turn with no request is allowed. A turn where Visor returns nothing is also normal. Both should render as no ad and no gap. They are different events: you did not ask, or you asked and nothing qualified.

The hard rule

A person asks. The app’s model answers. Then there is room for one ad, after that answer, with the label on it. The publisher guidelines say to show the model’s answer first, ask after that answer, render the card or the strip under it, keep the Ad label, and render nothing if the response is empty. The ad content policy says one ad is shown, not a stack, and the ad sits after the model’s answer, not inside it.

  1. One ad. Not two, and not a card plus a strip on the same answer.
  2. After the answer. Never inside the model’s words, and never before them.
  3. Labeled Ad · Sponsored. Plain text, top-left, never restyled away.
  4. Or nothing. If you do not ask, or if nothing qualifies, render nothing. No blank box.

Visor is not a pop-up, not an interstitial, and not a banner across the top of the screen. Those are not formats on this network. The slot is the card or the strip under the answer, or it is absent. Ad format is the spec for the unit itself.

Recommendations, not Visor rules

The headings below are recommendations. Visor does not detect a greeting, a short reply, a paid plan, or a sensitive topic. You decide whether to ask. If you do ask, the hard rule still applies to whatever comes back.

Do not request an ad on every short reply

A one-line courtesy is a weak place for an ad. “Sure.” and “You’re welcome.” are examples. The answer is real, and the hard rule would still put any ad after it, but asking on every short reply makes the ad louder than the product. Skip the request when the reply is only a courtesy. Visor does not publish a minimum answer length.

Skip greetings, errors, and refusals

If the model is saying hello, the app is showing an error, or the model is refusing the question, skip the request. There is no settled answer for an ad to follow. A greeting is not a result. An error is not a result. A refusal is the model stopping. If you do send a request anyway, you still render by the hard rule: one labeled unit after the text, or nothing.

Consider skipping the first answer of a session

Consider letting the first answer of a session stand alone, so the person sees the product before an ad. This is a consideration, not a Visor rule. There is no published session counter on this page, and there is no published definition of a session boundary. If you skip that first request, skip it in your app. Do not expect the network to count sessions for you.

A common pattern is ads on the free tier and no ads on the paid tier. People who pay for the product are not also shown the slot. People who do not pay can keep using the app, and advertisers pay a CPM for the views on the free tier. Visor does not require this split. Your pricing is yours. If the paid tier promises a quiet thread, do not request an ad on that tier.

One AI chat app grew its revenue by 80% with Visor. Another was able to go freemium on Visor ad revenue.1

1 Reported by the publisher. The apps are not named. Not a typical or promised outcome.

The freemium sentence is the pattern this section means: an app that can offer a paid tier because ad revenue covers a free tier. It is one unnamed app’s result. It is not a forecast, not a timeframe, and not a baseline you can plan on. The footnote is the whole caution. Do not add a month count. How you tell a free account from a paid account stays in your app. This page does not publish a tier field. Do not send a name, an email, or payment data to mark the tier. The allowed data is on Privacy.

No ads in sensitive moments

Do not request an ad in a sensitive moment. A health crisis and a conversation about self-harm are the examples used on Controls and brand safety. Visor does not need an ad on every answer. You choose not to ask. The network does not describe a detector for these moments, so do not wait for one.

The health-products block is separate. It stops a category of ads across the app. Skipping one request stops the slot on that turn only. You can do both.

No pop-ups, interstitials, or top banners

Visor is not those formats. Do not build them around the slot either. A modal over the answer, a full-screen interstitial between the question and the answer, or a banner pinned to the top of the chat are outside the product. The brand is built on one order: ask, answer, then one ad. A pop-up breaks that order even if the label is correct.

  • Do not pop a dialog over the thread when an ad arrives.
  • Do not gate the answer behind an interstitial.
  • Do not pin a second unit to the top of the screen.
  • Do not play the ad before the answer.

Animation, motion, and layout shift

The answer should stay where the person is reading it. The ad arrives after that, or it does not arrive. Do not reserve a tall empty box and collapse it later. That jump is the blank gap the guidelines forbid, and it moves the thread. Do not insert a placeholder that pushes the answer up to make room for an ad you might not get.

Visor’s own motion follows turn order. The question, then the answer, then the ad. The brand sheet describes Visor’s arrive motion as a rise of 8px and a fade, over 280ms, and it says prefers-reduced-motion: reduce turns that motion off. Those numbers are how Visor renders the unit. They are not a CSS spec for your app to copy. Do not add a pulse, and do not loop motion on the label. Layout shift from a no-fill is avoided by rendering nothing.

Measure the effect in your app

Retention is yours to measure. The terms of service say so. A thumbs-down rate, if your app asks people whether an answer helped, is also yours. Watch both after the slot is live. If people leave, or if they mark more answers down, treat that as a product signal. The recommendations above are the first levers: ask less often, skip sensitive turns, and keep the paid tier quiet if that is the promise.

Visor’s report counts ad views, clicks, and US dollars. It does not include a retention rate, and it does not include a thumbs-down rate. Reporting is the page for what a report counts. We do not publish a network benchmark for retention or for thumbs-down. Do not quote one.

Whose metric
MetricWho measures itWhere it lives
Ad views, clicks, US dollarsVisor, in aggregateYour report. Not a description of a person.
RetentionYou, in your appYour analytics. Not a Visor benchmark.
Thumbs-down rateYou, if your app has that controlYour product. Visor does not collect it.
How often you askYou, within the hard ruleYour integration. Not a public cap.

Network-side limits

No public number says how many ads a person may see in a session, an hour, or a day. If your publisher agreement sets a limit, that agreement controls. If the integration docs issued after the traffic check set a limit, those docs control. Neither number is published.

A sensible thread

Put the pieces together and a thread looks like this. The first answer of a session might carry no request. A later, full answer on the free tier might carry one request, and then either one labeled card or strip, or nothing. A “thanks” bubble carries no request. An error carries no request. A paid-tier thread carries no request, if that is your pattern. A crisis carries no request. Nothing in that list is a second ad, a pop-up, or a gap. Walk it once on a US account that is not marked under 18, and once on an account that is. The second walk should show no ad. Testing holds the longer checklist.

Questions

Is one ad per session the rule?
No. The rule is one ad per answer, after it, labeled. How often you request is your choice, plus any limit in your agreement. No public cap is stated here.
Do I have to request an ad on every answer?
No. Visor does not need an ad on every answer. Skipping greetings, errors, refusals, sensitive moments, and paid tiers is recommended. It is not required by a number on this page.
Can I show a banner at the top of the chat as well?
No. Visor is not a top banner, a pop-up, or an interstitial. Do not add those around the slot.
Will Visor tell me if retention drops?
No. Retention and thumbs-down rate are yours to measure. Visor reports ad views, clicks, and US dollars. It does not publish a benchmark for either product metric.

Was something unclear? Contact support