네이티브 광고

This guide is for publishers who want to display Native ads on their websites. It covers the embed code, CSS styling and optional custom layouts.

Create a Native ads tool for an approved traffic source. Paste its code where cards should appear. Choose Image + title or Image + title + description, then the layout (grid, row or single card), one to four cards and colours. Image shapes are 16:9 (the default), 1.91:1 and square. Missing descriptions are omitted.

Native ads use static images and CPM. The SDK reports a billable view after the main image loads and at least 50% of the card remains visible for one continuous second while the page is active. Loading ad data alone does not create a billable view. Clicks are tracked separately, with at most one recorded click per card.

Customising the CSS

The embed adds the classes below and loads /native/widget.min.css automatically. Add your rules to your site's stylesheet: the defaults have zero specificity, so !important is unnecessary regardless of load order. To customise one placement, prefix the class with [data-tm-native="ZONE"]. Keep the AD badge and any supplied ad choices link visible and readable.

CSSElement
.tm-nativeCard container
.tm-native-grid, .tm-native-row, .tm-native-singleSelected layout
.tm-native-cardIndividual card
.tm-native-linkCreative link
.tm-native-imageMain image
.tm-native-bodyText container
.tm-native-disclosureAD badge linking to the installation privacy page; optional brand in its tooltip
.tm-native-titleTitle
.tm-native-descriptionDescription
.tm-native-privacyAd choices link
/* Replace ZONE with your placement key. */
[data-tm-native="ZONE"] { gap: 24px; }
[data-tm-native="ZONE"] .tm-native-card {
    border-radius: 0;
    background: #f8fafc;
    color: #172033;
    font-family: inherit;
}
[data-tm-native="ZONE"] .tm-native-title { font-size: 20px; }
[data-tm-native="ZONE"] .tm-native-image { aspect-ratio: 16 / 9; }
[data-tm-native="ZONE"] .tm-native-disclosure { font-size: 12px; }

JSON and custom layouts

For a custom layout, load the SDK with ?k=ZONE&sdk=1, request data with TMNative.request(config), and insert content using textContent. Pass the mounted card and its main image to the tracking SDK. Keep the advertising disclosure visible. Each card needs a separate auction; never reuse a response for another impression.

For multiple custom cards, request them in sequence. Pass earlier responses’ campaignKey values in config.exclude (up to four keys) to select each campaign at most once per widget and avoid multiple cards competing for the same campaign cap. The default embed does this automatically.

The AD badge links to ad.disclosureUrl, the installation privacy page. An optional brand appears in its tooltip. If the response includes ad.privacy, display it as a separate ad choices link. The tracking SDK adds missing disclosure and ad choices elements to custom cards. Keep these links separate from the advertiser click URL.

<script src="https://YOUR-TRACKING-DOMAIN/native/?k=ZONE&sdk=1"></script>
<div id="native-slot"></div>
<script>
const config = {key: 'ZONE', endpoint: 'https://YOUR-TRACKING-DOMAIN/native/ads.php'};
TMNative.request(config).then(ticket => {
    if (!ticket) return;
    TMNative.render(document.getElementById('native-slot'), ticket, config);
    // Custom DOM instead: TMNative.track(card, mainImage, ticket, config).
});
</script>