---
title: "Self Serve Native Traffic: Plan, Launch & Optimize Campaigns"
canonical: "https://froggyads.com/self-serve-native-traffic/"
markdown_url: "https://froggyads.com/self-serve-native-traffic.md"
description: "Evaluate self serve native traffic through native placements, publisher context, creative fit, source reporting, tracking and accepted campaign economics."
language: "en"
---

Self-serve workflow

# Self Serve Native Traffic

Evaluate self serve native traffic through native placements, publisher context, creative fit, source reporting, tracking and accepted campaign economics, with controlled budgets and decision rules that avoid unsupported performance guarantees.

[Create My Free Account](https://premium.froggyads.com/#/signup)[Explore Native Ads](https://froggyads.com/native-ads-guide/)Self-serve control ·750+ SSP integrations ·20B+ daily impressions

![self serve native traffic planning visual](https://froggyads.com/assets-redesign-2026/images/v80-native-traffic-banner-network/self-serve-native-traffic-hero.svg)

Direct answer

## What Self Serve Native Traffic Means

Self Serve Native Traffic refers to sponsored content placements that are designed to fit the surrounding publisher experience while remaining clearly identified as advertising. Buyers normally combine a headline, image, brand name and destination, then evaluate performance by placement, source, device, GEO and accepted backend outcome. The practical focus for self serve native traffic is direct control over targeting, bids, budgets and source decisions. Use a controlled discovery budget and explicit keep, pause and scale rules before expanding spend.

01 • Format mechanics

## Understand How Native Ads Are Delivered

Self Serve Native Traffic begins with the real delivery model. Native units usually combine a headline, image, brand label and destination inside a publisher feed, recommendation area or content module. The ad should match the visual environment without disguising its commercial nature. For self serve native traffic, document the event chain from auction and impression through interaction, destination load, click identification and accepted backend outcome. Separate problems caused by rendering, placement, creative, destination speed and attribution. A platform total is not enough when the buyer cannot connect spend to a source and a validated result.

02 • Evaluation focus

## Define what Self Serve Native Traffic means for the campaign

The commercial wording in self serve native traffic should be converted into a measurable buyer requirement. In this guide, the useful boundary is direct control over targeting, bids, budgets and source decisions. Write the required GEOs, devices, inventory type, reporting fields, budget, attribution window and accepted outcome before comparing options. This prevents broad words such as best, top, cheap, trusted, global or fast from becoming unsupported promises. The correct conclusion can differ by offer, destination, creative capacity, compliance needs and the value of an accepted result.

03 • Inventory context

## Evaluate Supply Beyond a Volume Claim

Inventory quality for self serve native traffic depends on where and how the ad appears, not only how many impressions are available. Ask where the unit appears, how sponsored labeling is presented, which source or placement IDs are available, and whether feed position, widget type, device and category can be reported or controlled. Confirm whether the platform can preserve placement identifiers through reports and tracking parameters. Review the likely mix by GEO, browser, operating system, connection type and time of day. A broad reach claim is useful only when the buyer can isolate segments, control exposure and compare accepted outcomes under a consistent attribution model.

04 • Audience fit

## Define Eligibility Before Buying Reach

The practical role of Define Eligibility Before Buying Reach in Self Serve Native Traffic is to expose the exact condition that can change the buyer's next action. The evidence record should make List, offer, devices, languages, supported and action visible instead of hiding them inside a blended score or an unexplained recommendation. Keep the baseline unchanged while testing the next hypothesis; that comparison is what makes the decision reproducible. If the next step is a media test, FroggyAds lets the advertiser keep campaign settings and source-level performance visible instead of treating traffic volume as proof of success.

**Connect the guide to live testing**

## Connect Self Serve Native Traffic to a controlled audience test

A buyer evaluating Self Serve Native Traffic can use Connect Self Serve Native Traffic to a controlled audience test to make the page actionable: identify the condition, document the evidence, and define the response. The evidence record should make choices, established, Define, Eligibility, Buying and Reach visible instead of hiding them inside a blended score or an unexplained recommendation. When the evidence is strong, carry the exact setting or requirement into the next campaign step instead of broadening several variables at once.

[Create My Free Account](https://premium.froggyads.com/#/signup)

![Illustration of audience targeting controls for a self serve native traffic test](https://froggyads.com/assets-redesign-2026/images/showcase-audience-targeting.svg)

05 • Creative system

## Build Creative Assets for the Real Placement

Test meaningful combinations of image, headline, brand name and description. Keep claims truthful, avoid misleading editorial cues and make the destination continue the promise shown in the unit. For self serve native traffic, create several distinct concepts instead of minor color changes. Each concept should express one benefit, problem, proof point or use case and should be traceable through a unique creative identifier. Record the source files, launch date, message angle and destination version. This makes creative fatigue, placement mismatch and source quality easier to distinguish. Never use fabricated ratings, false urgency, fake interface elements or unsupported performance statements.

06 • Responsive production

## Protect Readability Across Devices and Placements

Use image assets that remain legible across responsive crops and device classes. Protect the focal point, avoid text-heavy images and verify how headlines truncate in real publisher placements. Preview self serve native traffic in representative desktop, tablet and mobile environments, including slower connections and common browser chrome. Check image crops, headline wrapping, contrast, brand visibility and the area available for the call to action. A creative that looks polished in a design tool can fail when the publisher template crops the focal point or the smallest placement makes the text unreadable. Keep the asset set manageable so each variation receives enough data to evaluate.

07 • Destination continuity

## Landing-page continuity for Self Serve Native Traffic

The destination should immediately confirm the message shown by self serve native traffic. Use a fast, responsive page that identifies the advertiser, explains the real benefit, shows important conditions and provides one clear next step. If the campaign uses an educational article or prelander, it should add truthful context rather than conceal the final offer. Measure response time, engaged sessions, form starts, accepted outcomes and rejection reasons by creative and source. Strong media can appear weak when message continuity or mobile usability breaks after the click.

08 • Attribution

## Create a Reliable Impression-to-Outcome Chain

Pass unique campaign, creative, click, source and placement identifiers wherever the platform supports them. Return validated outcomes through a server-to-server postback or another reliable integration, and align time zones, attribution windows and duplicate rules across the ad platform, tracker, analytics and backend. Before meaningful spend on self serve native traffic, complete a live test and confirm the exact identifier stored in every system. The goal is not perfect agreement between tools. It is enough consistent evidence to repeat a source decision and explain material discrepancies. For this URL, connect the point to the goal to acquire and qualify self serve native traffic by source, device, market, landing behavior and accepted downstream outcome; keep the Self Serve Native Ads intent separate.

![self serve native traffic controlled workflow visual](https://froggyads.com/assets-redesign-2026/images/v80-native-traffic-banner-network/self-serve-native-traffic-workflow.svg)

**Choose the execution format**

## Choose a paid-media format that supports Self Serve Native Traffic

Use the criteria around “Create a Reliable Impression-to-Outcome Chain” to decide whether push, native, display or pop fits the message and destination. Set format, targeting and spend as campaign controls in FroggyAds while the self serve native traffic decision remains the standard for judging the result.

[Create My Free Account](https://premium.froggyads.com/#/signup)

![Illustration comparing advertising formats for self serve native traffic execution](https://froggyads.com/assets-redesign-2026/images/showcase-ad-formats.svg)

09 • Pricing

## Translate Media Cost Into Accepted Acquisition Economics

Self Serve Native Traffic may be bought through CPM, CPC, SmartCPC or another supported auction model depending on the platform and inventory. Convert spend into effective CPC, landing cost, accepted CPA, revenue per click and contribution after variable costs. A low headline rate can be expensive when viewability, engagement or backend acceptance is weak. A higher rate can be efficient when the source produces valuable outcomes. Calculate a maximum bid from conservative assumptions and recheck it when conversion rate, approval rate, payout or source mix changes.

10 • Test protection

## Budget, frequency and stop-rule decisions for Self Serve Native Traffic

Treat Budget, frequency and stop-rule decisions for Self Serve Native Traffic as a specific gate for Self Serve Native Traffic, not as a reusable checklist item that means the same thing on every page. Review controlled, needs, total, loss, limit and daily together, because a strong result in one of them should not conceal a material failure in another. Do not scale the conclusion beyond the evidence window; repeat the check after the next meaningful change in volume, scope or audience.

11 • Traffic quality

## Check Quality Through Behavior and Backend Acceptance

Traffic quality for self serve native traffic should be examined through patterns rather than one label. Review device consistency, duplicate identifiers, abnormal click timing, destination engagement, conversion latency, backend rejection reasons, repeat value and the relationship between front-end events and accepted outcomes. Traffic-quality controls can reduce risk but cannot eliminate every invalid event. Compare sources after enough data and time periods mature. A lower-volume source may be more valuable when acceptance and downstream value are stronger.

12 • Source optimization

## Separate Placement, Bid and Creative Decisions

Optimize self serve native traffic in layers. First fix tracking, rendering or destination failures that affect every source. Next compare sources and placements under a stable creative and bid. Then test bid changes inside comparable inventory, and test creative or destination changes with controlled allocation. Use whitelists only after a source has enough evidence, and keep a discovery path for new inventory. Avoid reacting to one hour, one conversion or a blended average that hides important source differences. Keep this step inside the Self Serve Native Traffic decision boundary: acquire and qualify self serve native traffic by source, device, market, landing behavior and accepted downstream outcome. The adjacent Self Serve Native Ads page answers a different buyer task.

13 • Creative learning

## Structured creative testing for Self Serve Native Traffic

Build a creative matrix for self serve native traffic that separates message angle, visual concept, headline, call to action and destination. Test a few meaningful combinations, not dozens of nearly identical files. Review impressions, viewable impressions when available, clicks, click-through rate, destination engagement, accepted conversion rate, accepted CPA and downstream value by source. Pause clear losers after the planned evidence threshold, but protect promising variations from premature decisions when conversion lag is long. Record why each change was made and what result would support the hypothesis. A disciplined archive becomes a reusable learning system for future GEOs and offers.

14 • Policy and user experience

## Clear, truthful experience requirements for Self Serve Native Traffic

Native advertising works best when the sponsored label is clear, the creative is relevant to the surrounding context and the destination provides the information or offer promised by the unit. Review the full path for self serve native traffic, including the publisher placement, creative, redirects, landing page, forms, checkout and confirmation. Approval depends on policy, destination behavior, vertical, GEO and campaign details. A clean submission can reduce avoidable delay, but no responsible network should promise that every campaign will be accepted immediately. Keep material terms visible and make it easy for the user to leave or decline.

**Put the guide into practice**

## Turn Self Serve Native Traffic into a bounded campaign test

Make Turn Self Serve Native Traffic into a bounded campaign test specific to Self Serve Native Traffic by tying it to the exact workflow, audience or commercial constraint described on this page. Compare Clear, truthful, experience, requirements, documented and launch under the same scope and review window; if one is unknown, keep that uncertainty explicit rather than filling the gap with an estimate. Use the finding to choose a specific action—keep, cap, exclude, renegotiate, retest or stop—rather than recording a score with no operational consequence.

[Create My Free Account](https://premium.froggyads.com/#/signup)

![Illustration of a campaign launch checklist for self serve native traffic](https://froggyads.com/assets-redesign-2026/images/showcase-campaign-launch-checklist.svg)

15 • Measurement

## Decision scorecard for Self Serve Native Traffic: media cost to accepted value

Make Decision scorecard for Self Serve Native Traffic: media cost to accepted value specific to Self Serve Native Traffic by tying it to the exact workflow, audience or commercial constraint described on this page. Use Review, fixed, schedule, scorecard, covering and delivery as the traceable inputs for this section, then state which missing item would be serious enough to stop or narrow the decision. If the section exposes a measurement gap, repair that gap before changing the offer, creative and targeting simultaneously.

![self serve native traffic decision scorecard visual](https://froggyads.com/assets-redesign-2026/images/v80-native-traffic-banner-network/self-serve-native-traffic-scorecard.svg)

16 • Scaling and rollback

## Controlled scaling for Self Serve Native Traffic after a verified change

Scale self serve native traffic only after attribution is stable, accepted acquisition cost is inside the planned range and performance survives a measured increase. Expand one dimension at a time, such as budget, bid, source set, GEO or creative coverage. Monitor marginal performance rather than assuming the historical average will continue. If the source mix, acceptance rate or contribution changes materially, roll back to the last stable configuration and reopen discovery. Results depend on offer, market, creative, destination, competition and optimization, so no page can guarantee the outcome. The page-specific use of this step is to acquire and qualify self serve native traffic by source, device, market, landing behavior and accepted downstream outcome. That boundary distinguishes Self Serve Native Traffic from Self Serve Native Ads.

17 • Scenario planning

## Conservative, expected and stress scenarios for Self Serve Native Traffic

Create three planning cases for self serve native traffic. The conservative case should use a lower click or engagement rate, weaker backend acceptance and the upper end of expected media cost. The expected case should use evidence from the first controlled cohort, not a sales estimate. The stress case should model a sudden shift in source mix, creative fatigue or a longer conversion delay. Calculate the spend, accepted outcomes and contribution for each case. Scenario planning does not predict the future, but it shows how much performance can deteriorate before the campaign crosses its loss limit and which signal should trigger a rollback.

18 • Operator checklist

## Close the Self Serve Native Traffic review with a dated action and evidence requirement

Make Close the Self Serve Native Traffic review with a dated action and evidence requirement specific to Self Serve Native Traffic by tying it to the exact workflow, audience or commercial constraint described on this page. Review review, record, creative, active, bids and caps together, because a strong result in one of them should not conceal a material failure in another. Connect the finding to one owner and one next action so the page helps the visitor decide rather than merely describing a process. For a FroggyAds campaign, translate this conclusion into the narrowest applicable targeting or budget change and reconcile the result with the accepted business event.

Decision controls

## Practical Review Table for Self Serve Native Traffic

| Area | Evidence required | Action |
|---|---|---|
| Creative fit | The asset is legible and truthful in the real placement | Keep only distinct concepts with stable delivery |
| Attribution | Creative, click and source IDs reach the backend | Run a live accepted-outcome test |
| Quality | Engagement, acceptance and rejection reasons are visible | Pause abnormal or low-value sources |
| Economics | Effective CPC and accepted CPA are calculated | Compare against the planned limit |
| Scaling | Marginal performance remains stable | Increase one dimension in measured steps |

Questions media buyers ask

## Self Serve Native Traffic FAQ

### What context explains where self-serve native traffic began?

Publisher, page topic, placement, template, disclosure, device, and creative values describe the starting environment. That detail supports local quality decisions.

### What proof shows that native traffic followed a disclosed ad?

A served-template capture, label state, publisher-placement value, and response record show the commercial context. Aggregate visits cannot establish disclosure.

### How does publisher topic affect interpretation of native traffic?

The topic explains what the customer was reading when the recommendation appeared. It suggests context, not private intent or guaranteed interest.

### Why is a native click incomplete evidence of traffic quality?

A click confirms response to the unit but cannot establish whether the eventual customer result meets the acceptance standard. Mature backend results provide the commercial measure.

### Which native values should survive into the accepted result?

Permitted publisher, placement, template, creative, campaign, and device values should survive into the mature backend record. Missing data should remain explicit.

### What cost method compares native traffic sources consistently?

Complete spending for each source divided by mature accepted outcomes provides a common basis. Fees and later-rejected activity stay included.

### What test isolates one native publisher context?

The comparison can vary publisher context while creative, template, and destination stay fixed under one acceptance rule and review period. A fixed spend ceiling contains the test.

### Where do native traffic anomalies become actionable?

Repeated timing, device, disclosure, or placement patterns combined with weak backend acceptance justify investigation. The responsible source needs to remain identifiable.

### When should a native traffic placement be paused?

A repeatable disclosure failure, route problem, or mature quality deficit supports a pause. A correctable template fault may deserve repair and bounded retest.

### Can proven native traffic expand across more publishers?

Broader publisher use is justified once established sources preserve disclosure, route quality, and workable accepted-customer cost. Added publishers should remain distinct until their results mature.

Related campaign resources

## Continue the Native Ads Campaign Workflow

[**Native Ads Guide**Review native ads mechanics, creative requirements and source controls.](https://froggyads.com/native-ads-guide/)[**Campaign Reporting**Align click IDs, attribution windows and backend validation.](https://froggyads.com/campaign-reporting-guide/)[**Source Targeting**Preserve placement identifiers for bidding, whitelists and exclusions.](https://froggyads.com/source-targeting/)[**Creative Testing Framework**Turn message hypotheses into controlled, original tests.](https://froggyads.com/creative-testing/)
Control the campaign directly

## Build a Controlled Self Serve Native Traffic Test

A buyer evaluating Self Serve Native Traffic can use Build a Controlled Self Serve Native Traffic Test to make the page actionable: identify the condition, document the evidence, and define the response. Keep the review anchored to Treat, measured, acquisition, define, accepted and verify; those details are the parts of this section that can materially change the recommendation. If the section exposes a measurement gap, repair that gap before changing the offer, creative and targeting simultaneously. Use FroggyAds to test the media assumption that follows from this section, not to replace the evidence the section requires. Campaign controls support the decision; they do not manufacture proof.

[Create My Free Account](https://premium.froggyads.com/#/signup)[Visit Learning Center](https://froggyads.com/learning-center/)
Advertiser decision framework

## Self Serve Native Traffic: what should the advertiser decide next?

For Self Serve Native Traffic, native means a feed or content-style placement designed to fit the surrounding environment. The buying decision is whether that delivery context fits the offer, creative and destination well enough to produce an accepted post-click result. Use What Self Serve Native Traffic Means and Understand How Native Ads Are Delivered as the page-specific checkpoints, then judge self serve native traffic on headline-image continuity, pre-click context and downstream intent plus downstream conversion quality.

For the Self Serve Native Traffic decision, use Self Serve Native Traffic: what should the advertiser decide next? to separate a real operating requirement from a broad best-practice statement. Document remain, tied, existing, around, Means and Understand in the same decision record so a later reviewer can see why the option passed, failed or needs a narrower retest. Use the finding to choose a specific action—keep, cap, exclude, renegotiate, retest or stop—rather than recording a score with no operational consequence. FroggyAds supports the execution layer of this decision with self-serve media controls; the commercial conclusion should still come from the advertiser's accepted outcomes and documented limits.

| Decision | What to verify | FroggyAds action |
|---|---|---|
| Self Serve Native Traffic objective | Use What Self Serve Native Traffic Means to define the accepted business event and the maximum learning loss for self serve native traffic. | Launch one FroggyAds campaign objective for Self Serve Native Traffic and keep the conversion definition stable. |
| Self Serve Native Traffic audience | Use Understand How Native Ads Are Delivered to verify market, device, language and offer eligibility for self serve native traffic. | Apply only the FroggyAds targeting controls that change the real Self Serve Native Traffic customer journey. |
| Self Serve Native Traffic source evidence | Use Define what Self Serve Native Traffic means for the campaign to keep source-level differences visible instead of relying on one blended self serve native traffic average. | Keep, cap, exclude or retest Self Serve Native Traffic inventory from documented source evidence. |
| Self Serve Native Traffic economics | Use Evaluate Supply Beyond a Volume Claim to connect media spend with accepted conversions and downstream value for self serve native traffic. | Protect the Self Serve Native Traffic test with a written budget boundary and a consistent attribution window. |
| Self Serve Native Traffic scale rule | Use Define Eligibility Before Buying Reach to define the exact evidence that earns the next budget increase for self serve native traffic. | Scale Self Serve Native Traffic one major control at a time and compare marginal performance with the prior baseline. |

### A page-specific FroggyAds test sequence for Self Serve Native Traffic

1. **Self Serve Native Traffic outcome:** define the accepted event for self serve native traffic and the maximum loss permitted while the first test is learning.

2. **Self Serve Native Traffic path:** verify market eligibility, device experience, landing-page continuity and tracking against What Self Serve Native Traffic Means before buying more traffic.

3. **Self Serve Native Traffic hypothesis:** launch one bounded FroggyAds test tied to Understand How Native Ads Are Delivered; do not change bid, creative, audience and destination together.

4. **Self Serve Native Traffic source review:** compare qualified activity, accepted conversions, timing and cost by the source or segment dimensions relevant to Define what Self Serve Native Traffic means for the campaign.

5. **Self Serve Native Traffic scaling:** use Evaluate Supply Beyond a Volume Claim and Define Eligibility Before Buying Reach to define what must reproduce before the next budget increase.

### Why FroggyAds is relevant to Self Serve Native Traffic

For Self Serve Native Traffic, FroggyAds gives advertisers a self-serve DSP and ad-network workflow for buying supported traffic with campaign-level budgets and targeting. Depending on format and campaign context, available controls can include country, city, device, operating system, browser, carrier, category, source, ID and IP options. SmartCPC and Adscore-supported traffic-quality controls can support the self serve native traffic optimization process, while the advertiser's tracker, analytics and backend acceptance remain the final evidence for commercial quality.

The practical role of Why FroggyAds is relevant to Self Serve Native Traffic in Self Serve Native Traffic is to expose the exact condition that can change the buyer's next action. Preserve the source, date and owner for Define, Eligibility, Buying, Reach, final and checkpoint whenever they affect the decision, especially when the page compares options or sets a budget boundary. If the evidence does not support the current assumption, narrow the scope or run the smallest reversible test that can resolve it. Use FroggyAds to test the media assumption that follows from this section, not to replace the evidence the section requires. Campaign controls support the decision; they do not manufacture proof.

[Create your free FroggyAds account](https://premium.froggyads.com/#/signup)

Search intent and buyer decision

## How to use this Self Serve Native Traffic page

This URL has one primary job for **performance-focused advertisers**: **acquire and qualify self serve native traffic by source, device, market, landing behavior and accepted downstream outcome**. Keep this page focused on that buying decision instead of turning it into a generic advertising article. The nearest related FroggyAds page is [Self Serve Native Ads](https://froggyads.com/self-serve-native-ads/); use that URL when its narrower task is the one you actually need.

**Scope boundary:** Use this page when the task is to acquire and qualify self serve native traffic by source, device, market, landing behavior and accepted downstream outcome. Use Self Serve Native Ads instead when the task is to design and test self serve native ads by creative message, format, placement context, destination continuity and accepted response.

The current competitor review for this page records 10 reviewed comparison and competitor pages in the native cluster, with 10 fetched successfully. Separately, the page-level entity coverage tracks publisher styling, ad disclosure, structured creative assets, placement context, and conversion tracking. We use both as coverage checks, not as copied claims or proof of FroggyAds performance. Applied to Self Serve Native Traffic, this check should support the distinct decision to evaluate self-serve setup, control and optimization workflow and remain traceable to the page's own evidence.

For **Self Serve Native Traffic**, evaluate any native placement in its actual publisher context: confirm publisher styling and ad disclosure, check that structured creative assets fit the placement context, and keep conversion tracking aligned to the landing experience. This avoids judging native inventory from a headline or format label alone.

| Step | Ad Format workflow | Evidence to retain |
|---|---|---|
| 1 | Match the format to the user journey and creative requirement | Keep the evidence tied to Self Serve Native Traffic and the accepted outcome defined for this URL. |
| 2 | Control targeting, frequency or placement variables that can change the result | Keep the evidence tied to Self Serve Native Traffic and the accepted outcome defined for this URL. |
| 3 | Compare accepted outcomes by source before scaling the format | Keep the evidence tied to Self Serve Native Traffic and the accepted outcome defined for this URL. |

### Transparent Self Serve Native Traffic decision example

**Hypothetical example:** if a controlled Self Serve Native Traffic test spends USD 225 and records 7 accepted outcomes after the same review window, accepted CPA is USD 225 divided by 7 = **USD 32.14**. Replace the example inputs with your own economics; this is not a FroggyAds performance claim.

Use FroggyAds as the execution layer only when the page's decision calls for paid traffic. Set the relevant budget, targeting and format controls, verify conversion tracking, keep source-level evidence, and increase spend only when the accepted outcome supports the next step. [Create your free FroggyAds account](https://premium.froggyads.com/#/signup). Applied to Self Serve Native Traffic, this check should support the distinct decision to evaluate self-serve setup, control and optimization workflow and remain traceable to the page's own evidence.

**Research basis for Self Serve Native Traffic:** This URL helps performance-focused advertisers evaluate self-serve setup, control and optimization workflow. It is mapped to the native research cluster. Our current review used [support.google.com](https://support.google.com/admanager/answer/6075370?hl=en) and [support.google.com](https://support.google.com/admanager/answer/7031536?hl=en) to check terminology, buyer questions and decision coverage relevant to Self Serve Native Traffic. These external sources are research inputs, not evidence of FroggyAds campaign performance.

Direct answer

## Self Serve Native Traffic — what matters first

**Direct answer:** This page helps you acquire and qualify self serve native traffic by source, device, market, landing behavior and accepted downstream outcome. Keep the comparison or test inside that scope, then use FroggyAds campaign controls only where paid traffic is part of the decision. Apply this evidence to Self Serve Native Traffic only where it helps you acquire and qualify self serve native traffic by source, device, market, landing behavior and accepted downstream outcome; the closest neighboring topic is Self Serve Native Ads.