The short answer
If your page promotes credit card offers to US users, the documented rule is a clear no for personalized advertising in the named categories: you may not target by gender, age, parental status, marital status, or postal code. Google’s publisher policy lists credit cards and loans as examples of credit-related products and services, alongside banking products and certain financial planning and management services. It also treats negative financial-status information, such as signals of a low credit rating or high debt burden, as sensitive information that cannot be used for personalization. The retrieved text is illustrative, not an exhaustive category ruling.
What the restriction covers
The policy groups three categories under the same US and Canada personalized-ad limit. The named examples are illustrative; the retrieved text does not draw a complete category boundary.
| Category as named in the retrieved policy | Examples named in the retrieved policy text | Gender, age, parental status, marital status or postal code barred for personalized ads in the US and Canada | Scope note |
|---|
| Credit-related products or services | Credit cards and loans | Yes | Examples are illustrative; the retrieved text does not define the category boundary exhaustively. |
| Banking products and services | Bank and checking accounts; debt management products | Yes | Debt management products are named as an example under this grouping in the retrieved text. |
| Certain financial planning and management services | None named in the retrieved text | Yes | The retrieved text says “certain” services but does not enumerate which ones. |
The shared “yes” matters more than the examples. A credit card comparison page sits in the first row; a page mixing card offers with checking-account promotions spans two rows. The third row is undefined in the retrieved text, so do not infer a complete boundary.
Credit-status signals are a separate bar
Even if you avoid the five demographic and location signals, “bad credit” or “high debt” audiences are not a workaround. The retrieved policy bars personalization based on inferred or actual sensitive information and explicitly names negative financial-status information, including signals showing a low credit rating or a high debt burden. That makes a segment such as “credit-challenged applicants” a sensitive-data problem, not merely a demographic-targeting problem. The rule is about the input used to select the ad, so renaming the segment does not change the analysis.
If interest-based audience data remains
If you still run interest-based campaigns through Google products or Google ad code, the retrieved policy sets three separate obligations. First, you must hold all necessary rights to audience data such as cookie lists. Second, the ads must state that they are interest-based, with the AdChoices icon given as an example rather than the only permitted label. Third, the parties involved must follow applicable industry self-regulatory principles, such as the Digital Advertising Alliance’s Online Behavioral Advertising Principles. These duties sit alongside the targeting ban; they do not authorize the barred signals.
The practical sequence: draft the offer page, set the audience, add the label, update the privacy policy, then launch. The retrieved text addresses personalized advertising, not contextual placements; confirm contextual treatment separately on current English policy.
Privacy policy and page-level disclosures
The site-level disclosure is distinct from the on-ad label. The policy requires a privacy policy disclosing data collection, sharing, and use resulting from Google products and services, including cookies, web beacons, and IP addresses. It must also tell users that third parties may place and read cookies on their browser, or use web beacons or IP addresses, because of ads on the site. The retrieved text applies this across platforms, apps, connected TV, consoles, and email, so a credit card page is not exempt as a single page or small site.
Page restrictions and promise-language risk
Restricted pages may still carry AdSense code, but the retrieved publisher restrictions say they are likely to receive fewer ads than unrestricted content; no volume figure is given. On the same page, do not click your own ads or inflate impressions or clicks, reward users for viewing ads or searching, or use ad layouts mistaken for menus, navigation elements, or download links. Product-integration features must not become the visual focus or use misleading wording such as “click here to get the best deals.” For AdSense for Search, ads need genuine query intent, clear labels, separation from organic results, and no more ads than organic results. Search boxes and links must not be pre-filled, with one request per user action. Desktop caps are three units plus an optional link unit; mobile caps are two units, one visible at a time.
Enforcement examples and their limit
The retrieved enforcement guidance uses a strike system: five ordinary violations equal one strike, while one egregious violation equals one. Egregious examples include free or cash offers, promising loans, and specific promises outside the publisher’s control, such as “Open a PNC high-yield savings account with no credit check!” That example concerns a savings account, not a credit card ruling; applying the pattern to “guaranteed approval” card copy is an interpretation, not a documented card-specific decision.
Pre-publication checklist
Before publishing, verify the current official English policy pages and effective dates for: the US and Canada personalized-ad ban and its five signals; the sensitive-information rule covering negative financial status; audience-data rights, interest-based labeling, and self-regulatory adherence; privacy-policy wording for cookies, web beacons, IP addresses, and third-party ad cookies; reduced ad serving for restricted content; and the placement, search, unit-cap, and promise-language rules above. The retrieved wording came from a Chinese-language compliance knowledge base and may be a translation or older snapshot. Confirm contextual-ad treatment separately because the retrieved text addresses personalized advertising only. Treat platform policy compliance as separate from legal, tax, and financial advice; consumer-credit law needs review by a qualified professional. No card issuers, APRs, fees, rewards values, or approval statistics are used here because none were retrieved.
研究の知恵