Advertising and free access

Why ads?

Some prompts may be locked; after the ad slot is shown and the server validates, text becomes visible and copyable. This keeps content free or low-cost.

Sponsorship transparency

Commercial partnerships or sponsored content may be labeled separately; regulatory alignment is the goal.

Google AdSense / publisher policies

Ad slots must be configured only after account approval and in line with publisher policies; on suspected invalid traffic or policy issues, pause the network and fix content. See official Google AdSense / GAM guides.

Brand safety and inappropriate ads

If you see misleading, aggressive, or off-brand ads, report via Feedback with a screenshot or advertiser hint when possible. Network-side complaint tools may also be used.

Cookies and CMP

Third-party ad or analytics cookies should load in line with CMP / header scripts from admin. Details: privacy.

Personalized advertising

Such ads are shown only with a valid legal basis and (where required) consent; you can also limit this in device or browser settings.

A/B placement experiments

Ad slot position and in-card order are measured via A/B Settings JSON (admin); compare RPM/CPM with site events. Aim for one variable per experiment and enough sample size.

Backfill ad network

If the primary network is unfilled, use house messaging or a secondary network; follow the ops runbook for full swaps. Staging keeps real production tags off.

Mobile anchor / sticky ads

On mobile web, frequency and screen share for sticky units follow policy; no fullscreen interstitials (cards use data-interstitial-policy=no-fullscreen).

Viewability and measurement

Viewability targets are tracked in network reports; min-height reservation and lazy loading limit CLS. Load measurement after CMP/consent when recommended.

Traffic source and CTR anomalies

Cross-check the ad network and site_events on sudden CTR spikes from one source or datacenter; pause campaigns per procedure if suspicious.