# Ad Object Structure

### <mark style="color:green;">**AD IMAGE COMPONENTS IN THE ADMOB NATIVE AD FORMAT**</mark>

<div align="left"><figure><img src="/files/OUGadKyA86qTe8zhakxc" alt="" width="375"><figcaption></figcaption></figure></div>

1. Small icon image (e.g. advertiser logo)
2. The Big image showing the product

* The Ad fill may or may not have a big product image.
* If the big product image is available, it can be of landscape, square, or portrait aspect ratio.
* The SDK handles all these conditions automatically and contains <mark style="color:green;">Display Handler Templates</mark> for the different cases.

***

#### <mark style="color:green;">1.1</mark> <mark style="color:green;"></mark><mark style="color:green;">**UNDERSTANDING THE AD DISPLAY VARIANTS**</mark>

The Display Handling Templates can be broadly classified under two categories:

1. MEDIA VIEW TYPES (Ad contains Big Image)
   1. MediaLandscapeSimple
   2. MediaLanscapeBlur
   3. MediaPortrait
2. NON MEDIA VIEW (Ad does not contain Big Image)
   1. NonMedia

***

&#x20;<mark style="color:green;">**1.2 STRUCTURE OF THE SDK AD PREFAB**</mark>

The structure of SDK's Ad object is shown below:

<figure><img src="/files/Kv2fSiaYQwnhXmx47dNj" alt=""><figcaption></figcaption></figure>

The object hierarchy is similar for both Screen Space (<mark style="color:green;">SS\_NativeAd</mark>) and World Space (<mark style="color:green;">WS\_NativeAd</mark>) with minor differences

<table><thead><tr><th width="241">OBJECT NAME</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td></td><td></td></tr><tr><td>Placeholder</td><td>An image to show before the Ad loads<br>This can also be set to None or 100% transparent to show nothing before the Ad is loaded</td></tr><tr><td>MediaViewTypes</td><td>Parent for all Display Templates containing Big Image</td></tr><tr><td>NonMediaView</td><td>Parent for Display Templates without Big Image</td></tr><tr><td>StatusVisualiser</td><td>A debug tool that indicates impression and click detection status <br>Only displayed with Test ads</td></tr></tbody></table>

***

#### &#x20;<mark style="color:green;">**1.3 GENERAL STRUCTURE OF DISPLAY HANDLER  TEMPLATE OBJECTS**</mark>

<figure><img src="/files/aY20sCocc3nZ3Uu9Cdt8" alt=""><figcaption></figcaption></figure>

The image above shows the object hierarchy of the MediaLandscapeSimple display template. The structure is similar to other templates as well with minor variations.

<table><thead><tr><th width="213">GameObject NAME</th><th>DESCRIPTION </th></tr></thead><tbody><tr><td></td><td></td></tr><tr><td>BigImage</td><td>Has image component to display Big Product texture</td></tr><tr><td>AdIconImageHolder</td><td>Background for Ad Icon</td></tr><tr><td>AdIconImg</td><td>Has image component to display Advertiser Logo icon</td></tr><tr><td>CtaStars</td><td>Contains child display objects for CTA button and Star Rating</td></tr><tr><td>AdChoices<br>AdTag</td><td>Google requirements for Ad Compliance</td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://pubscale.gitbook.io/immersive-ads-sdk/presentation/ad-object-structure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.