> ## Documentation Index > Fetch the complete documentation index at: https://docs.fetchski-attract.com/llms.txt > Use this file to discover all available pages before exploring further. # Conversions the page can fire (public) > Anonymous and read-only: what the site’s own pages load to fire conversions in the browser. Each enabled Conversion with a browser trigger, compiled, with only its rows sent from the page and its page-view triggers resolved against `path` to a yes/no. No names, no server-only IDs, and never the site’s page list. Integrations should use `GET /conversion/definitions` instead. ## OpenAPI ````yaml /api-reference/openapi.yaml get /conversion/active openapi: 3.1.0 info: title: Fetchski Attract CMS API description: >- Auto-generated OpenAPI spec for this Fetchski site instance. Authenticate machine-to-machine requests with an API key by sending the header `Authorization: ApiKey `. Keys are issued in the CMS (API Keys) and carry scopes that limit them to specific actions. Each key also has its own security policy, chosen when it is created: a signing mode (token only, signed writes, or every request signed with the key’s signing secret via `X-Fetchski-Timestamp` + `X-Fetchski-Signature`), an optional network allowlist, and reads/writes-per-minute limits (429 with `Retry-After` over them). Some routes require a signature from every key — see each route. version: 1.0.0 servers: - url: https://{host}/api/v1 description: 'Your site: set `host` to its host name.' variables: host: default: acme.example security: [] tags: - name: Authentication description: >- Sign in as a person to get a bearer token or a session cookie. Integrations use an API key instead: send `Authorization: ApiKey `. - name: SDK Packages description: >- The site’s own npm registry and Composer repository for the Attract SDKs, so an app installs them with one of the site’s API keys. Point npm, pnpm, Bun or Composer at them; the SDKs never call them. - name: Pages description: 'The page tree: each page’s content, place and URL.' - name: Global Content description: Site-wide content and settings every page shares. - name: Redirects description: Old URLs and where they now send visitors. - name: Internationalization description: The site’s locales. - name: Languages description: >- The site’s languages: the main language’s name and every further language’s name, code and Public switch. A save applies at once: a new language gets its home page and its own addresses (/fr/…), and its pages are then translated with each type’s localize routes. - name: Page Templates description: >- The site’s whole-page starting arrangements. They are not pages of the site (the Pages list leaves them out for API keys): read one, then make a page from it with Pages → create and `_copyingId` (`copyingId` in the SDKs). - name: Blog Posts description: The blog’s posts, and importing them from Markdown or MDX. - name: Blog Categories description: The categories posts are filed under. - name: Authors description: The people posts are credited to. - name: Team Members description: The people the Team section shows. - name: Testimonials description: Quotes from customers. - name: FAQ Items description: Questions and their answers. - name: FAQ Categories description: The groups questions are sorted into. - name: Google Reviews description: Reviews from the business’s Google profile, synced on a schedule. - name: Instagram Posts description: Posts from the connected Instagram account, synced on a schedule. - name: Service Areas description: The places the business serves, for the service map. - name: Cookies description: The cookies the consent banner declares. - name: Media description: The Images and Files libraries, and their tags. - name: Videos description: The Videos library. - name: Image Folders description: The folders that organize the Images library. - name: File Folders description: The folders that organize the Files library. - name: Video Folders description: The folders that organize the Videos library. - name: Photo Albums description: Hand-picked, ordered sets of photos for galleries. - name: Photo Feeds description: >- Feeds that collect photos from a connected photo source into the Images library on a schedule. - name: Attachments description: Uploading files and cropping images. - name: Fetchski Media description: >- Read-only discovery over the Images and Videos libraries: find what to reference in an MDX blog import, or which file to use, with its URLs. - name: Forms description: The site’s forms and their fields. - name: Form Submissions description: >- What visitors sent through the site’s forms. Submissions hold personal details: give a key `forms:read` only where it is needed. - name: Conversion Events description: >- The conversion event log — one record per conversion, with its attribution and consent snapshot and its delivery to each ad platform. Read it incrementally, post facts from other systems (a reservation purchase, a lead outcome), and adjust them (refunds, cancellations). One event ID travels everywhere as the platforms’ de-duplication key. - name: Visitor Attribution description: >- Per-visitor attribution on this site: first touch, last ad or campaign touch, and the ad platforms’ browser IDs. The join other systems use to attach a purchase to the marketing-site journey that led to it. - name: Ads Metrics description: >- Aggregates for dashboards: ad-click landings and conversions, by day, platform, campaign and more. - name: Conversions description: >- Conversion definitions — the visitor actions (a lead, a call click, a booking, a purchase) this site reports to the ad platforms, each with a row per platform. Managed by administrators in the CMS. - name: Webhooks description: >- Push notifications of form submissions and conversion-event changes to the site’s Webhook Destinations — signed with each destination’s own secret, retried for a day, at-least-once. Set destinations up in the CMS (Webhook Destinations, for people granted “Manage webhook destinations”): URL, events, optional filters and custom headers, and the signing secret shown once. - name: Request Log description: >- The page views the site captured (Connections → Tracking → Request log), and the query parameters on them: campaign tags and ad click IDs. paths: /conversion/active: get: tags: - Conversions summary: Conversions the page can fire (public) description: >- Anonymous and read-only: what the site’s own pages load to fire conversions in the browser. Each enabled Conversion with a browser trigger, compiled, with only its rows sent from the page and its page-view triggers resolved against `path` to a yes/no. No names, no server-only IDs, and never the site’s page list. Integrations should use `GET /conversion/definitions` instead. operationId: listActiveConversions parameters: - name: path in: query required: false description: The page path the conversions are for. Default `/`. schema: type: string maxLength: 2048 default: / example: /thank-you responses: '200': description: The page’s conversions. content: application/json: schema: $ref: '#/components/schemas/ListActiveConversionsResponse' example: conversions: - id: ckq1w2e3r4t5y6u7i8o9p0 key: phone-call counting: once value: null currency: USD sendUserData: true destinations: - google-ads - ga4 platforms: google-ads: sendTo: AW-123456789/AbC-D_efG ga4: event: contact triggers: forms: [] links: - tel:* outbound: false downloads: [] chat: [] pageView: false security: - {} x-codeSamples: - lang: typescript label: TypeScript source: >- import { createSiteClient } from '@fetchski/attract-cms-sdk'; const site = createSiteClient(); const listActiveConversions = await site.conversions().listActiveConversions(); - lang: php label: Laravel source: >- use Fetchski\AttractCmsLaravel\Facades\Attract; $listActiveConversions = Attract::conversions()->listActiveConversions(); components: schemas: ListActiveConversionsResponse: type: object required: - conversions properties: conversions: type: array items: $ref: '#/components/schemas/ListActiveConversionsResponseConversionsItem' ListActiveConversionsResponseConversionsItem: type: object required: - id - key - counting - value - currency - sendUserData - destinations - platforms - triggers properties: id: type: string key: type: string description: >- The Conversion’s key, sent to Google Analytics and Tag Manager as `conversion_key`. counting: type: string enum: - once - every value: type: - number - 'null' currency: type: string sendUserData: type: boolean destinations: type: array description: The platforms the page sends this Conversion to. items: type: string enum: - google-ads - ga4 - gtm - meta - tiktok platforms: type: object description: >- Per platform in `destinations`, what its tag needs: the event name (GA4, GTM, Meta, TikTok), or the Google Ads `send_to`. additionalProperties: type: object properties: event: type: string example: generate_lead sendTo: type: string example: AW-123456789/AbC-D_efG conversionId: type: string example: '12345678' triggers: type: object required: - forms - links - outbound - downloads - chat - pageView properties: forms: type: array items: type: string links: type: array items: type: string description: >- Link patterns: a scheme (`tel:*`, `tel:+15550100100`), a full address (may end in `*`), a `/path` of this site, or a domain. outbound: type: boolean description: Fires on any link that leaves the site. downloads: type: array items: type: string description: File extensions whose links fire it, e.g. `pdf`. chat: type: array items: type: string enum: - chat-started - lead-captured pageView: type: boolean description: Whether viewing `path` fires it. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.