Skip to main content
Answers to frequently asked questions about the AdXensor publisher integration.

General

Yes. Create a publisher account at publisher.adxensor.com, add your site, and complete the onboarding steps. Once your site is approved you will receive a Site ID.
Yes. There is no cost to install or use the SDK. You earn revenue from each valid impression and click on the ads served to your visitors.
The SDK does not read cookies, fingerprint devices, or collect personally identifiable information (PII). Country, browser, and OS are resolved server-side from the visitor’s IP address and User-Agent string. Session IDs are stored in sessionStorage and are never shared with third parties.
AdXensor currently serves ads in Benin, Côte d’Ivoire, Togo, Senegal, Niger, Burkina Faso, Mali, Guinea, and Mauritania. Visitors from other countries may not see ads; the slot will remain empty.

Technical

No. Use one method only. Loading both will result in duplicate initialization and duplicate events.
The SDK is browser-only. It must not be executed on the server. Initialize inside useEffect (React/Next.js) or onMounted (Vue). See the Next.js guide for SSR-safe patterns.
Lazy loading delays the ad request until the slot is near the viewport. This reduces wasted requests for slots the user never scrolls to, which can improve your fill rate and effective CPM. It is enabled by default.
Yes. Place as many <ins> tags as you need, each with a unique data-ad-slot name.
The SDK reserves the slot dimensions at fill time based on the requested format. If you need responsive resizing after the fact, use data-ad-format="auto" and ensure the parent container has a defined width at the time the slot enters the viewport.
1

Enable debug mode

Enable debug mode (data-debug attribute or debug: true in config).
2

Open the browser console

Open the browser console — you will see logs for every slot found, every API call, and every event fired.
3

Check your dashboard statistics

Check Publisher Dashboard → My Sites → [Your Site] → Statistics for incoming pageviews.
Yes. See the CSP section in the Troubleshooting guide for the required directives.
Ad blockers will typically block requests to AdXensor CDN and API domains. This is a known limitation shared by all ad networks. There is no reliable way to bypass ad blockers without violating user trust.

Payments & Revenue

Payments are processed monthly via mobile money (MTN Mobile Money, Moov Money, and other supported operators). Your earnings are visible in the Publisher Dashboard under My Wallet. Contact support@adxensor.com for payout details.
The most common reasons:
  1. Your site status is not Active yet.
  2. You are testing with an ad blocker enabled — disable it.
  3. There are no active campaigns targeting your audience at this time.
  4. Your data-ad-client value is incorrect.
Enable data-debug and check the browser console for diagnostic output.