Introduce your offer through clearly labeled sponsored cards that fit the layout of the publisher’s content.
Explore types & examplesPlaces, stories and a little inspiration for your next escape.
Sponsored recommendations follow the editorial layout, with their advertising labels kept visible.
A recommendation area follows the publisher’s story and uses a similar card layout.
Native advertising adapts the presentation of sponsored content to the surrounding page. A typical placement combines an image, headline, brand label and destination. The format should remain identifiable as advertising even when its layout matches editorial recommendations.
A visitor reaches a recommendation area within or after the content. Sponsored cards present a concise proposition. Clicking a card opens the advertiser’s destination, where the full product or offer can be explained.
Native describes how an advertisement fits its surroundings. Image, headline and layout can follow the publisher’s design while a clear sponsored label preserves the distinction from editorial content.
A sponsored card appears among the publisher’s stories or recommendations. Its image and headline use the same visual rhythm as neighboring items, while the advertising label makes clear that the destination is part of a paid promotion.
Match the required image ratio and headline length. The landing page should deliver the subject promised by the card rather than an unrelated offer.
A native unit appears at a deliberate point within a longer article. The publisher reserves a visible break for the sponsored recommendation, allowing the visitor to follow the offer or continue reading the surrounding editorial content.
Keep the label next to the recommendation. Review spacing and mobile wrapping so the unit remains identifiable without interrupting the article’s structure.
A group of sponsored recommendations appears after the main content. Each card presents a distinct image and headline, giving the visitor several possible next destinations without suggesting that paid recommendations were independently selected by the article’s author.
Review the full grid, including repeated offers and headline truncation. Measure card-level response where supported instead of treating every position as equivalent.
Illustrative examples, not live advertising. Available inventory, creative requirements and delivery behavior are confirmed for your setup.
The publisher requests eligible native assets.
The renderer places the headline, image and brand in the site layout.
A click opens the offer and preserves the configured attribution.
Connect the creative promise to the landing-page experience. Choose an image and headline that explain what the visitor will discover, then test variations against actual conversions. A strong click-through rate is useful only when the resulting visits serve your objective.
Plan a native ads campaignPlace sponsored recommendations where they make sense within the reading journey. Match the unit to the site layout while keeping the advertising label visible. Review the number of cards, image treatment and spacing across desktop and mobile.
Discuss your websiteReview impressions, clicks and conversions by placement and creative. Compare headline tests with landing-page quality, not click volume alone.
Asset specifications and rendering depend on the native placement. Sponsored content must be distinguishable from editorial content.
A native connection delivers assets and a way to render them. Choose who owns the card layout, who records its events and how advertising remains obvious within the surrounding content.
Place the supplied native unit in an approved article, feed or recommendation position. Its renderer assembles the supported headline, image, advertiser identity and link into cards, while the publisher checks how the complete unit fits the reading experience.
Publishers introducing a sponsored recommendation area.
For an agreed asset integration, the publisher receives structured creative fields and renders them in a controlled template. This gives the publisher responsibility for required assets, image treatment, sponsorship identification and the supported impression and click tracking behavior.
Teams maintaining their own recommendation design.
A compatible native auction requests the assets required by the placement. The selected response is passed to the configured renderer through the reviewed Prebid or OpenRTB arrangement. Exchanging a successful bid does not automatically place a finished card on screen.
Publishers or partners with native auction support.
Follow what happens on the device. The integration, placement and browser all shape the experience your audience receives.
Match spacing and typography to the page while keeping a clear advertising label beside the sponsored content. A native card should be understandable before a visitor follows its link, not only after arrival.
Long headlines and image crops change how the message reads on mobile. Review the actual assembled card, including brand identification and missing optional fields, rather than approving each asset in isolation.
A visitor choosing a product recommendation should reach the corresponding offer. Keep the image, headline and landing-page proposition consistent; curiosity-driven clicks alone do not demonstrate useful engagement or qualified acquisition.
Review the full recommendation journey, from asset request to the destination. Include the publisher template in approval because it changes how the same creative is understood.
Agree headline limits, image proportions, advertiser identification and destination fields. Identify which assets are mandatory and how the unit should behave when a required field is missing or unusable.
Preview the unit within a representative article and feed. Inspect disclosure, headline truncation, image cropping and touch spacing at narrow widths, including cards displayed beside ordinary editorial recommendations.
Follow the image, headline and call-to-action links that the template exposes. They should preserve the intended destination and attribution without counting a single interaction multiple times through nested click handlers.
Establish whether an impression refers to a card or the containing widget. Compare creative and position results with destination behavior, then adjust one identifiable element before drawing conclusions about the next test.
Active filters, validation criteria and reporting treatment are agreed for the integration.
Use the source, event history and destination together when reviewing traffic quality.
Review whether the headline and imagery fairly describe the offer. Clear sponsorship and an honest destination reduce misleading interactions; cosmetic similarity to editorial content is not a substitute for a recognisable advertisement.
Weak conversion performance may indicate a poor creative promise, placement mismatch or technical problem. Review those explanations alongside agreed duplicate and automated-activity checks; do not label every short visit or unconverted click as fraud.
Retain the agreed creative, placement and source identifiers for comparison. If activity changes unexpectedly, inspect template updates and traffic origin with the partner before expanding delivery. No native layout or filtering configuration guarantees valid traffic.
Compare like-for-like events. Use this guide to agree the reporting definitions for your native ads setup before traffic starts.
A useful native test joins three things: a clearly sponsored recommendation, an accurate creative promise and a destination that fulfils it. Evaluate the complete card in its real publisher layout.
Connect the creative, placement and reporting decisions before traffic starts. These are the practical questions to resolve with your team.
A native campaign asks a reader to choose a sponsored recommendation among other content. Explain what they will find after clicking: a product collection, a useful demonstration or a clearly described offer. Prepare an image that works at the required crop and remains recognizable without small embedded text. The headline should still make sense when read without the image.
Keep the landing page aligned with that expectation. If a recommendation promises practical information, a destination that immediately changes the subject can attract clicks without useful engagement. Test one meaningful creative difference at a time, such as the product angle or image subject, and keep descriptive names for the versions you compare.
A publisher can position native inventory within an eligible feed or around the end of an article, depending on the reviewed placement. Look at where readers naturally look for their next item. Match the card structure to the surrounding page while preserving a visible sponsored label, so visual consistency does not become confusion about who paid for the message.
Test headline wrapping, image crops, card counts and spacing at narrow widths. A multi-card unit that works on desktop may create a long interruption on mobile. Decide how the unit behaves when fewer advertisements are available, and review destination suitability along with the appearance of the cards themselves.
Review impression and click activity by headline, image and placement where those dimensions are available. A recommendation can generate interest for the wrong reason, so CTR should lead to a closer look at the resulting visits rather than becoming the sole success criterion. Use a defined conversion or another relevant post-click event to evaluate the promise made by the creative.
For a publisher, consider how the sponsored unit affects onward reading and the usefulness of the surrounding recommendations. A visually dominant card can redirect attention away from your own content. Compare a controlled layout change with a similar traffic mix, and preserve the ad label during every experiment.
A native card adapts to the layout around it. Contextual advertising uses supported information about the page to help choose a message. A placement may combine the two, but a recommendation is not automatically selected by topic merely because it looks native. Confirm the available matching signals separately from the card design.
No. It is paid advertising and should carry a clear sponsored or advertising label.
The publisher renderer controls the presentation within supported specifications; the advertiser supplies the required creative assets.
Only when it meets each placement's specifications. Check aspect ratio, crop behavior and supported resolutions with the renderer. Important product information should not depend on text that becomes too small or disappears when the image is cropped.
The headline may create an expectation that the landing page or offer does not fulfil. Review the message, destination, source and device journey together. A high CTR is a diagnostic signal, not proof that the campaign is producing valuable customers.
Changes must follow the agreed creative and rendering rules. Cropping an image or shortening a headline can alter the offer’s meaning, while changing links can break attribution. Review template behavior and approved variations before applying them across every card.
The headline may attract interest that the destination does not satisfy, or the placement may generate accidental interactions. Check the message, mobile layout and tracking before increasing spend. Compare accepted business outcomes rather than treating CTR as proof of traffic quality.