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

# GetPageTrackingAPI mirrors the erdo_get_page_tracking MCP tool: which analytics
destinations the


> caller org's published pages send visitor data to, the companion to /v1/page-analytics/query. It reports organization configuration, not per-page coverage (meta\_pixel and linkedin\_insight load only when the page's declared artifact\_kind is landing\_page; legacy undeclared pages may qualify through an eligible capture binding). It returns only public client-side identifiers already in page JS; the provider's internal project id is stripped. It is read-only because destinations are Erdo-provisioned, never caller-chosen, and the first-party beacon is not listed, so an empty list means no vendor tracking, not no recording.




## OpenAPI

````yaml /api/openapi.json get /v1/page-tracking
openapi: 3.0.0
info:
  title: Erdo API
  description: >-
    Erdo's REST API: query and write datasets, run agents, manage threads,
    integrations, pages, evals, workstreams, experiments, and bounded outreach.
    Authenticate with a Bearer API key (erdo_api_...) or scoped token
    (erdo_token_...).
  version: '2026-11-21'
servers:
  - url: https://api.erdo.ai
    description: Production
security:
  - bearerAuth: []
paths:
  /v1/page-tracking:
    get:
      summary: >
        GetPageTrackingAPI mirrors the erdo_get_page_tracking MCP tool: which
        analytics

        destinations the
      description: >
        caller org's published pages send visitor data to, the companion to
        /v1/page-analytics/query. It reports organization configuration, not
        per-page coverage (meta\_pixel and linkedin\_insight load only when the
        page's declared artifact\_kind is landing\_page; legacy undeclared pages
        may qualify through an eligible capture binding). It returns only public
        client-side identifiers already in page JS; the provider's internal
        project id is stripped. It is read-only because destinations are
        Erdo-provisioned, never caller-chosen, and the first-party beacon is not
        listed, so an empty list means no vendor tracking, not no recording.
      operationId: GET:mcp.GetPageTrackingAPI
      responses:
        '200':
          content:
            application/json:
              schema:
                properties:
                  consent:
                    description: >
                      banner. With "required", low or absent event volume can be
                      a consent gate rather than absent traffic.
                    title: >
                      Consent is "implied" or "required" — whether recording
                      waits on a consent
                    type: string
                  destinations:
                    description: >
                      enabled or not — the third-party analytics a published
                      page is wired to send to. Erdo's own first-party
                      page-events beacon is deliberately not among them: it is
                      provisioned per page on first render rather than stored on
                      the org, so an empty list here means no vendor tracking,
                      NOT that nothing is recording. The beacon is what
                      page-event queries read, and it runs independently.
                    items:
                      $ref: '#/components/schemas/mcp.PageTrackingDestinationInfo'
                    title: >
                      Destinations is every VENDOR destination configured on the
                      organization,
                    type: array
                  mask_inputs:
                    description: >
                      so a consumer building a replay-backed surface needs to
                      know whether the recordings it is about to show were
                      masked at capture time.
                    title: >
                      MaskInputs masks form-input values in session replay. Lead
                      forms carry PII,
                    type: boolean
                type: object
          description: Success response
        default:
          $ref: '#/components/responses/APIError'
components:
  schemas:
    mcp.PageTrackingDestinationInfo:
      description: >
        This is a curated projection, not the stored TrackingDestination: the
        stored struct also carries ProjectID, the provider's INTERNAL numeric
        project id (PostHog), which exists so the backend can read data back
        through the management API. It is not a client-side identifier, it never
        appears in page JS, and it must never cross /v1.
      properties:
        conversion_id:
          description: >
            lead capture. It is absent when the Insight Tag is configured for
            retargeting only.
          title: >
            ConversionID is the optional LinkedIn conversion ID fired for a
            successful
          type: string
        enabled:
          description: >
            org configuration, not per-page coverage: session\_analytics and
            google\_analytics load on every published page, while meta\_pixel
            and linkedin\_insight load only when the page's declared
            artifact\_kind is landing\_page (legacy undeclared pages may qualify
            through an eligible capture binding). A configured but disabled
            destination is reported rather than hidden: "configured and switched
            off" and "never configured" are different problems with different
            fixes, and collapsing them is how a consumer draws the wrong
            conclusion.
          title: >
            Enabled is whether the organization has this destination switched
            on. It is
          type: boolean
        host:
          description: >
            empty means the provider default. It travels with PublicID because
            the id alone does not identify an instance — the same \`phc\_…\` key
            means different projects on different PostHog regions — so dropping
            it would make PublicID less verifiable without making anything more
            private.
          title: >
            Host is the ingest host events are sent to (e.g.
            https://us.i.posthog.com);
          type: string
        kind:
          description: >
            "session\_analytics" (heatmaps + replay), "google\_analytics",
            "meta\_pixel", "linkedin\_insight". Provider-agnostic — this is the
            field to branch on.
          title: |
            Kind is the Erdo-named capability the destination implements:
          type: string
        provider:
          description: >
            "google" for google\_analytics, "meta" for meta\_pixel, "linkedin"
            for linkedin\_insight) — an implementation detail, reported so an
            operator can go look in the right console.
          title: >
            Provider is the vendor behind the kind ("posthog" for
            session_analytics,
          type: string
        public_id:
          description: >
            by design — a PostHog \`phc\_…\` project key, a GA4 \`G-…\`
            measurement id, a numeric Meta pixel id, or a numeric LinkedIn
            partner id. Included because "is a pixel enabled" is only half the
            question: a pixel can be enabled and still belong to an account the
            org's campaigns cannot target (a real incident — a pixel provisioned
            in an Erdo Business Manager was invisible to every campaign meant to
            use it). The id is what lets an operator match what fires on the
            page against what the ad account holds. It discloses nothing a page
            visitor cannot already read.
          title: >
            PublicID is the client-side identifier already embedded in published
            page JS
          type: string
      title: >
        PageTrackingDestinationInfo is one analytics destination as seen from
        /v1.
      type: object
  responses:
    APIError:
      content:
        application/json:
          schema:
            externalDocs:
              url: https://pkg.go.dev/encore.dev/beta/errs#Error
            properties:
              code:
                description: Error code
                example: not_found
                externalDocs:
                  url: https://pkg.go.dev/encore.dev/beta/errs#ErrCode
                type: string
              details:
                description: Error details
                type: object
              message:
                description: Error message
                type: string
            title: APIError
            type: object
      description: Error response
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: An Erdo API key (erdo_api_...) or scoped token (erdo_token_...).

````

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