---
title: "Create and manage Advertisements"
slug: "create-and-manage-advertisements"
updated: 2025-09-01T10:51:34Z
published: 2025-09-01T10:51:34Z
canonical: "documentation.deltatre.com/create-and-manage-advertisements"
---

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

# Create and manage Advertisements

> [!NOTE]
> **Note:**This entity can be customized to fit bespoke needs. The fields described in this article may not coincide with the ones in your FORGE instance.

## Where do I find Advertisements?

In the menu on the left, select the *Advertisement* icon:

![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/21582580460828.png)

**Note:**The *Advertisements* icon can be in a different place because of the custom entities in your FORGE instance.

## Managing the Advertisement entity

When creating and managing an *Advertisement* entity, the entity-specific fields are:

- **Name**: The internal or display name of the advertisement, used for identification and reporting.
- **URL**: The destination link users are taken to when interacting with the ad.
- **Billboard (970x90)**: A wide, high-impact banner format typically placed at the top of desktop pages.
- **Leaderboard Large (728x250)**: An extended leaderboard format offering more vertical space for rich creative on desktop.
- **Leaderboard (728x90)**: A standard horizontal banner used across desktop sites, often in header or footer areas.
- **Leaderboard Mobile (320x50)**: A compact banner format optimized for visibility on mobile devices.
- **Mrec (300x250)**: A medium rectangle banner, commonly embedded in content areas for high engagement.

![](https://cdn.document360.io/2e698e3c-4773-44a4-9476-1d05bac85eee/Images/Documentation/21583669935772.png)

## Translations

‌*Advertisement*entities follow [the language-independent workflow](/v1/docs/translations-with-language-independent-workflow). The entity fields and publishing status can be different for each language.

For example, an *Advertisement*can have different field values for the English UK language and for the French language. Also, the English UK *Advertisement* can be published while the French one is unpublished.