Where Credit Cards Sit in the Policy Taxonomy
Google groups credit-related products and services, banking products and services, and certain financial planning and management services into one restricted advertising category, naming credit cards and loans, bank and checking accounts, and debt-management products as examples.
That classification changes how the page is read: not generic retail content once ads are served against it, but a category that inherits financial-services rules. Deciding whether your page markets a credit product is the first gate, because it settles which targeting and wording tests follow.
The US and Canada Attribute Rule
In the United States and Canada, personalized ads may not use audience gender, age, parental status, marital status, or ZIP code to promote credit-related products or services, banking products and services, or certain financial planning and management services.
Separate the delivery model before worrying about the list. Contextual delivery matches the page a reader is on; personalized delivery matches the reader to an audience attribute. The five attributes attach to the second: a segment built on "women aged 30–45," "new parents," or "married, ZIP 90210" cannot be aimed at credit-card inventory, however careful the copy.
One limit matters: the retrieved material documents what is prohibited, not what is permitted. Do not read this as "everything else is fine"; confirm allowed practices on the live policy page.
Inferred Credit Trouble Is Sensitive Data
Personalized ads may not be selected or targeted using inferred or actual sensitive information, and negative financial status or other detailed personal-finance information is listed among it — data indicating a low credit rating or a high debt burden, for example.
This is where credit-card content quietly goes wrong. A page titled "cards for people rebuilding credit" is fine as a topic; an audience segment built on the inference that a reader has a low credit rating is not. The inference does not have to be correct to be restricted.
The safer move is placement, not profiling: serve against the topic and let contextual matching work.
Consent, In-Ad Notice, and Privacy Disclosure
Three obligations appear separately in the retrieved text.
Audience data: advertisers delivering personalized ads through Google products or ad code must hold all rights needed to use audience data such as cookie lists.
In-ad notice: the ad itself must state that it is interest-based, with the AdChoices icon given as an example. A site footer does not satisfy this, because the requirement sits on the ad.
Self-regulatory alignment: all parties must follow applicable industry codes, such as the Digital Advertising Alliance's Self-Regulatory Principles for Online Behavioral Advertising or the IAB Europe EU Framework.
Site disclosure: your privacy policy must clearly disclose data collection, sharing and use arising from Google products — cookies, web beacons, IP addresses or other identifiers — and must state that third parties may place and read cookies, or use web beacons and IP addresses, because of ads on your site. Notice and policy remain separate duties.
Claim Wording and the Two Violation Tiers
The retrieved compliance reference draws a line between two tiers: vague promises are normal violations, impossible concrete promises are egregious — because five normal violations equal one strike, while a single egregious violation equals one strike.
| Claim pattern | Example in retrieved material | Tier | Documented strike weight |
|---|
| Promise implied but not explicit; information promised, never delivered | "Graduate education should be affordable!"; "see a list of top doctors near you," no list provided | Normal violation | 5 normal = 1 strike |
| Concrete promise that cannot be fulfilled, or one outside publisher control | "Free or cash offers"; "promising loans"; account opening with no credit check | Egregious violation | 1 egregious = 1 strike |
At the vague end sits a promise implied but never stated, or specific information promised and never delivered. At the other end sits a commitment concrete enough to be checked.
That is the test for a credit-card page: could a sentence be read as an explicit, checkable commitment outside the publisher's control? "Guaranteed approval," "no credit check," and "we'll get you the loan" sit at that end; "you could be approved" sits closer to the vague tier. Hedging helps, but vague promises still count.
Layout Balance and Accuracy Checks
Two further checks concern the page as built.
Google-served ads may not appear on screens where advertising or other paid promotional content occupies more of the layout than the publisher's own content. An offer-heavy page whose affiliate blocks outnumber original paragraphs is a layout problem even when every claim is accurate. Measure the proportion, not the intent.
Separately, information you submit to Google must be highly accurate and complete, with no misleading omissions; severely incomplete personal or payment details and inaccurate website information such as ads.txt entries are given as examples.
Pre-Publish Gate
Run this pass before publishing any credit-card page that carries Google-served ads:
- No gender, age, parental status, marital status, or ZIP code targeting on a credit page.
- No segment built on inferred low credit rating or high debt burden.
- An interest-based notice on the ad itself, not only a site footer.
- A privacy policy disclosing third-party cookies, web beacons, and IP addresses.
- No "guaranteed approval," "no credit check," or loan promises.
- Paid promotional content that does not exceed your own content.
- Accurate account details and ads.txt entries.
- A same-day re-check of the live publisher policy page.
Where This Summary Stops
This is a summary of retrieved policy language, not legal advice; for a specific page, consult your own counsel or Google account team. The retrieved material says policies may be revised at any time, and publishers are responsible for staying current, so date-check the live page before acting. The strike weights come from an internal compliance reference, not a public help page. No card-level rates, fees, approval odds, or credit-scoring data were retrieved.
研究の知恵