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

# Conversion-tracking audit

> Audit what a GTM container actually deploys for conversion tracking, reading the **published** version.

Covers the container half of the audit: base tags (a Google tag on all pages, and something storing the click id), conversion tags without a firing trigger, paused tags, malformed conversion ids, missing consent settings, and the Meta pixel (base code on all pages, conversion events firing on every page, missing sequencing or event id). It ends with the cross-checks to run next with `adside google-ads conversion-actions list` and `adside meta account-pixels get` — those need the ad accounts and cannot be answered from the container alone.

CLI: `adside google-tag-manager conversion-tracking audit`



## OpenAPI

````yaml /api-reference/openapi.yaml post /v1/workspaces/{workspaceId}/google-tag-manager/conversion-tracking/audit
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}/google-tag-manager/conversion-tracking/audit:
    post:
      tags:
        - Google Tag Manager
      summary: Conversion-tracking audit
      description: >-
        Audit what a GTM container actually deploys for conversion tracking,
        reading the **published** version.


        Covers the container half of the audit: base tags (a Google tag on all
        pages, and something storing the click id), conversion tags without a
        firing trigger, paused tags, malformed conversion ids, missing consent
        settings, and the Meta pixel (base code on all pages, conversion events
        firing on every page, missing sequencing or event id). It ends with the
        cross-checks to run next with `adside google-ads conversion-actions
        list` and `adside meta account-pixels get` — those need the ad accounts
        and cannot be answered from the container alone.


        CLI: `adside google-tag-manager conversion-tracking audit`
      operationId: google-tag-manager.audit_conversion_tracking
      parameters:
        - name: workspaceId
          in: path
          required: true
          schema:
            type: string
            minLength: 1
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $schema: https://json-schema.org/draft/2020-12/schema
              type: object
              properties:
                container_path:
                  type: string
                  description: >-
                    The container's `path`, from `adside google-tag-manager
                    containers list` — e.g.
                    "accounts/6000123/containers/12345678".
              required:
                - container_path
      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.