Get started

Quickstart

Create a free account, pass the traffic check, and place one slot under the answer. The publisher ID, the integration snippet, and SDK access come after the check, not before.

Last updated

On this page

This is the fast path, and it is an honest one. You can create an account today. You cannot show an ad today unless the traffic check has already passed. The publisher ID, the integration snippet, and SDK access are issued after that check. They are not on this page.

Eight steps

  1. Create a free account

    Open the signup form and create the account. The form records the application. It does not turn ads on, and it does not skip review.

  2. Describe the app

    Name the chat app and say how a person uses it. Review needs a real product someone can open, not a description of a product you might build later.

  3. Pass the traffic check

    Visor looks for a real US chat app and real traffic. Ads do not start until the check passes. No approval time is published. The traffic check says what is public about review.

  4. Receive a publisher ID, a snippet, and SDK access

    After the check passes, Visor issues a publisher ID, an integration snippet, and SDK access. You cannot get them before that. They are sent with the publisher agreement, not pulled from a public URL.

  5. Place the slot after the answer

    The slot sits under the model’s words, never inside them. One slot, one ad. Visor picks a card or a strip. You do not design the unit. The samples further down are illustrative.

  6. Render nothing on no fill

    If Visor returns no ad, render nothing. Do not leave a blank box, a skeleton, or a gap where the ad would have been.

  7. Set category blocks

    Block anything you do not want, on top of the categories that never run. Turn ads off for every account marked under 18. The network list is the ad content policy.

  8. Test, then go live

    Check the label, a real no-fill, the under-18 switch, and a US request. Then the slot can go live. Testing and go-live holds the longer checklist.

The publisher ID, the snippet, and SDK access

People ask for the install line before the check. There is not one to copy. The ID identifies your app on requests. The snippet is how a site loads the slot. SDK access is the package for an approved app. All three are issued after the traffic check passes. Sign-in is not connected yet, so there is no account area to open.

Place the slot after the answer

Put the slot in the thread after the answer component, as the last thing in that turn. Do not insert it between sentences of the answer. Do not put a second slot under the same answer.

Illustrative: slot after the answertsx
import { AdSlot } from "@visor/react";

export function Thread({
  messages,
}) {
  return (
    <>
      <Answers messages={messages} />
      <AdSlot
        publisherId="YOUR_PUBLISHER_ID"
        messages={messages}
        locale="en-US"
        country="US"
      />
    </>
  );
}

In the React sample, Answers is your component. AdSlot stands where the ad goes, after those words. publisherId, messages, locale, and country show the idea of the call. They are not a field list for a live API. In the JavaScript sample, the script address is YOUR_SNIPPET_URL. renderNothing is your function for an empty slot. It is not a Visor callback with a published name.

When there is no ad

No-fill is a normal result. Nothing qualified, so nothing renders. The thread should look as if you never asked: the answer, then the next thing your app was already going to show. A reserved gap reads as a broken layout. A blank card reads as a missing ad. Both are wrong.

Category blocks

Some categories never run on the network. That list is fixed, and the ad content policy is the source. On top of it, a publisher can block more.

  • Alcohol.
  • Dating.
  • Health products.
  • Loans and other credit offers.
  • Specific advertisers, and any brand or domain you name.
  • Every account marked under 18. Turn ads off for those accounts.

Where those switches sit for a verified account is part of the locked controls, not this public page. You can decide the blocks before the first ad. You do not have to wait for a live slot to know what you will refuse.

Test, then go live

Before the slot is live, walk one thread as a person would. The answer comes first. The label reads Ad · Sponsored, in plain text, at the top-left of the ad, if an ad is there. If you force a case with no qualifying ad, the thread closes up with no gap. A request that is not US traffic should not be how you test a live integration.

Also confirm the under-18 switch. An account marked under 18 does not get an ad. Apps directed at children under 13 are not a fit for the network at all.

Next steps

The eight steps above are the whole public fast path. These pages go further on one part each.

Was something unclear? Contact support