Two restrictions, not one
Credit-card offers face two policy mechanisms, not one. The retrieved text puts credit-related and banking products in the same US/Canada targeting group as housing and employment services, while a separate sensitive-data rule governs audience inputs. Start your review with the category, not the creative.
| Restriction | What the policy prohibits | Geographic scope stated in the text | Source |
|---|
| Negative financial-status data as a personalized-ad input | Selecting or targeting personalized ads, or collecting or using audience data such as cookie lists, based on inferred or actual sensitive information, including a low credit rating or high debt burden | No regional limit stated in the retrieved text | AdSense Help 10502938 |
| Attribute-based targeting of credit and banking ads | Using gender, age, parental status, marital status, or postal code to advertise credit-related, banking, or certain financial planning and management services (examples: credit cards and loans, bank and checking accounts, debt management products) | United States and Canada | AdSense Help 10502938 |
The category rule is scoped to US and Canada; the sensitive-data rule has no stated regional limit in the retrieved text. Passing one check does not satisfy the other, and neither replaces the advertiser notices or publisher disclosures below.
Five attributes, US and Canada only
For a US or Canadian audience, the five named attributes are gender, age, parental status, marital status, and postal code. The restriction covers credit-related products or services, banking products and services, and certain financial planning and management services; examples include credit cards and loans, bank and checking accounts, and debt management products. A segment defined by gender, age, and ZIP code combines three banned selectors for a credit-card offer, and even one banned attribute—such as marital status—crosses the line. The rule does not ban personalized advertising, only those audience selectors. A segment that is lawful for another market can still be unusable for this audience.
Hardship data is a separate input
The policy separately bars using inferred or actual sensitive information—including a low credit rating or high debt burden—to select or target personalized ads or to collect and use audience data such as cookie lists. A campaign can avoid all five attributes and still fail if it imports a lead-gen list scored by creditworthiness or models high-debt users. The sensitive element is the person's financial hardship, not the card product. The attribute restriction is scoped to US and Canada; this data restriction has no regional limit stated in the retrieved text.
What personalized ads still require
Three obligations apply cumulatively when personalized ads run through Google products or Google ad code: hold all rights needed to use audience data such as cookie lists; add an in-ad notice that the ad is interest-based, for example through the AdChoices or Ads Options icon; and comply with applicable self-regulatory codes, such as the Digital Advertising Alliance's principles or IAB Europe's framework. Rights to a list do not replace the notice, and the notice does not cure a code violation. Review the segment and the creative together.
Publisher duties and page risks
Publisher duties sit on separate compliance surfaces. Your privacy policy must clearly disclose data collection, sharing, and use resulting from Google products and services, including cookies, web beacons, IP addresses, or other identifiers, across websites, apps, connected TV, consoles, and email. Information you supply to Google must be accurate and complete, with no misleading omissions; retrieved examples include inaccurate payment or personal details and inaccurate site or app information, such as ads.txt entries or partial or incorrect URLs or app IDs. Page-level rules add two more checks: Google-served ads may not be placed on screens where ads or other paid promotional content occupy more space than publisher content, and AdSense for Search traffic sources must be relevant to and accurately describe the landing page, must not promise offers absent from or hard to find on it, must not mislead about those offers, and must lead to a page substantially the same as what an organic visitor sees. Mostly offer blocks or a headline offer buried after the click are obvious risks.
How enforcement escalates
Google's enforcement uses a strike framework. In the compliance summary retrieved, five normal policy violations equal one strike, while one egregious violation equals one strike. Egregious examples include concrete, explicitly stated promises that cannot be fulfilled, such as free or cash offers, promised loans, or specific promises outside the publisher's control. The summary gives a credit-adjacent example: an ad promising a high-yield savings account with no credit check. Fixed, unqualified claims therefore sit in a different enforcement tier from ordinary policy errors.
Pre-launch audit and evidence limits
Before launch, inventory every audience segment and remove gender, age, parental status, marital status, and postal code from credit and banking campaigns aimed at US or Canadian users. Trace imported lists for financial-hardship scoring and remove them if found. Confirm the in-ad interest-based notice, the three advertiser duties, and a privacy policy covering cookies, web beacons, IP addresses, and other identifiers across every property. Check ads.txt, declared URLs, app IDs, and payment details for accuracy. Test offer-heavy layouts against the ad-to-content rule, and make every traffic source match the landing page an organic visitor sees. Then verify the live English policy at the consolidated Publisher Policies Help Center, because the retrieved text is a Chinese-language compilation with no publication or effective date. Copies remain visible in the AdMob, AdSense, and Ad Manager help centers while the migration proceeds. The strike details come from an internal summary without a public URL. No credit-card products, rates, fees, approval outcomes, or revenue figures are verified here; this is compliance information, not legal advice. Legal disclosure duties are outside this guide. Other markets and state-level rules were not verified and are out of scope. No author or reviewer credential is asserted. No issuer or card product is named.
研究の知恵