CFAMM + ADMENSION
◼ CFAMM + ADMENSION v1.2 Advanced Publisher Stack
page=— s=1/3 dev=— pv=— adsShown=— score=— adm=—

The Only Link Shortener That Pays You — Automatically

No signup. No dashboard. No referrals. Share a link → people browse → ads run → revenue is pooled and distributed.

How it works (10 seconds):
1) Share your link
2) Visitors browse naturally (no timers, no tricks)
3) Ads earn revenue
4) Pool + proportional payout (only after real settlement)
No revenue = no payout.
Read the Docs View Transparency Stats Admin
HOME — Top Banner

Try it (demo flow)

Use the buttons below to run the 3-step flow. This increases pages/session via user intent (policy-safe).

Reminder: Do not add timer-based ad refresh. Only refresh/change on user intent (route / step).

3-step flow

Use the buttons below to cycle steps (creates controlled PV/session without auto-refresh).

Step 1 of 3
labels utm_content
Reminder: Do not add timer-based refresh. Only refresh ads on user intent (page/nav/step).

Create

Create a share link in this browser (signup‑free).

CREATE — Desktop Rail

Manage

View links created in this browser and manage local data.

—
MANAGE — Desktop Rail

Docs

Idiot-proof, blunt, and accurate. If you read this page, you understand the whole system.

DOCS — Top Banner

1) What this is (in one sentence)

CFAMM is a signup-free link shortener + browsing flow that earns ad revenue, then (optionally) shares a fixed portion via a transparent pool model.

Share link → people browse → ads earn → revenue settles → pool is funded → payout is proportional.

2) The only rule that matters

No revenue = no payout.
Ads must earn money and the ad network must pay out for the month before any pool distribution can exist. Anything else is fantasy.

3) How payouts actually work (simple math)

Pool = min( monthly_cap , received_revenue_this_month × pool_percent )
Your share = your_units ÷ total_units
Your payout = pool × your_share

Units are NOT dollars. Units are just a contribution counter used to compute percentages. The pool is funded after revenue exists.

4) What’s real vs. what’s local (important)

Local (this browser only):
  • Stats, projections, sponsor schedules, monthly summaries
  • Admin settings (PIN unlock), density toggles, context skins
Real-world (requires deployment + ad network):
  • Actual ad revenue
  • Actual settlement totals
  • Actual sponsor payments
This file is intentionally designed so you can test flow and UX safely without pretending revenue is real.

5) Policy safety (how we avoid bans)

This build is designed to stay within ad-network rules:
  • No auto-refresh timers for ads
  • No incentivized clicks (no “click to earn”, no “watch to earn”)
  • Ads refresh only on user intent (navigation / step change)
  • Support modal is optional and not tied to rewards
If you break these rules, you risk losing the ad account. Don’t.

6) Why this can earn even at low traffic (10–250 DAU)

Most sites die at low traffic because they have low intent and low session depth. CFAMM focuses on:
  • High-intent framing (calculator / estimator / reference contexts)
  • Session depth via legitimate “next step” routes
  • High viewability (anchor + side inventory stays visible)
  • Sponsors that buy presence, not volume
Low traffic won’t make you rich — but it can still be worth running.

7) Context Skins (how to raise CPM without changing layout)

Context Skins change title/meta/copy so different advertiser auctions compete. Same layout. Same ads. Better bids.
  • Calculator: utility intent
  • Estimator: decision intent
  • Reference: authority intent
  • Checklist / 2026: urgency/recency signals
Tip: clones across multiple domains/paths compound this effect.

8) Geo Tier Density (why we hide ads for low-value traffic)

Some traffic is low-CPM. Overserving it hurts RPM overall. Geo Tier Density lets you render fewer placements for Tier-3 while keeping Tier-1 premium.
  • Tier‑1: full inventory
  • Tier‑2: balanced
  • Tier‑3: light (protects RPM)

9) Sponsored Stickies (the low-DAU income hack)

Sponsors buy 72 hours of visibility — not clicks and not promises. This works even at low DAU because it’s “presence” inventory.
Suggested tiers (same layout, different coverage):
  • Base: one sticky slot
  • Plus: sticky + one additional placement
  • Premium: sticky + all contexts (Calculator/Estimator/Reference)
Always keep language neutral: “placement / visibility”, never “guaranteed results”.

10) Demand stacking + header bidding (when you’re ready)

This file is ready for demand stacking, but it is not included by default.
  • Start with one ad network until stable traffic
  • Add a fallback network if fill is weak
  • Only consider managed header bidding after you have steady usage and clean policy history
Header bidding can lift RPM, but it adds complexity. Don’t rush it.

11) Quick start checklist (deploy)

  1. Host the file on static hosting (anywhere)
  2. Replace placeholder ad blocks with your network tags
  3. Keep no timers, no incentives, navigation only
  4. Use Admin to tune density + context skins
  5. Track outcomes with real analytics (optional)

12) FAQ (common confusion)

Q: Do I need an account?
A: No. This build is signup-free by design.

Q: Are payouts guaranteed?
A: No. Payouts exist only after real revenue settles.

Q: Can I refresh ads automatically?
A: Don’t. It’s one of the fastest ways to get banned.

Q: What matters most at low traffic?
A: Session depth, viewability, context quality, and sponsors.

Fast navigation

Non-negotiables

  • No auto-refresh timers
  • No incentivized clicking
  • No “watch to earn”
  • User-intent navigation only
DOCS — Desktop Rail
DOCS — Desktop Rail

Transparency Stats

Local transparency counters (for optimization only).

Sessions (24h)
—
Pageviews (24h)
—
Ads shown (24h)
—
Ads/PV (24h)
—
Sessions (7d)
—
Pageviews (7d)
—
PV/session (7d)
—
Desktop share
—
Reached Step 3
—
Top source
—

Admin

Local controls, sponsor scheduling, and safety notes. Admin actions require your admin PIN.

Projection + last-month inputs (local)

Because payouts are not known until the end of the month, the progress bars use projected month revenue. After settlement, fill “Last month summary (latest settlement)” to show real outcomes.
Planning-only estimate for the current month.
Conservative default. Planning only.
HOME — Desktop Rail
HOME — In-Content Tall (engagement-gated elsewhere)
HOME — Footer Banner

Admin unlock

Admin features are locked so random visitors can’t mess with local data. Click Unlock and enter your admin PIN to use sponsor controls and reset.
locked

Sponsored sticky (72-hour) manager

Hard limits: 90 days ahead, 72 hours each, ≤9 per window, ≤270 total scheduled in horizon.
How start time works: You provide a start time; the system auto-sets end time = start + 72h. Use UTC format to avoid timezone confusion. If blank, it uses “now rounded up to next hour”.

Scheduled sponsors (local)

—

Reset (PIN)

This clears data for this browser only.

Monthly summaries (history)

Add up to 3+ monthly settlement summaries. Once there are 3 saved monthly summaries, the system switches the pool cap to $100,000/month for future projections.
Use the month that just settled.

Saved summaries

Shown newest → oldest.
—

Compliance basics (don’t get banned)

• Don’t auto-refresh ads on timers.
• Don’t incentivize clicks or tie “earnings” to ad interaction.
• Refresh/change ad slots only on user intent (route/step).
• Sponsored sticky must be labeled.




ADMIN — Desktop Rail
ADMIN — In-Content Tall

Ad Funnel & Processing (How revenue happens)

This page explains the ad flow in plain language. This is a static single-file build: it shows placeholders and logs user-intent navigation. Real ad revenue is created only when you publish with a real ad provider and follow their policies.

1) The funnel (why the site earns)

2) Ad inventory on the site

3) What this build logs vs what an ad network pays

4) Policy safety (why we avoid refresh spam)

72‑Hour Sponsored Stickies (Paid Rotation)

Sponsors are scheduled in 72 hour windows. A window can contain up to 9 sponsors. This UI can display up to 3 at a time (bottom + left + right), rotating by user navigation (not timers).

How sponsors are selected

If no sponsors are booked

Sponsor quality rules

ADMENSION Pool Math (Transparent, post‑revenue)

RPM Optimization Manual (Ad-only, policy-safe)

This system is designed to maximize legitimate ad revenue via user-intent navigation and high viewability. It does not use auto-refresh timers or incentivized ad interaction.

1) What this site is

2) Placements (defined once)

3) User-intent impressions (why this is compliant)

4) Progressive reveal (viewability-first)

5) Geo-weighted density

Higher-paying geographies can support more placements without harming RPM. Lower CPM traffic uses a lighter density to keep average RPM higher.

6) What we explicitly do NOT do

7) Stats vs payouts

Advanced Publisher Controls (v1.3)

Tune density and CPM assumptions by geo tier. Affects rendering + estimates (not a promise).

Context Skin

Same engine, different copy/meta for stronger ad context.

Traffic Tier Simulator

For testing density rules locally. In production this can be wired to geo signals later.

Context Skin

Same engine, different copy/meta for stronger ad context.

CPM assumptions (for estimates)

Used only for Stats estimation. Not a guarantee.
Tier-1 CPM:
Tier-2 CPM:
Tier-3 CPM:

Placement Density by Geo Tier

Avoid over-serving low CPM traffic. Toggle what renders per tier.
Tier-1 (Premium)




Tier-2 (Balanced)




Tier-3 (Light)




Advanced Publisher Stack (v1.2)

This build adds publisher-grade knobs and diagnostics: funnel conversion, geo-tier density tuning, context skins, duration bins, and placement-weighted RPM estimation — while staying policy-safe (no refresh timers, no incentivized clicks).

Decision rules (stair-climb)

Compliance stance

ADMIN — Desktop Rail
ADMIN — In-Content Tall
Sponsored · 72-hour feature
—