Image ad items (commonly known as "display ads") are an effective medium for delivering advertising messages across multiple platforms. They are easy to setup and configure because they require only a creative (i.e. an image file) and, when applicable, a destination URL to which users will be redirected when the ad is clicked.
In general, ad items are assigned to an advertiser campaign, and in turn the campaign to a zone. Ad items can also be assigned directly to a zone, but we recommend doing so only if the ad items are directly related to that zone's publisher or are intended to be default/house ads.
x-group: Campañas - name: Ad Items / Custom HTML description: >-Creating a custom HTML ad item is the best option if you need to serve a third-party advertisement from an ad network or another advertiser, or if you want to create an ad that cannot be achieved using traditional display advertising.
Custom HTML ad items allow you to implement virtually any type of ad using Haku’s ad serving macros and a text box.
In general, ad items are assigned to an advertiser campaign, and in turn the campaign to a zone. Ad items can also be assigned directly to a zone, but we recommend doing so only if the ad items are directly related to that zone's publisher or are intended to be default/house ads.
x-group: Campañas - name: Ad Items / Native description: >- Native ad items use native templates to create seamless editorial content.Ad item companion products link an ad item to a product in a product DB catalog. Each companion product belongs to a single ad item and references a specific product via a catalog ID and product identifier (SKU).
Companion products are nested under ad items and can be
managed under both
/ad-items/image/{ad_item_id}/companions/products and
/ad-items/native/{ad_item_id}/companions/products.
Requires the Display Ad Item Companions and Product DB Replicated features.
x-group: Retail media - name: AdServe description: > For server-side ad requests via JSON API, use the adserve endpoint to request ad items in JSON format from the ad server.Ad items represent the particular catalog item (product) being promoted. One or more catalog ad items may be assigned to a campaign.
x-group: Retail media - name: Ad Items / Catalog Item / Bulk description: >-Bulk operations for catalog ad items. These endpoints allow you to create or delete multiple catalog ad items at once and assign them to campaigns.
x-group: Retail media - name: Zones / Catalog description: >-A catalog zone is the representation of a source of promoted product ads. Advertiser campaigns would be assigned to catalog zones (called a placement), making them eligible to be matched against when making an ad request.
x-group: Retail media - name: Creatives (All) description: >- Creatives are the displayed part of an ad item. It can be an image, HTML5/rich media, custom HTML, or video. x-group: Campañas - name: Creatives / Image description: >- The image file that makes up an advertisement is known as the image creative. You can create a new image creative, retrieve one or more image creatives, update an existing image creative, or delete the image creative. x-group: Campañas - name: Data Keys description: >- Aside from keywords, location, and platform-based targeting, Haku also lets you target specific audiences using key value-based attributes. These are called data keys. For example, you can use data keys to target a specific age, gender, or date. Like the other forms of targeting, you must create and define data keys before you can use them. Data keys simply hold the value of attributes. After creating and defining data keys, you must create [Data Key Targets](#tag/Data-Key-Targets) to set up the actual targeting filters. For more information, read How to create data keys and data key targets via API. x-group: Targeting - name: Data Key Targets description: >- Data Key targets are used hand-in-hand with [Data Keys](#tag/Data-Keys) to create custom targeting filters. For more information, read How to create data keys and data key targets via API. x-group: Targeting - name: Geo Targets description: >-Geographic targets ("geo targets") enable you to deliver advertisements to users based on their geographic location. This is an effective way of reducing wasted impressions and increasing your return on investment.
Geographic targeting can be as generic as continents or as specific as cities. A geo target may contain as many areas as desired which can vary in specificity. (For example, an area of "South America" and an area of a specific city could exist in the same geo target.) Geo targets can either be inclusive or exclusive.
x-group: Targeting - name: Media Groups description: >- Media groups allow you to group creatives together for easier organization and management in your account. x-group: Campañas - name: Native Templates description: >- Native templates define the styles and formatting of native ads. Once a template is created it can then be applied, reused, and edited as needed to make native ad items.Native ads are ads that look like editorial content. For example, a native ad on a blog looks like the other articles on the site, a native ad on Instagram looks like an Instagram post, and a native ad on a search engine looks like other search results. Native ads are also known as sponsored content or promoted posts. x-group: Inventario - name: Placements description: >- Assign an advertisement or campaign to a zone based on a set of scheduling criteria using the placements endpoint. Each placement represents a combination of criteria required to serve an advertisement. Prior to creating a placement, you will need to have created several other resources: * An [ad item](#tag/Ad-Items-(All)), * a [campaign](#tag/Campaigns-(All)), * a [zone](#tag/Zones-(All)), * and a [schedule](#tag/Schedules) You also have the option to create targeting filters, keywords, and activity limits to further control the deliverability of your placements. x-group: Campañas - name: Platform Targets description: >-Target your advertisements to specific mobile/tablet/notebook/desktop devices, or to specific browsers and operating systems to help ensure users get the best ads for their platform. You can also target specific mobile phones or tablets, such as iPhones or Samsung devices using device targeting filters.
x-group: Targeting - name: Product DB / Catalog description:Product catalogs that can be used for product-based advertising.
x-group: Retail media - name: Product DB / Catalog Items description: >-Product catalog items that can be used for product-based advertising.
x-group: Retail media - name: Product DB / Catalog Items / Bulk Upload description: >-Bulk upload a catalog CSV with column names that match the fields submitted to a catalog.
x-group: Retail media - name: Product DB / Publisher Sources description: >-Publisher Sources that can be used for product-based advertising targeting.
x-group: Retail media - name: Product DB / Publisher Source Targets description: >-Publisher Source Targets that can be used for product-based advertising targeting.
x-group: Retail media - name: Publishers description: >- A publisher is typically a person or a company who owns a website, app, newsletter, or even another ad server. Each publisher will have one or more zones, which represent the locations on their websites, apps or newsletters where advertisements can be displayed. x-group: Inventario - name: Reports description: >-Reporting is the new interface to Statistics. It serves to quantify the serving of your advertisements across price and performance related metrics. They are updated in real time. We go to great lengths to give you detailed and accurate data about the performance of your advertisements to help you make informed decisions. The following endpoints enable you to build your own reporting dashboard.
x-group: Reportes - name: Schedules description: >- Schedules describe the conditions necessary for serving advertisements. Common conditions include start and end dates, and quotas. You can also use delivery methods to determine the expiration and pacing set up for advertisements. Default delivery delivers the impressions as quickly as possible, while smooth delivery will evenly serve impressions over the lifetime dates and quotas. For example, with smooth delivery, if your campaign has a quota of 30,000 impression set over a period of 60 days, the system would serve the assignment 500 times per day. Smooth delivery assignments have the highest potential priority for serving within Haku. If a quota has not been filled then that assignment will generally always serve as long as a targeting system does not interfere. __NOTE__: Schedules have no effect on their own and must be referenced through their ID. For campaigns with campaign-level scheduling, the schedule must be referenced in the [placement](#tag/Placements). For campaigns with ad item-level scheduling, the schedule must be referenced in the [campaign assignment](#tag/Campaign-Assignments) for each ad item in the campaign. Multiple placements and assignments can reference the same schedule, so they can share the same quota, start/end dates, and other common settings. x-group: Campañas - name: Zones (All) description: > Zones represent the space on a Publisher's website where ads are displayed ("served"). A zone's size can either be fixed or dynamic. The types of zones are: * __Standard__ - The most common, used to serve various ads including image, HTML5/Rich Media, Native Ads or third party scripts. * __VAST__ - Used to serve VAST video ads. * __Email__ - Used to serve image ads in emails and newsletters. x-group: Inventario - name: Zones / Standard description: >- The most common zone type. Used to serve image ads (JPG,PNG, or GIF), HTML5/Rich Media, or third party scripts. x-group: Inventario paths: /ad-items/native/{ad_item_id}/companions/products/{id}: get: tags: - Ad Items / Companion Products summary: Get a Companion Product for a Native Ad Item parameters: - name: ad_item_id in: path description: Identifier of the ad item. required: true schema: type: integer example: '' - name: id in: path description: Identifier of the companion product. required: true schema: type: integer example: '' - $ref: '#/components/parameters/fields' responses: '200': description: successful operation content: application/json: schema: $ref: '#/components/schemas/ad_item_companion_product_get' '404': $ref: '#/components/responses/resource_does_not_exist' components: parameters: fields: name: fields in: query description: >- Restrict the fields you wish to retrieve by listing the desired fields formatted as a comma-separated list. Fields like "object", "self", and "id" are always returned. schema: type: string schemas: ad_item_companion_product_get: allOf: - $ref: '#/components/schemas/resource_get' - properties: object: type: string example: ad_item_companion_product self: type: string example: /v2/ad-items/image/1234/companions/products/5678 type: object - $ref: '#/components/schemas/ad_item_companion_product' resource_get: properties: object: description: A string denoting the current resource being requested or affected. type: string readOnly: true self: description: >- The relative URL of the current resource being requested or affected. type: string readOnly: true id: description: The current resource identifier (ID). type: integer readOnly: true example: 1234 type: object ad_item_companion_product: properties: catalog: description: The ID of the product DB catalog. type: integer example: 10001 product_identifier: description: The product identifier (SKU) within the catalog. type: string example: SKU-1001 type: object error_resource_does_not_exist: properties: http_status: type: integer example: 404 type: type: string example: resource_not_found_error message: type: string example: Resource not found. type: object responses: resource_does_not_exist: description: Resource not found content: application/json: schema: $ref: '#/components/schemas/error_resource_does_not_exist' securitySchemes: API Key: type: apiKey in: header name: Authorization description: >- API key en el header `Authorization: Basic TU_API_KEY`. La key va tal cual, sin codificar en base64. Las credenciales se entregan al comenzar la integración. ````