Buy Traffic

The creative rules that decide whether push ads even reach a moderator

Last updated: 8 September 2026

On this page
  1. What a moderation queue actually inspects on push ads
  2. Title and body copy limits across push ads panels
  3. Icon specifications that clear automated push ads screening
  4. Vertical-specific rules that apply to push ads
  5. Getting a resubmission approved after a first push ads rejection

Push ads carry three editable fields and almost no room to hide a weak one: an icon, a short title, and a single line of body text rendered by the operating system rather than by the advertiser. A rejection rarely comes with a specific reason attached, which pushes buyers toward guessing at rules that are, in most cases, published plainly and never read before the first submission goes in. Most inconsistent-looking moderation is actually a consistent rule applied to a field the buyer never checked against the panel's own specification sheet.

What a moderation queue actually inspects on push ads

Automated pre-screening checks the icon and the destination URL before a human ever opens the queue, flagging mismatched file dimensions, banned words inside the title field, and destinations that resolve to a domain with an existing strike against it. Anything that clears the automated pass moves to a manual check, where the same three fields get inspected again against category-specific rules that vary by vertical rather than by network.

The single biggest source of avoidable rejection is an icon that does not match the aspect ratio the panel specifies, since a slightly cropped or stretched icon reads as low-effort spam to the automated filter regardless of what the underlying creative actually promotes.

A second common cause, less discussed than the icon issue, is a destination URL carrying tracking parameters the moderation system has not seen before. A brand new subdomain or an unfamiliar redirect pattern occasionally trips the same fraud heuristics built to catch cloaking, even when the destination itself is entirely legitimate, and switching to a previously whitelisted domain pattern often clears a stubborn rejection faster than any change to the creative.

Timing also plays a quiet role that most buyers never account for. Submissions filed during a panel's peak queue hours, typically overlapping business hours in the network's home time zone, take noticeably longer to clear than the same creative filed overnight, purely because of queue depth rather than any difference in scrutiny applied. A buyer working against a launch deadline gains more from submitting a day early than from polishing a creative that was already compliant.

Title and body copy limits across push ads panels

Character limits on titles differ enough between panels that a creative approved on one network gets truncated mid-word on another, and truncation itself can trigger a second manual check because the resulting text sometimes reads as a banned phrase by accident.

Where truncation causes accidental rejections

A title ending mid-sentence at a hard character cut can land on an unrelated word that happens to sit on a network's banned list, producing a rejection that has nothing to do with the creative's actual intent. Testing a title at its full length and again at each panel's stated limit before submission catches this before it costs a cycle.

The field limits published on push ads documentation break down title and body caps per platform side by side, which is a faster reference than testing blind against each panel one submission at a time.

Body text carries a second, less obvious constraint on several panels: certain punctuation marks, particularly exclamation points repeated more than once, get flagged as clickbait regardless of the surrounding wording. A creative that reads naturally with a single exclamation point often clears without incident, while the same line with two in a row triggers an automatic hold lasting several hours even outside peak queue times.

Icon specifications that clear automated push ads screening

Icons render at a fixed small size on the device regardless of what resolution gets uploaded, so detail that reads clearly at 192 pixels square often disappears entirely once scaled down to the 48 pixel thumbnail a subscriber actually sees, and a rejected icon is frequently one that looked fine in the upload preview but became illegible on the device.

FieldTypical specCommon rejection cause
Icon192x192px PNG or JPGWrong aspect ratio, text too small at 48px
Title30-60 characters depending on panelTruncation lands on a banned word
Body text45-120 characters depending on panelExceeds limit, gets auto-cut mid-phrase
Destination URLMust resolve without redirect chainRedirect flagged as cloaking

None of these specs are secret; they sit in each network's help center, and the failure mode is almost always a buyer reusing a creative built for one panel's limits on a different one without re-checking the numbers first. A side-by-side spec sheet for icon and title fields across the major panels removes most of that guesswork before a first upload.

Color contrast inside the icon matters more than most buyers assume, since the notification tray on several Android skins applies a background tint that can wash out a light icon into near invisibility. An icon that tested clearly on a stock Android emulator can still disappear on a Samsung or Xiaomi device running a heavily customised interface, which is one reason experienced creative teams test icons on at least two device manufacturers before locking a final version.

Vertical-specific rules that apply to push ads

A creative acceptable in the sweepstakes vertical can fail instantly in dating or adult categories, since moderation applies stricter language filters and image screening the further a category sits from mainstream advertising, and a buyer moving a working creative across verticals without adjusting it is the second most common source of avoidable rejection after the icon issue.

Banned regardless of vertical

System-alert mimicry, fake battery or virus warnings, and countdown timers implying urgency the offer cannot back up get rejected on every panel checked for this piece, with no exceptions found across the major networks. These patterns also carry the highest chance of a domain-level strike if they slip through once and later get reported by a user.

A subtler variant of the same problem is a creative implying a private message from a specific named person, which several panels now treat identically to system-alert mimicry even though it contains no fake interface elements at all. The rule targets the deceptive framing rather than any specific visual pattern, which is why it catches creatives that would have cleared moderation a year or two earlier.

Gambling and financial trading creatives face an additional layer entirely separate from the format rules above: several panels require proof of licensing for the advertised operator before a campaign in that category clears at all, a document check that sits outside the normal automated pipeline and can add a full business day to the timeline regardless of how clean the creative itself is.

Getting a resubmission approved after a first push ads rejection

Most panels allow resubmission without a cooldown period, but resubmitting the identical creative rarely changes the outcome since the same automated filter flags it again on the same grounds. Changing the specific field that triggered the flag, rather than the whole creative, clears the queue fastest and avoids burning a fresh slot on an unrelated edit.

A resubmission checklist that saves a cycle

Rejection reason shownField to changeField to leave alone
Icon flaggedRe-export icon at correct aspect ratioTitle and body text
Title flaggedShorten or rephrase the flagged segmentIcon and destination URL
Destination flaggedRemove redirect, link directlyIcon and title

The moderation reference on push-ads.io lists banned patterns by vertical rather than as one generic set of rules, which is the detail most rejection notices leave out and the one that actually shortens the path back to an approved push notification ads creative on the second attempt rather than the fourth.

Keeping a short log of every rejection reason and the fix that cleared it, specific to each panel rather than treated as one universal rulebook, turns a slow trial-and-error process into something closer to a checklist by the third or fourth campaign, which is usually the point where the time spent on moderation stops feeling disproportionate to the spend it protects.

A handful of larger agencies go a step further and maintain a shared internal database of banned words and rejected patterns across every panel they run creatives on, updated by whoever hits a new rejection first. Smaller buyers rarely have the volume to justify that overhead, but even a simple personal note file kept over a few months of campaigns tends to prevent the same mistake from repeating on a new push ads account months after it was first solved on an old one.

Material last verified: September 8, 2026.