> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aiderx.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Native formats and styles

> Define the fields in native creatives and prepare a presentation for an AdUnit.

To serve native creatives that you register directly, use an administrator or operator account to prepare a **format** and a **style**. A format defines the fields and input rules a creative must provide. A style lays out and formats those fields on the page. Link a style for each format to the AdUnit.

![A native format defines fields, a creative fills values, and a style lays them out for rendering in an AdUnit](https://mintcdn.com/aiderx/PhozVR5g7G_8N2UG/images/guides/en/native-structure.png?fit=max\&auto=format\&n=PhozVR5g7G_8N2UG\&q=85\&s=f2209cb0d93f7ef02543d58ccd87cf29)

When an external ad network supplies the assets, you may not need a style that you created. First check the AdUnit's [native rendering mode](https://docs.aiderx.io/guides/for-retailers/en/placement.md#3-prepare-a-native-adunit) and your service integration.

![Three native setup steps: create and activate a format, create and activate a style, link one style per format to an AdUnit](https://mintcdn.com/aiderx/PhozVR5g7G_8N2UG/images/guides/en/native-setup.png?fit=max\&auto=format\&n=PhozVR5g7G_8N2UG\&q=85\&s=0c9d9129100706d0fb828a73c337d606)

## Create a native format

1. Open **Native → Formats** and select **Create format**.
2. Enter a **Format name** and, if needed, a **Description**.
3. Select **Add field** to define the values a creative can provide.
4. For each field, set its **Kind**, **Identifier**, **Label**, and whether it is **Required**. Add a description and constraints if needed, then save the field.
5. Review the field list, including its input type, required setting, and constraints, then select **Create format**.
6. A new format starts as **Inactive**. Select **Activate** on the format detail page. Inactive formats do not appear when you create a style.

| Field setting | Purpose and options |
| - | - |
| Kind | Choose Title, Image, Data, or Link. Image and Data also require a subtype. |
| Identifier | A name the system uses to identify the field. Use lowercase English letters and underscores, and do not repeat an identifier in the format. Example: `main_image` |
| Label | A human-readable name shown to the person entering creative content. You can keep it the same as the identifier. |
| Required | Whether every creative must provide a value for this field. |
| Constraints | Set a maximum text length, minimum or maximum number, allowed image ratios, or URL schemes when needed. |

The format editor supports **Title**, **Image**, **Data**, and **Link** kinds. Data can accept text or a number. Image and Data require a subtype. The format editor does not support Video fields.

> You cannot add, edit, or delete fields after a style or creative is linked to the format. To change the field structure, create a new format and link styles and creatives to it. Deactivating or deleting a format may also be blocked while it has published allocations, linked styles, or creatives.

![Native formats list](https://mintcdn.com/aiderx/PhozVR5g7G_8N2UG/images/guides/en/native-formats.png?fit=max\&auto=format\&n=PhozVR5g7G_8N2UG\&q=85\&s=17b45780aba53a08d5f3e37de21513b5)

![Field list on the native format detail page](https://mintcdn.com/aiderx/PhozVR5g7G_8N2UG/images/guides/en/native-format-detail.png?fit=max\&auto=format\&n=PhozVR5g7G_8N2UG\&q=85\&s=2eb9ca04f6900b6ab9885d582792e8b4)

## Create a native style

1. Open **Native → Styles** and select **Create style**.
2. Choose **Guided design editor** or **HTML / CSS editor**.
3. Enter a **Style name** and optional **Description**, then choose **Native size**: **Fluid** or **Fixed**. For a fixed size, select a listed size or enter the width and height.
4. Select the **Native format**. If you chose the Guided design editor, also choose a template.
5. In the design step, adjust the template layout and appearance. In the HTML / CSS editor, enter code or generate starter code for the format's fields and edit it.
6. Check the preview to make sure the fields appear in the intended order and layout, then save.
7. A new style also starts as **Inactive**. Select **Activate** on the style detail page. An inactive format or style cannot be linked to an AdUnit.

The Guided design editor supports standard formats. Use the **HTML / CSS editor** for a user-defined format. Only active formats appear in the format list. The format and editor type selected when creating a style cannot be changed later, so verify them before saving.

![Native styles list](https://mintcdn.com/aiderx/PhozVR5g7G_8N2UG/images/guides/en/native-styles.png?fit=max\&auto=format\&n=PhozVR5g7G_8N2UG\&q=85\&s=42b49be4981b3644ff54e28064e373d3)

![Preview tab on the native style detail page](https://mintcdn.com/aiderx/PhozVR5g7G_8N2UG/images/guides/en/native-style-detail.png?fit=max\&auto=format\&n=PhozVR5g7G_8N2UG\&q=85\&s=fd449159dc54c64934bc0726acd8aac1)

## Link a style to an AdUnit

1. Open the **Native Styles** tab on the [AdUnit detail page](https://docs.aiderx.io/guides/for-retailers/en/placement.md#3-prepare-a-native-adunit).
2. Select **Add Style**.
3. Select the **Native Format** and a **Style** created for that format, then save.
4. Confirm the format and style in the linked list.

An AdUnit can have one linked style per format. In **Asset** rendering mode, you cannot add or change style links, though you can review or unlink existing mappings. If a published allocation is currently using the format and style, changing the mapping may be blocked. Check the delivery impact with your operations team before making a change.

## Verify the setup

* In the format details, confirm the fields, required settings, and constraints.
* In the style preview, check that values similar to real creative content appear as intended.
* In the AdUnit details, confirm the selected format and style are linked.
* Asset rendering also returns the native response and original assets. To verify the result with the Style applied, your service must use HTML rendering. See [Manage AdUnits and Placements](https://docs.aiderx.io/guides/for-retailers/en/placement.md) for the integration steps.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.