White and Offer Page URL and Render Methods

Understand Render Methods, Use Cases, and Strategic Impacts in XCLO Campaign Builder.

🧩 Key Definitions

✅ What is a White Page URL?

The White Page is your safe page – shown to filtered traffic such as:

  • Ad reviewers and bots
  • Traffic failing filters (GEO, device, UTM, etc.)
  • Users you intentionally want to hide your offer from

This is typically a clean, harmless, or “legal” page to satisfy compliance or reduce risk of bans.

Example: https://yourdomain.com/safe.html

✅ What is an Offer Page URL?

This is your actual landing page where conversion happens – the true goal of your campaign.

Example: https://affiliate-network.com/landing?id=123

🔄 Render Methods – How XCLO Delivers Pages

Render method defines how XCLO shows either the white or offer page to the visitor. This choice directly impacts speed, stealth, and tracking.

🧱 White Page Render Methods

1. CURL (server-side)

  • XCLO server fetches and renders the white page’s HTML internally
  • Only shows the final result to the user, hiding the true URL

✅ Pros:

  • Highly stealth — ideal for Facebook & Google cloaking
  • Does not trigger redirects

❌ Cons:

  • Does not support interactive white pages (e.g., JS, forms)
  • Can break pages needing cookies or sessions

2. 302 Redirect

  • Redirects the user using HTTP 302 status to the White Page URL

✅ Pros:

  • Fast and compatible with most browsers
  • Supports JavaScript and login pages

❌ Cons:

  • URL is visible to crawlers
  • Ad reviewers may follow the redirect chain

🎯 Offer Page Render Methods

1. Meta Refresh

<meta http-equiv="refresh" content="0;url=https://your-offer.com">

✅ Pros:

  • Simple obfuscation – avoids direct 302 redirect
  • May delay scrapers or bot detection

❌ Cons:

  • Slower load than 302
  • Some browsers block tracking during redirect

2. Iframe

<iframe src="https://your-offer.com" width="100%" height="100%"></iframe>

✅ Pros:

  • URL does not change in browser
  • Fast and seamless user view

❌ Cons:

  • Many offers block iframe with X-Frame-Options
  • Pixels and tracking may not fire correctly

3. 302 Redirect

  • Direct redirect via HTTP header to the offer URL

✅ Pros:

  • Full tracking and pixel compatibility
  • Fastest method

❌ Cons:

  • URL is fully exposed
  • Scrapers and bots can follow

📊 Comparison Table

Method Stealth Pixel Friendly Supports JS Ideal Use Case
CURL (White) ✅✅✅ ✅ ❌ Facebook cloaking, legal landing clones
302 (White) ⚠️ ✅ ✅ TikTok, mobile redirects, login white pages
Meta Refresh (Offer) ✅ ⚠️ ✅ Affiliate links with cloaking intent
Iframe (Offer) ✅ ❌ ✅ Internal tracking or demo/testing
302 (Offer) ⚠️ ✅✅✅ ✅ Direct-to-offer campaigns, push traffic

🧠 Best Practices

  • Use CURL for stealthy white pages on FB/Google
  • Use 302 (Offer) if pixel accuracy is mission-critical
  • Use Iframe only for private offers or testing
  • Use Meta Refresh if you want basic redirection stealth

📌 Summary

Choosing the right render method in XCLO is a strategic decision. You balance stealth vs. performance, speed vs. tracking accuracy. There’s no one-size-fits-all — tailor your setup based on platform, offer type, and traffic source.