Integrate
Mobile apps and webviews
iOS, Android, React Native, Flutter, and webview apps follow the same rule: one labeled ad after the answer. Package install steps stay in the verified SDK docs.
On this page
iOS, Android, React Native, Flutter, and webview apps use the same rule as the web. One labeled ad sits after the finished answer. Nothing sits inside the answer. If there is no fill, the app renders nothing and leaves no gap. The phone does not get a second format.
What changes is the shell. You either render the web slot inside a webview under the native answer, or you render natively from a response your server already fetched. Packages for approved apps exist. Their install steps are not on this page.
The same rule on the phone
- The person asks in the app.
- The model finishes the answer. Visor is not in that step.
- If the answer is a refusal, an error, or empty, skip the slot.
- If the account is marked under 18, skip the slot.
- Ask once, then render a card or a strip under the answer, or render nothing.
The label is Ad · Sponsored, plain text, top-left. The wording does not change. The ad does not use the assistant’s avatar. It is not a pop-up, not an interstitial, and not a banner across the top. Placement is the full rule. There is no mobile exception.
No ad is requested before approval. The publisher ID, the integration snippet, and SDK access arrive after the traffic check, with the publisher agreement. Publisher onboarding is that sequence. US traffic only. There is no partial launch for other countries.
Packages for approved apps
Approved apps receive packages for web, iOS, Android, React, and Node. The configure step uses the publisher ID you were issued. What the request may include, and what it must not include, is the same public list as everywhere else: the current conversation or a short topic summary, anonymized in-app signals, device type, country, an under-18 flag, and a pseudonymous identifier.
Install commands, version numbers, and repository URLs are not public. Sign-in is not connected yet, so it does not open them.
React Native and Flutter
We do not publish a package name for React Native or Flutter on this page. Those apps have two supported approaches, and both keep the placement rule.
- Render the web slot inside a webview under the native answer. The web snippet page is the slot. The native page is the answer.
- Ask from your server, and render the card or the strip natively from that response. Server-side integration is the request. Ad format is what you are allowed to draw.
Do not add a third layout because the toolkit is different. Do not put the ad in a native dialog. Do not attach it to a push notification. The ad is in the thread, after the answer, or it is absent.
A webview under the answer
If the whole product is already a webview, follow the web snippet and keep the placement rules. If the answer is native and only the ad is web, render the native answer first. When that answer has finished, show a webview under it that loads the slot. Do not cover the answer with the webview. Do not load the webview on the first token.
Give the webview a height that follows the ad. If the response is empty, collapse the webview so there is no gap. A webview with a fixed height and a blank document is a reserved gap. Remove it. JavaScript has to be enabled in that webview or the snippet cannot run. If you cannot enable JavaScript, use the server-side path and draw natively instead.
You do not need to relax the webview’s cookie policy for Visor. Matching does not use a third-party cookie. Do not turn on third-party cookies “so the ad works.” It does not need them, and the cookie notice says we do not use a cookie to decide which ad to show.
If the native app exposes the webview to assistive technology, name that region Advertisement, the same way the web landmark does: an aside with aria-label="Advertisement" inside the web content, or the native equivalent that announces an advertisement. The visible label still has to read Ad · Sponsored. Do not rely on the accessible name alone.
Render natively from your server
Your server asks after the answer, using only the allowed data. Your app paints the card or the strip that came back. You do not design a third format. The label stays plain text at the top-left. If the body is empty, or you cannot map it with the format in your integration docs, paint nothing.
The public formats are a card (a picture or banner, a name, one or two sentences, a link or button) and a strip (one line: the label, a short sentence or name, a link). Visor picks which one returns. The response fields that carry those parts are not public. They are in the verified API reference. Until you have that document, do not guess field names and ship them.
Keep the ad out of the assistant’s layout. A native cell that reuses the assistant’s avatar will be read as the assistant. Use a separate cell, under the answer cell, full width of the thread. On a narrow phone the order does not change.
Where the click opens
Open the click in the system browser, or in the platform’s in-app browser, rather than inside the chat webview. On iOS that in-app browser is a Safari view. On Android it is a custom tab. This is a recommendation. The chat stays where the person left it. The landing page can be a real page, which the ad content policy requires when the ad has a click.
Do not navigate the chat webview itself to the advertiser. The person would lose the thread, and the ad would feel like the app had changed into the ad. Do not open the click as a new message inside the chat. The ad is not the assistant continuing the conversation.
app-ads.txt
A website uses ads.txt to name who may sell its inventory. A mobile app uses app-ads.txt for the same job. The file is published on the developer website listed for the app. Visor’s line, once issued, belongs in the file you control. The line is not listed on this page. It is issued with the publisher agreement.
See ads.txt and sellers.json for what those files are, and for the fact that the Visor line is not printed in the docs. Do not copy a line from another network and change the name. Wait for the line you are issued.
Device advertising IDs
Visor does not ask for the device advertising ID. That includes the iOS Identifier for Advertisers (IDFA) and the Google Advertising ID (GAID). Matching does not use them. Do not send them. You do not need to request tracking permission in order to pass a device advertising ID to Visor, because Visor does not want that ID.
Do not put the advertising ID in the pseudonymous identifier field. A pseudonymous identifier is a stand-in you choose. It is not a platform advertising ID, and it is not a name. The privacy policy lists what matching never wants, including a profile that follows a person across the web.
App Tracking Transparency
App Tracking Transparency is Apple’s prompt before an app tracks a person across other companies’ apps and websites. Visor does not track a person from app to app. It does not use a third-party cookie, and it does not follow someone from site to site. Matching stays inside the chat app.
Whether your app must show Apple’s prompt depends on the rest of what the app does. Other libraries can change that answer. This page is not legal advice, and it is not a reading of Apple’s rules for your binary. The privacy policy is the source for Visor’s data rules. Your counsel reads the platform rules for everything else you ship.
Under 18, and children under 13
Turn ads off for every account marked under 18. Do not request an ad for that account on the device, in the webview, or on the server. A publisher can mark an account as under 18. We then do not request an ad. Do not send a birth date.
Apps directed at children under 13 are not a fit. Do not rework a children’s app to add a slot. This page does not interpret child-privacy statutes. The product rule is the privacy policy and the publisher guidelines.
Before you ship, walk Testing and go-live on a real phone. A desktop preview of a webview misses the click path, the collapse on no-fill, and the way a screen reader moves from the native answer into the ad.