Installing your sponsor wall

1. Copy your code

Your listing generates the exact snippet, with your own site ID and verification code already filled in. Open your listing, go to Install, and choose Copy code. It looks like this:

<div data-sponsor-site="YOUR-SITE-ID" data-sponsor-verify="YOUR-CODE" style="display:none!important" hidden></div>
<script async src="https://www.sponsorslot.app/embed/loader.js"></script>

The div marks where the wall goes. The script draws it. Neither one sets a cookie, stores anything in the browser, or identifies your readers.

2. Paste it under your hero

Directly below your hero section is where a sponsor wall belongs, and it is what buyers expect when they land on your page from a tile. The wall renders inside the container you pasted, at the width its parent gives it, so it inherits the layout you already have. Your own margins and grid gaps stay yours.

Put it on the exact page you saved on your listing. One paste per site, however many tiles you sell — the wall holds all of them, and you change how many from your listing without touching this code again.

The same paste serves a side rail. If you choose Side rail instead of a block in the page, the wall lifts out of the flow and pins itself to your right margin — you change nothing here. On a screen too narrow to have a margin it drops back into the page, exactly where this code sits, so paste it somewhere it reads well either way.

3. If your site is React, Next.js, or similar

Render the container in the page’s initial HTML — a server-rendered component, not one that only appears after JavaScript runs. Our check reads the published HTML and does not execute your JavaScript, so a container created in the browser is invisible to it. Your listing offers a React version of the snippet under the React / Next.js tab.

For an app that renders entirely in the browser, you can prove ownership with a DNS record instead, from the Need another way to connect? section of the install step. That confirms the site is yours; the snippet is still what delivers the sponsorship.

4. Publish, then check

Deploy your site so the change is live at its public address. Then come back to Install & preview and choose Check installation. You can close the tab and come back later — your draft is saved, and nothing is lost by waiting for a deploy.

5. Your wall is already working

You do not have to wait for a first sponsor. An empty wall is the point: every open tile tells your readers the space is available and what it costs, and someone already reading your page is the best-qualified sponsor you will ever get. Your listing shows the wall exactly as your readers see it, before and after you install it.

If the check does not find your code

Nearly every failure is one of these:

• The page is not published yet. The check reads your live site, not your local copy or a preview build behind a password.
• A different URL. It looks at the exact page saved on your listing. If that address redirects somewhere else, save the final address instead.
• The container is not in the HTML. Code inside a comment, an escaped code sample, a <template>, a <noscript>, or a JavaScript string does not count as installed.
• The snippet was edited. The site ID, the verification code and the script address all have to match what your listing generated.
• A login or bot challenge. We need to read the page the way an ordinary visitor would.

If your site sets a Content Security Policy

Most sites do not, and can skip this. If yours does, allow https://www.sponsorslot.app in both script-src and frame-src. Without it the browser blocks the snippet silently: the check may still pass on the markup, but the wall never renders for your readers.

Turning it off

You keep the switch. Disable delivery on your wall’s page takes the whole wall down within thirty seconds, and a wall that fails to load collapses to nothing rather than leaving a gap. Removing the snippet from your page works too. Campaigns you have already agreed to are settled with an operator, not by pulling the code.