Contact

Contact and corrections

Use this page when you need to flag a broken assumption, outdated platform rule, sourcing issue, or legal request related to AdsRPM.

Key links

Editorial policy

See how source reviews, benchmarks, and correction handling work before you send a request.

Public profile

Current public profile: @adsrpm. Use it for launch-stage contact routing and visible correction requests.

When to use this page

Good reasons to reach out

Report a broken calculator path, a platform monetization change, or a source link that no longer matches the published page copy.

Use the same route for legal notices, policy concerns, or clear factual corrections that affect a live page.

Include the exact page URL, the affected metric or sentence, and the source that supports your correction.

If the issue is about an RPM benchmark, explain whether the challenge is the platform rule, the modeled assumption, or the labeling around it.

Corrections

How updates are handled

Corrections are reviewed against primary platform documentation first. When the issue affects a benchmark assumption, the underlying snapshot and source references are checked before publishing a change.

When a correction changes a live estimate or guidance page, the page source verification date and the corresponding assumption snapshot should be updated together.

Primary-doc conflicts take priority over older benchmark assumptions.

Ambiguous monetization rules are labeled as modeled estimates rather than presented as guaranteed payouts.

Requests

Commercial and legal requests

Use the same contact route for rights requests, terms questions, or commercial inquiries tied directly to the site.

Do not send passwords, payment details, or sensitive personal information through public contact channels.