Industry · Status at source date: Newsletter archive
Google bans personalised targeting for Rummy and Fantasy Sports App campaigns in India
Starting February 5, 2026, Google no longer allows personalised targeting for App campaigns promoting Rummy or daily fantasy sports apps in India. Only non-personalised delivery is permitted for these verticals in that market.
This update uses a PMC cover because no suitable source image was available when checked on 8 Sept 2026. Available source and video links are retained.
Why it matters for advertisers
For you, this means switching affected campaigns to contextual targeting if you promote skill-based gaming apps in India.
Perspective from the original PMC newsletter.Sources & contributor credit
- Newsletter coverage · Paid Media Collective newsletter
Original newsletter text, contributor labels and media for this update.
- Source referenced in newsletterGoogle Ads Policy Help
Linked from the original newsletter. The source publication date has not been independently confirmed.
Original creator unverified
The original creator has not yet been verified. Newsletter curation and publication do not establish original authorship.
Attribution evidence and limitations
Full attribution review pending.
A source link alone does not establish original authorship.
Original image and video creators have not yet been verified.
- Published on this site
This update reflects the dated source reporting. Availability may have changed. Further coverage of this same development will be added to this page.
Original newsletter text and archive evidence
Google bans personalised targeting for Rummy and Fantasy Sports App campaigns in India
Starting February 5, 2026, Google no longer allows personalised targeting for App campaigns promoting Rummy or daily fantasy sports apps in India. Only non-personalised delivery is permitted for these verticals in that market. For you, this means switching affected campaigns to contextual targeting if you promote skill-based gaming apps in India.
Source captured . No explicit first-contributor label was provided for this update.
