> For the complete documentation index, see [llms.txt](https://docs.digitalturbine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalturbine.com/dt-ads-demand/ad-creative-types/native-ads.md).

# Native Ads

Native ads are video or interactive ads that appear within the context of the user experience, such as in-feed sponsored content.

### Identifying Native Ad Inventory

In a bid request, a value of `1` for the `imp.native` attribute indicates that the ad is a Native Ad. The [`Native`](https://gitlab.com/digitalturbine/dt-developer-portal/gitbook/-/blob/main/14_exchange_dsp/dt-exchange-openrtb-2.5-specs#object-native) object specifies the supported version and asset types.

### Specifying Native Ads in a Bid Response

DT accepts Native Ad videos using the VAST protocol. Your bid response should use the VAST version requested by the publisher and include the necessary tracking and creative elements. Native Ads should follow the exact specification of the video protocol or API framework passed in the bid request. The DT SDK Video Player provides the following video player elements for Native Ads:

* Skipability: Native Ads are non-skippable, and no **Skip** button is presented to the user.
* End Card Behavior: End cards do not apply to Native Ads.
* Orientation: DT has no orientation restrictions and abides by app and device settings.

### Closing Native Ads

Device users cannot close Native Ads, and DT does not present a button to close the ad. Custom close functions are not supported.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digitalturbine.com/dt-ads-demand/ad-creative-types/native-ads.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.