Advertising a Children's Online Store: Policies, Feed and Privacy

Advertising a children's online store has to account for a simple asymmetry: the decision and the payment usually come from an adult, while the product is used by a child. So campaigns are best built around the adult buyer, placements where the audience may include minors need separate control, and personalisation should not be relied on where the platform restricts it. What makes this manageable is a clean catalogue, precise landing pages, careful creative and a transparent measurement scheme.

Start by defining who the ad speaks to

A "children's product" label does not by itself mean the ad is addressed to a child. Nappies, car seats or nursery furniture are normally chosen by an adult. A video that directly urges a schoolchild to ask for a purchase, on the other hand, already operates in a different context, even if the product itself is entirely ordinary.

Before launch, split your range and your messaging into three tracks:

• Products with an adult decision-maker. The copy explains to parents or other adults the specifications, compatibility, materials, care, delivery and returns.
• Products with teen appeal. Clothing, cosmetics, electronics or hobby products call for a separate review of creative, category and the targeting options available.
• Content or placements aimed at children. For YouTube inventory marked made for kids, Google prohibits personalised advertising, third-party trackers, calls for children to buy a product and misleading claims. Google describes additional protections for children and teens across YouTube, Google Display Ads and Display & Video 360, and warns that the list of products may expand (Google Ads: ad protections for children and teens).

In your internal catalogue, add working flags: who makes the purchase decision, whether the creative may address a minor directly, whether the category carries additional restrictions, which audience mechanics are permitted. These fields do not have to be passed to the ad systems. Their job is to steer campaign management and editorial review.

What Google's age restrictions mean

Google distinguishes between children below the digital age of consent and teens above that threshold but under 18. The policy page itself does not set a numeric threshold for Ukraine. For users under 18, Google does not allow personalised advertising, including targeting based on Google's ready-made audiences (restricted personalised targeting).

This is not a blanket ban on advertising children's products to adults. It defines which data and signals may be used when the recipient of the ad is a minor. In the same way, audience restrictions for sensitive categories should not be carried over automatically to a shop's entire range.

Practical rules:

• do not upload to advertiser audiences any user information obtained from viewers of child-directed content;
• do not pass personal data through the product feed or remarketing lists;
• do not combine personal data with pseudonymous identifiers in breach of platform rules;
• do not build excessively narrow segments that effectively allow individuals to be identified;
• do not send precise location without the user's consent;
• for products in sensitive categories, check separately whether Customer Match, custom data segments, audience expansion and similar audiences are permitted.

If your catalogue mixes ordinary and sensitive categories, separate them by campaign. That simplifies the review of audience settings and avoids forcing the same logic onto products with different statuses.

The product feed: accuracy beats advertising tricks

For shopping campaigns, decision quality depends on the data Merchant Center receives. The baseline set includes id, title, description, link, image_link, price and availability. The status of other attributes depends on category, country and display format (product data specification).

For every SKU, check:

• a stable, unique id that does not change after a routine product update;
• a title without promotional inserts that accurately describes the model and variant;
• a description that matches the actual specifications;
• a correct main image, with no substitution of a different variant;
• price and availability drawn from a single source of truth for the feed, the page and the checkout;
• colour, size, age group and the relationship between variants wherever those attributes apply;
• a GTIN only where the manufacturer has genuinely provided an identifier. Inventing one is not allowed.

An age range in the product title and the age_group attribute serve different purposes. The first helps the shopper understand who the product is for; the second must comply with the feed specification wherever it is required. Do not assign an arbitrary age based on a photo or a marketing name alone.

The landing page must back up the feed

A link from Merchant Center must lead to the page for that specific product, not to a category, a search page or the homepage. It must clearly show the product, its title, description, image, price, currency, availability and a way to buy. The page language must match the language of the product data (Merchant Center landing page requirements).

Test the same URL on mobile and desktop, in a fresh session and while logged out. Material information must not depend on device, browser, location, cookies or user agent. The crawler and the shopper must see the same product. Remove unnecessary redirects, error pages and any scenario where price or availability appears only after an action a crawler cannot perform.

If stock or currency varies by region, verify that the target country in the feed leads to a stable version of the page with the matching terms. Do not paper over the discrepancy with "once you pick a city, everything will be right".

Meta: use the dated rule with care

In January 2023 Meta announced that, from February, advertisers reaching teens would be left with age and location, gender would be removed as an option, and teens' previous interactions with content in the apps would no longer determine the ads shown to them. The page was published on 10 January and updated on 18 January 2023 (Meta's announcement on ads for teens).

This is an official but dated announcement about a rollout of changes. It is not a full specification of the 2026 interface. Before every launch, open the current Ads Manager, check which audience fields are available for the chosen countries, and check the creative against the current Meta Advertising Standards. Record the result in the campaign checklist so the next team does not copy old settings blindly.

Privacy by design for tags and events

Start with a data map. For every event, record where it fires, which parameters it carries, where it is sent, under which consent state it triggers, and who is responsible for changing it. Flag separately any pages or sections that may be child-directed.

A minimum audit covers:

• URL parameters in feed links and in ads;
• the values that end up in view_item, add_to_cart, checkout start and purchase;
• form fields read by advertising tags;
• customer lists and the rules for uploading them;
• precise location and the source of consent for using it;
• browser-side and server-side copies of the same event;
• logs where personal data may be retained longer than necessary.

Consent Mode communicates consent status for cookies and app identifiers to Google, but it does not create a banner itself. In basic mode, Google tags are blocked until the user interacts with the banner; in advanced mode, cookieless pings may be sent while the state is denied. The ad_storage parameter governs the use of advertising cookies and identifiers. Google documents regional behaviour separately for the EEA, Switzerland and the UK, so Consent Mode should not be described as a universal legal requirement for Ukrainian traffic.

Enhanced Conversions supplements existing conversion measurement with hashed first-party data, including email, name, address or phone number, where the shop collects them. SHA-256 is used for transmission. Hashing does not make the data anonymous and does not automatically create a legal basis for processing.

The Conversions API connects an advertiser's marketing data to Meta's systems in order to measure and optimise events from a website, an app, business messaging or offline interactions. The overview page does not confirm specific deduplication or hashing rules. Nor does a server-side channel override the user's choice in the browser. Implementation details should be taken from the dedicated documentation and from the agreed data map.

Symptom, check, action

Symptom	What to check	Action
Product disapproved over its data	Required and conditional attributes, value formats	Fix the feed source, then re-run validation
Variants merge or duplicate	id, grouping, colour, size, age group, real identifiers	Rebuild the variant mapping without invented GTINs
Price or availability does not match	Feed, product page, basket and checkout	Bring all channels to a single source of truth
Landing page found non-compliant	Final URL, redirects, language and what is served to the bot	Point to a stable page for the specific product
Audience tool unavailable	Product category, audience age, segment type	Split the campaigns and remove the disallowed signal
Events disappear after a consent choice	The ad_storage state, Consent Mode setup, tag firing order	Review the implementation with a consent specialist
Browser and server events duplicate	The current deduplication scheme in the dedicated documentation	Align event identifiers and retest the flow

Pre-launch checklist

• The range is tagged by who the messaging addresses and by the risk of breaching ad policies.
• Creative for children and teens contains no direct purchase pressure, manipulative wording or unsubstantiated claims.
• The permitted audience mechanics are recorded for every campaign.
• The feed has stable id values, accurate titles, descriptions, images, prices and availability.
• Variants are linked correctly; GTINs are not generated artificially.
• Every link leads to the page for that specific product in the right language.
• Pages serve the same material data to users and crawlers.
• The consent banner and tag behaviour have been tested for every available state.
• Enhanced Conversions and CAPI pass only the agreed fields.
• Meta settings have been verified in the current Ads Manager, not from an old template.
• Local requirements on privacy, advertising to children and consumer protection have been cleared with a lawyer or DPO.

Weekly checks

• Review new and changed SKUs: category, variants, identifiers, price and availability.
• Open a sample of feed URLs on different devices and in a clean session.
• Check Merchant Center diagnostics and the reasons for disapprovals, not just the number of active products.
• Review new creative together with its landing page: context can change how an ad is assessed.
• Test key events across the consent states available to the user.
• Reconcile the browser-side and server-side flows, without drawing conclusions from the conversion count in a single interface alone.
• Log changes in Google Ads, Merchant Center and Meta Ads Manager that affect age, audiences, data or creative.

Checks like these are not a guarantee of future ad approval or of legal compliance. What they give the team is a repeatable process: separate the adult buyer from the possible minor recipient, avoid mixing different targeting modes, and quickly find the point where the catalogue, the page or the measurement lost alignment.

Related UPLIFY resources

• Performance Max and Shopping
• Google Ads audit
• All Playbooks
• Editorial policy