RuleRun
Resources

Article

How to validate bonus terms prominence in email creatives

Significant conditions only protect you when a reader can actually see them. Here is how to measure prominence on the rendered email — not the markup — and enforce it on every campaign.

9 min read

What regulators mean by “prominence”

Across advertising-standards bodies and financial-promotion regimes, the guidance rhymes: if an offer carries conditions that materially change what the reader is agreeing to, those conditions must be presented so that a typical recipient actually notices and understands them. The language varies — “clear and prominent,” “not hidden or obscured,” “presented with sufficient prominence” — but the underlying test is consistent and, importantly, it is about perception, not presence.

That distinction matters. A disclaimer that exists somewhere in the email is not the same as a disclaimer that a reader can reasonably be expected to see. Prominence is judged from the standpoint of the person receiving the message: can they perceive the significant conditions in the same glance that carries the headline promise? If the answer is no — because the terms are too small, too faint, too far away, or rendered as an unreadable slab of image — then the condition has not been communicated, regardless of what the HTML contains.

Presence is not prominence

A compliance sign-off that only confirms the disclaimer text exists in the creative answers the wrong question. The regulator is asking whether the reader would see it. Those are two different checks, and only one of them can be judged from source code.

Why bonus terms have to compete with the offer

Marketing creatives are engineered to make one thing unmissable: the offer. A bright hero, an oversized number, a contrasting button. That is the job of the design. The problem is that the very same design pressure pushes the significant conditions in the opposite direction — smaller, greyer, lower, and out of the way — because they are commercially inconvenient. Prominence rules exist precisely to counteract that gravity.

In regulated marketing, especially iGaming and financial promotions, the conditions that most need prominence are the ones that change the economics of the offer:

  • Wagering requirements— a “100% bonus” behaves very differently at 10x versus 40x playthrough.
  • Minimum deposit— the amount a reader must commit before the offer applies.
  • Time limits— expiry windows that quietly determine whether the offer is usable at all.
  • Maximum bet or maximum win— caps that constrain the upside the headline implies.
  • Eligibility and exclusions— new-customer-only, region, or game restrictions.

None of these are footnotes in the reader’s decision. They are the terms of the deal. Prominence is the mechanism that keeps the terms visible next to the promise, so the reader evaluates the real offer rather than a flattering summary of it.

The measurable dimensions of prominence

“Prominent” sounds subjective, but it decomposes into properties you can actually measure on a rendered image. Treating prominence as a set of dimensions — rather than a gut feeling — is what makes it enforceable and repeatable across campaigns.

Relative font size

The size of the terms should be assessed relativeto the offer, not against an absolute pixel floor. Terms set at a small fraction of the headline’s height read as an afterthought no matter how many pixels they technically occupy on a large screen.

Colour contrast

Light-grey terms on a busy background can be technically present and practically invisible. Contrast between the terms and their immediate background is a measurable ratio, and low contrast is one of the most common ways prominence quietly fails.

Position and proximity

Distance matters. Conditions buried in a pre-footer, three screens below the claim, are not near the offer they qualify. Proximity — how close the terms sit to the headline in the rendered layout — is directly measurable.

Live text versus baked into an image

When terms are flattened into a hero image, they cannot be selected, resized by the client, or read by assistive technology, and they degrade badly on high-density or scaled displays. Whether the terms are live, extractable text or pixels in a picture is a first-class prominence signal.

Truncation on mobile and dark mode

A disclaimer that is perfectly prominent on a desktop preview can be clipped by a narrow mobile column, or made near-invisible when a dark-mode client inverts colours and collapses your careful contrast. Prominence is only real if it survives the environments your recipients actually use.

size ratio

Terms height measured against the offer height, not a fixed pixel floor

contrast

Terms-to-background ratio, checked in light and dark rendering

proximity

Rendered distance between the offer and the conditions that qualify it

Why source-code inspection cannot judge prominence

A natural instinct is to grep the HTML for the disclaimer string and call it done. That check confirms one thing only: the text exists in the markup. It says nothing about whether a reader will see it, because the rendered visual hierarchy is the product of a long chain the source does not resolve.

  • A font-sizein the CSS is not the final rendered size — media queries, client overrides, inherited scaling, and clamping all intervene.
  • Declared colours are not effective contrast. The rendered contrast depends on the actual background behind the text, which may be an image, a gradient, or an inverted dark-mode surface.
  • Source order is not visual order. Absolute positioning, flex, and floats mean the disclaimer’s position in the DOM tells you little about where it lands on screen.
  • Text inside an image is invisible to markup inspection entirely — the source sees an<img>, not the words baked into it.

The core issue is a category error: prominence is a property of the rendered pixels, and the source code is a recipe, not the finished dish. To judge prominence you have to look at what the recipient looks at.

The check that feels safe but is not

“The disclaimer is in the template, so we are covered” is the exact failure mode prominence rules were written to catch. A present-but-invisible condition is, from the reader’s perspective, no condition at all — and that is how the creative will be judged.

How automated rendered-view checks measure prominence

The reliable way to validate prominence is to check the email the way the recipient receives it: render it, then measure. RuleRun renders each creative and evaluates prominence as a set of comparisons rather than a single pass/fail on text presence.

  • Render the creativein representative environments — including mobile widths and dark mode — so the check reflects real conditions, not a single desktop preview.
  • Locate the offer— the headline claim or promotional number that the conditions qualify.
  • Locate the terms— the significant conditions, whether they are live text or text embedded in an image, so image-baked disclaimers are not silently skipped.
  • Compare the dimensions— relative size, contrast against the actual rendered background, and proximity between the terms and the offer.
  • Produce evidence— annotated screenshots and a PDF that show precisely what was measured, so a reviewer sees the finding rather than re-checking by eye.

Because the measurement happens on the rendered view, it treats an image-based disclaimer and a live-text disclaimer by the same standard: can it be seen, and is it seen next to the offer. That is the question the rule actually asks.

What prominent and buried actually look like

The contrast is easiest to see side by side. On the left, the terms sit directly under the offer, at a readable size, with strong contrast — a reader takes in the promise and the conditions together. On the right, the same terms are shrunk, greyed, and pushed to the bottom of the creative, far from the claim they qualify. The words exist in both. Only one of them is prominent.

100% BONUSCLAIM NOWMin deposit £10. 10x wagering.Expires in 7 days. Max bet £5.New customers only. 18+.PROMINENT100% BONUSCLAIM NOWMin deposit £10. 10x wagering. Expires 7 days. Max bet £5. 18+.
Left: terms sized and placed to be seen with the offer. Right: the same terms present but buried — small, low-contrast, and far from the claim.

A quick self-test

Shrink your creative to a phone-sized column and glance at it for one second. If the offer registers but the conditions do not, prominence has failed — and that one-second glance is close to what a real recipient gives it.

How RuleRun enforces prominence on every campaign

Prominence is not something you want to remember to check manually before each send. RuleRun turns it into a rule that runs automatically, on the rendered email, every time. You define the policy once — the required significant conditions, the acceptable size ratio relative to the offer, the minimum contrast, and the proximity expectation — and every campaign is measured against it.

  • Rendered, not read from source— checks run against the visual the recipient sees, across mobile and dark-mode variants, so truncation and inversion are caught.
  • Image-aware— terms baked into a hero are located and measured, so a designer cannot accidentally opt out of the check by flattening the disclaimer.
  • Comparative— the terms are always measured against the offer, matching how the prominence test is actually framed.
  • Evidenced— each run produces annotated screenshots and a PDF, giving reviewers and auditors a record of what was measured and why it passed or failed.

The result is a consistent, defensible answer to a question that used to depend on whoever happened to eyeball the creative: were the significant conditions actually prominent, on the email that actually went out.

Key takeaways

  • Prominence is about perception, not presence — a disclaimer that exists but cannot be seen has not been communicated.
  • Significant conditions like wagering, min deposit, time limits, and max bet must stay visible next to the offer they qualify.
  • Prominence decomposes into measurable dimensions: relative size, contrast, proximity, live-vs-image text, and mobile/dark-mode survival.
  • Source-code inspection can only confirm text exists — it cannot judge the rendered visual hierarchy a reader actually sees.
  • Automated rendered-view checks render the email, locate the offer and the terms, and compare them, with screenshot and PDF evidence.
  • RuleRun enforces prominence automatically on every campaign, image-aware and evidenced, so the check is consistent and auditable.

See RuleRun on your own emails

Check rendered marketing emails against your compliance policy — assets, text prominence, links, and content embedded in images.