The Short Answer: Five Attributes, Three Product Groupings
In the United States and Canada, Google publisher policy states that personalized ads may not be selected or targeted based on an audience's gender, age, parental status, marital status, or ZIP code for credit-related products or services, banking products and services, or certain financial planning and management services. The policy's example list names "credit cards and loans, bank and checking accounts, debt management products"; the retrieved text presents those as examples, not an exhaustive statutory list. The retrieved materials are Chinese-language renderings, so English wording here is a translation, not official policy phrasing.
This is an attribute restriction inside personalized advertising, not a blanket prohibition on credit-card content or every finance campaign. It is also not an allow-list: the source names prohibited attributes but does not enumerate permitted ones. For pre-launch review, document what you removed and why rather than invent an approved-targeting matrix.
The Second Clause Finance Audiences Often Miss
The same policy section separately bars selecting or targeting personalized ads based on inferred or actual sensitive information, and bars collecting or using cookie lists or other audience data on that basis. Its list explicitly includes negative financial-status information or other detailed personal financial information, such as signals of low credit rating or high debt burden.
For credit-card content, this catches audience logic labeled "rebuilding credit," "paying down debt," or "bad-credit recovery." Even with no age, gender, parental, marital, or ZIP field, the inference may be exactly the sensitive signal described. Treat the fixes separately: removing ZIP does not cure a debt-burden inference, and removing a credit-rating inference does not make an age field acceptable.
What Still Supports Personalized Credit-Card Campaigns
Personalized advertising is not eliminated. The compliance layer still matters: the party using audience data such as cookie lists must hold all necessary rights; the advertiser must add an interest-based ad notice, such as the AdChoices icon; and all parties must follow applicable self-regulatory codes, such as the Digital Advertising Alliance Self-Regulatory Principles for Online Behavioral Advertising or the IAB Europe EU Framework for Online Behavioral Advertising. These are process obligations, not substitutes for the attribute and sensitive-data bans.
Publisher disclosure has a separate layer. Publishers using Google ad products must maintain a privacy policy that clearly discloses data collection, sharing, and use from Google products, including cookie, web-beacon, IP-address, and other identifier use, and disclose that third parties may place and read ad cookies or use web beacons or IP addresses. Precise location data is another separate rule: if collected, processed, or disclosed, it requires notice, explicit opt-in consent before collection/processing/disclosure, encrypted transmission, and privacy-policy disclosure. Do not merge precise-location consent with the ZIP-code audience-attribute restriction. The ZIP attribute rule asks what audience field you selected; the location rule asks how you collected and handled precise location data. A ZIP field in an audience segment is not the same as GPS, Wi-Fi, or cell-tower data.
Where Creative and Traffic-Source Promises Become the Bigger Risk
Audience cleanup can pass while creative still creates enforcement exposure. In the retrieved AdSense Search Ads product-integrated-feature examples, "specific promises outside of your control" are an egregious violation; the example is an account-opening promise including "no credit check." The table maps one egregious violation to one strike versus five normal violations to one strike. Scope that to the retrieved AFS enforcement table; do not generalize timelines, appeals, or reinstatement outcomes.
The drafting habit is narrower: promise only what the landing page delivers. For related-search traffic acquisition, the retrieved AFS policy requires traffic sources to be relevant to and accurately describe the destination page; it prohibits promising products, services, or offers absent or hard to find there, and prohibits misleading claims about them. Comparison pages also face the misleading-statement rule: content may not misrepresent the publisher, content creator, purpose, or content, or falsely imply association with or endorsement by another organization, product, or service.
A Pre-Launch Pass for a Credit-Card Audience Build
Treat this as a documented review pass, in launch order, not a one-time fix:
- Classify the campaign as personalized or contextual, and record which policy clause you are applying. The retrieved materials constrain personalized or interest-based advertising; they do not settle contextual treatment for credit-card content.
- Strip gender, age, parental status, marital status, and ZIP code from audience segments used for credit-related, banking, and covered financial planning or management offers.
- Audit first-party and modeled segments for inferred or actual low-credit-rating or high-debt-burden signals, and check whether cookie lists or other audience data use those signals.
- Confirm rights to use audience data such as cookie lists, keep the interest-based ad notice such as the AdChoices icon in place, and document adherence to applicable DAA or IAB Europe self-regulatory codes.
- Verify the site's privacy policy discloses cookie, web-beacon, IP-address, and other identifier use, plus third-party ad cookies, and keep the separate precise-location notice, opt-in consent, and encryption rule where that data is involved.
- Re-read creative and traffic sources for promises the landing page cannot fulfill, offers absent or hard to find there, and any implied issuer or brand endorsement.
What This Answer Cannot Settle
This article addresses Google publisher and advertising policy compliance, not US consumer-credit law, card economics, or creditworthiness advice. No retrieved source provides APRs, fees, offers, approval criteria, or issuer terms, so none appear here. The retrieved policy text is a translation, and policies may be revised; confirm the current official English wording on the live policy page before relying on it in a client deliverable. The attribute restriction is stated for the United States and Canada, so do not extend it to other markets on this evidence. Anything involving consumer-credit regulation, a live enforcement notice, or an account appeal should go to compliance or legal counsel.
研究の知恵