Integration Verification

This guide helps you verify that Ad Sentinelle is properly integrated on your site.

Verification Checklist

✅ 1. Script is Loaded

Open the developer tools (F12) and check in the Network tab:

• The SITE_ID.js script is loaded with status 200
• The script comes from adwall-backend-xxxxx.run.app

✅ 2. SDK is Initialized

In the Console, you should see:

✅ Ad Sentinelle SDK initialized
✅ Session ID: abc123-def456-789...
✅ Config loaded for site: SITE_ID

✅ 3. Detection Works

With an ad blocker enabled, you should see:

✅ Adblock detected: true
✅ Detection method: bait
✅ Wall displayed

✅ 4. Wall Appears

• Wall appears as overlay on the page
• Title and message are visible
• CTA button is clickable
• Style matches your configuration

✅ 5. Conversion Works

1. Disable your ad blocker
2. Click the CTA button
3. Verify in console:

✅ Verification started
✅ Adblock disabled confirmed
✅ Conversion tracked
✅ Wall removed

Test with Different Ad Blockers

Test with multiple ad blockers to validate detection:

Ad Blocker	How to Test
uBlock Origin	Chrome/Firefox extension
AdBlock Plus	Chrome/Firefox extension
AdBlock	Chrome extension
Brave	Brave browser with shields enabled

Verification in Dashboard

After your tests, verify in the Ad Sentinelle dashboard:

1. Go to Analytics → Real-time
2. Verify your test sessions appear
3. Verify events:
   • adblock_detected
   • adwall_displayed
   • conversion_allowlist (if conversion completed)

Debug Mode

Enable debug mode for detailed logs:

<script>
  window.ADWALL_CONFIG = { debug: true };
</script>
<script src="https://adwall-backend-xxxxx.run.app/v1/loader/SITE_ID.js" async></script>

Debug Logs

[Ad Sentinelle Debug] Init started
[Ad Sentinelle Debug] Session ID: abc123...
[Ad Sentinelle Debug] Variant assigned: control
[Ad Sentinelle Debug] Starting adblock detection...
[Ad Sentinelle Debug] Bait element created
[Ad Sentinelle Debug] Bait element blocked: true
[Ad Sentinelle Debug] Network test started
[Ad Sentinelle Debug] Network test blocked: true
[Ad Sentinelle Debug] Detection result: BLOCKED
[Ad Sentinelle Debug] Checking conversion status...
[Ad Sentinelle Debug] User not converted, showing wall
[Ad Sentinelle Debug] Wall template loaded
[Ad Sentinelle Debug] Wall displayed
[Ad Sentinelle Debug] Event tracked: adwall_displayed

Common Issues

Script Doesn't Load

Possible Causes:

• Incorrect script URL
• Invalid Site ID
• Network issue

Solutions:

1. Check URL in dashboard
2. Check for typos in Site ID
3. Check console for CORS errors

Wall Doesn't Appear

Possible Causes:

• Ad blocker not active
• User already converted (cookie present)
• Site not configured

Solutions:

1. Verify your ad blocker is enabled
2. Delete adwall_* cookies and retry
3. Check site configuration in dashboard

CORS Error

Access to script at 'https://...' from origin 'http://localhost:3000' 
has been blocked by CORS policy

Solution: Add your domain (including localhost for testing) to authorized domains in the dashboard.

Wall Appears Without Ad Blocker

Possible Causes:

• False positive detection
• Extension blocking certain resources

Solutions:

1. Disable all extensions and retry
2. Contact support with details

Testing Tools

Development Extension

Use the Ad Sentinelle development extension (available on request) to:

• Force wall display
• Simulate an ad blocker
• Reset cookies
• View events in real-time

Ad Sentinelle Console

In the browser console:

// Force a new detection
window.AdSentinelle?.check()

// Get session ID
window.AdSentinelle?.getSessionId()

// Reset (delete cookies)
document.cookie = 'adwall_converted=; max-age=0; path=/'
document.cookie = 'adwall_seen=; max-age=0; path=/'

Validate in Production

Before deploying to production:

1. Test on a staging environment
2. Verify mobile behavior
3. Test different browsers
4. Validate analytics in dashboard
5. Disable debug mode

Important

Don't forget to disable debug: true in production to avoid cluttering your users' console.