> ## 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.

# /dmp/v0/log

> Records ad interaction events for advertising optimization and analytics.

Supported event types:
- Impressions (imp): Records ad view events
- Clicks (clk): Records ad click events
- Conversions (conv): Records post-view conversion events including purchases, installations, and subscriptions

Note: Returns 200 OK for all requests. Invalid schemas are silently ignored.



## OpenAPI

````yaml /openapi/decision.api.en-0.2.2.json post /dmp/v0/log
openapi: 3.1.0
info:
  contact:
    email: a2support@aiderx.io
    name: A2 Support
    url: https://aiderx.io
  description: >+

    ### Introduction

    The Decision API is responsible for selecting and distributing ads or
    content based on user requests or contextual information, all in real time.

    Its rapid response and dynamic capabilities enable the **optimal** ad or
    recommendation to be served, ensuring users receive the highest possible
    value.


    A variety of algorithms, machine learning models, and rule-based logic can
    be applied, allowing the system to **adapt flexibly** to constantly changing
    conditions.

  title: Decision APIs
  version: v0.2.2
  x-logo:
    altText: A2 Logo
    url: >-
      https://cdn.prod.website-files.com/668de9e1f25ab5675d87758d/6690cf1bdce95af5e3522c25_a2_logo_800_250.png
servers: []
security: []
tags:
  - description: >

      Ad Serving APIs for requesting ads and configuring cache settings and
      other parameters of the ad serving modules.
    name: Ad Serving
  - description: >-

      APIs for manipulating caches of the serving server.


      ### **Important**

      If you directly manipulate the cached data related to advertising or
      recommendations on the Serving server,

      we **strongly advise** against also modifying the advertising or
      recommendation data through the Ad Manager.


      Alternatively, we **recommend** handling any advertising or recommendation
      data modifications via the Ad Manager APIs.

      Any changes made on the Serving server will **not** be reflected in the Ad
      Manager,

      which can compromise **data integrity**.
    name: Cache Management
  - description: |-

      APIs for manipulating configurations of the serving server
    name: Configuration
  - description: >

      APIs for receiving ad conversion, impression, and click logs — essential
      for tracking and optimizing advertisement performance.
    name: Ad Serving
paths:
  /dmp/v0/log:
    post:
      tags:
        - Ad Log
      summary: /dmp/v0/log
      description: >-
        Records ad interaction events for advertising optimization and
        analytics.


        Supported event types:

        - Impressions (imp): Records ad view events

        - Clicks (clk): Records ad click events

        - Conversions (conv): Records post-view conversion events including
        purchases, installations, and subscriptions


        Note: Returns 200 OK for all requests. Invalid schemas are silently
        ignored.
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/LogType'
        required: true
      responses:
        '200':
          description: OK
      security:
        - '': []
components:
  schemas:
    LogType:
      anyOf:
        - $ref: '#/components/schemas/AdLog'
    AdLog:
      properties:
        action:
          $ref: '#/components/schemas/ActionType'
          description: 'Event type - One of: `clk`, `imp`, `conv`'
        ad_log:
          description: >-
            Ad tracking identifier from Decision API responses (ext.ad_log
            field)
          type: string
        price:
          description: >-
            Monetary value of the conversion (optional). Include only when an
            accurate value is available.
          format: double
          type:
            - number
            - 'null'
        type:
          $ref: '#/components/schemas/AdLogType'
      required:
        - action
        - ad_log
        - type
      type: object
    ActionType:
      oneOf:
        - description: Click event - Records when a user clicks on an advertisement
          enum:
            - clk
          type: string
        - description: >-
            Impression event - Records when an advertisement is displayed to a
            user.


            Note: While optional in A2, impression logging is recommended for
            accurate metrics
          enum:
            - imp
          type: string
        - description: >-
            Conversion event - Records when a user performs a valuable action
            after viewing an ad. Conversions can be defined based on your
            business goals.


            Example conversion activities include:


            * Product purchase

            * Cart addition

            * Application installation

            * Service subscription

            * File download

            * Link click

            * Timed content consumption


            You can define any meaningful user action as a conversion based on
            your advertising objectives.
          enum:
            - conv
          type: string
    AdLogType:
      enum:
        - ad_log
      type: string

````