Contact ytcpm.online

What happens after you write

Every message reaches the same small inbox, so there is no ticketing system to learn and no account to create. A data correction is the most useful thing you can send, and the more context you include the faster it can be checked: the exact page URL, the number you believe is wrong, the number you expected, the country or niche it applies to, and where your figure came from. A Studio screenshot with the report range visible is ideal, but a plain description of the mismatch still helps.

Corrections that are supported by first-party data are applied to the benchmark and noted on the sources page. If a value turns out to be right, we will say so rather than change it. Feature requests for a missing country or niche are read against the same data set, so a request that names the audience country and the format you are comparing usually gets implemented; a request without that context rarely can be.

What not to send

Please do not email passwords, two-factor codes, OAuth tokens, session cookies or unredacted financial statements. We cannot use them, they will not be retained, and sending them creates a security risk for you. If a privacy question involves data we hold, describe the request and the page it relates to instead of attaching the raw record.

We also cannot recover a YouTube channel's private analytics, impressions, audience-country mix or revenue for you, and we do not need your login to help with a calculation question. If the number you are checking comes from the Channel Auditor, include the channel URL and what you expected to see, and the limitation that applies will usually be the answer.

Before you write

A large share of questions are already answered in the methodology page, the sources and limitations page and the guide to checking your own CPM in YouTube Studio. The Channel Auditor page also states exactly which figures it can and cannot show for a public channel.