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

# Custom-conversions list

> List the account's custom conversions — the named conversions built on a dataset's traffic, as opposed to Meta's standard pixel events or named custom pixel events. To verify raw event activity on a dataset, use `adside meta pixel-stats get`; an empty custom-conversion list does not mean the pixel has no events.

Use this to find the ID to optimise an ad set towards: pass it as `promoted_object.custom_conversion_id` on create_ad_set_enhanced or update_ad_set. Many accounts never adopted Meta's standard event taxonomy and put all their real volume here, so a standard event that looks right can have fired zero times.

In reporting and insights breakdowns the same conversion appears as `offsite_conversion.custom.<id>`.

CLI: `adside meta custom-conversions list`



## OpenAPI

````yaml /api-reference/openapi.yaml post /v1/workspaces/{workspaceId}/meta/custom-conversions/list
openapi: 3.1.0
info:
  title: Adside API
  version: 1.0.0
  description: >-
    Campaigns, creatives, assets and reporting across your ad accounts. Call it
    with a personal API key as a bearer token, or with the `adside` CLI: each
    page names its command.
servers:
  - url: https://api.adside.ai
    description: Production
security:
  - userAccess: []
tags:
  - name: Account
  - name: Reporting
  - name: Meta
  - name: Google Ads
  - name: LinkedIn
  - name: TikTok
  - name: Reddit
  - name: Snapchat
  - name: X
  - name: Google Tag Manager
  - name: Creatives
  - name: Creative styles
  - name: Media
  - name: Characters
  - name: Assets
  - name: Brands
  - name: Brain
  - name: Research
  - name: Boards
  - name: Artifacts
  - name: Audiences
  - name: Ad comments
  - name: Publications
  - name: Routines
  - name: Skills
  - name: To-dos
  - name: Audit
  - name: Credits
paths:
  /v1/workspaces/{workspaceId}/meta/custom-conversions/list:
    post:
      tags:
        - Meta
      summary: Custom-conversions list
      description: >-
        List the account's custom conversions — the named conversions built on a
        dataset's traffic, as opposed to Meta's standard pixel events or named
        custom pixel events. To verify raw event activity on a dataset, use
        `adside meta pixel-stats get`; an empty custom-conversion list does not
        mean the pixel has no events.


        Use this to find the ID to optimise an ad set towards: pass it as
        `promoted_object.custom_conversion_id` on create_ad_set_enhanced or
        update_ad_set. Many accounts never adopted Meta's standard event
        taxonomy and put all their real volume here, so a standard event that
        looks right can have fired zero times.


        In reporting and insights breakdowns the same conversion appears as
        `offsite_conversion.custom.<id>`.


        CLI: `adside meta custom-conversions list`
      operationId: meta.list_custom_conversions
      parameters:
        - name: workspaceId
          in: path
          required: true
          schema:
            type: string
            minLength: 1
      requestBody:
        required: false
        content:
          application/json:
            schema:
              $schema: https://json-schema.org/draft/2020-12/schema
              type: object
              properties:
                account_id:
                  description: Meta Ad Account ID (uses configured account if not provided)
                  type: string
                limit:
                  description: Maximum to return. An account may hold up to 100.
                  type: integer
                  exclusiveMinimum: 0
                  maximum: 100
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                $schema: https://json-schema.org/draft/2020-12/schema
      security:
        - userAccess: []
components:
  securitySchemes:
    userAccess:
      type: http
      scheme: bearer
      description: >-
        A personal API key (`adside_pat_…`) or a token from `adside login`.
        Either carries the permissions of the person it belongs to.

````

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