> ## Documentation Index > Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt > Use this file to discover all available pages before exploring further. # Ads: scope and feature boundaries > What the Ads console covers — Meta click-to-chat campaigns only — what it deliberately does not cover (Google Ads, TikTok, and other ad networks), and a tile-by-tile map of the dashboard. # Ads: scope and feature boundaries The **Ads** console manages **Meta click-to-chat advertising only**. It connects one Meta Ad Account, creates campaigns whose destination is a WhatsApp, Messenger, or Instagram Direct conversation, returns business outcomes to Meta through the Conversions API (CAPI), and reports attribution against the entry ad. If you came here to run ads on Google, TikTok, or any other network, this is not the surface — read [Feature boundaries](#feature-boundaries) for what it deliberately excludes and where those channels stand. ## What the Ads console manages Every feature on the Ads page fits inside one loop, and the loop starts and ends with Meta: 1. **Connect** — authorize one Meta Ad Account per organization over OAuth. One account connects at a time; the console reports its billing currency so budgets, spend, and revenue render in that currency. 2. **Run** — create click-to-chat campaigns from the dashboard. The destination is always a conversation surface Meta owns: WhatsApp, Messenger, or Instagram Direct. New campaigns are created `PAUSED` so you review in Meta before spending. 3. **Convert** — post outcomes (`Lead`, `Purchase`, and other Meta standard events) through the Conversions API, matched with a `ctwa_clid` click id or a hashed phone/email. Match keys are SHA-256 hashed server-side; raw PII never leaves. 4. **Attribute** — read per-ad entry counts, first-touched contacts, attributed revenue, spend, and ROAS, first-touch across a 1–365 day window. If the question you are asking sits inside that loop, the console answers it. If it sits outside — a different network, a different destination, a different objective — it does not, and the next section says so plainly. For the full operational walk-through (OAuth steps, CAPI verification, troubleshooting), use the [Ads console guide](/guides/ads-console). This page exists to draw the boundary, not to repeat the guide. ## Feature boundaries **Channels (destinations):** in scope are WhatsApp, Messenger, and Instagram Direct — the conversation surfaces Meta click-to-chat ads support. Out of scope are every non-Meta surface: an SMS inbox capture flow, email capture, and voice are not ad destinations here, and the console does not pretend otherwise. * **Google Ads:** not supported. There is no Google account connector on the Ads page and no Google campaign creation or attribution loop on this surface. * **TikTok Ads:** not supported. No TikTok connector, no TikTok campaign creation, no TikTok attribution. * **Other networks (X, LinkedIn, Snapchat, etc.):** not supported. * **Meta Lead Ads (instant forms):** in scope, as a second *entry* path only. A lead-form submission lands in the same attribution view as a click-to-chat entry. This is ingestion of a Meta-native form, not a general lead-capture builder for other networks. * **Ad creation itself:** creating, pausing, resuming, and deleting a Meta click-to-chat campaign happens here. Media buying strategy, creative production, and bidding advice stay on Meta's side — the console manages the campaign loop and the convert-and-attribute half, not creative services. When a non-Meta network joins the console, it will ship as a separately documented connector — this page and the [Ads console guide](/guides/ads-console) will be updated the day it lands, and it will be announced on the changelog. ## Dashboard tiles map The Ads page is arranged as a set of tiles, top to bottom. Each tile answers one question: | Tile | What it answers | | --------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Connect card** | Is an account connected? Names the connected Meta Ad Account id on success, or offers **Connect Ad Account** via OAuth, with a typed-phrase **Disconnect** once linked. A failed connection-status read renders an error card with a retry path. | | **Ad Campaigns** | Is Meta delivering? Lists campaigns with name, status, destination, and per-row impressions, clicks, and conversations; **Create campaign** launches a new click-to-chat campaign (`PAUSED` at creation); **View Insights** opens the per-campaign funnel (impressions, reach, clicks, CTR, spend, cost per click, conversations) in the account currency. | | **Audiences** | Who are you targeting? Builds and syncs Meta Custom Audiences from your own segments, for targeting and suppression. | | **Conversions > Configuration** | Where do outcomes go? Holds the Meta Dataset ID that CAPI posts to. | | **Conversions > Test Conversion Event** | Does Meta accept the payload? Sends a test conversion and logs only Meta-confirmed receipts in **Recent Test Events**, with Meta's trace id when one comes back. | | **Conversions > Post Conversion** | What happened? Posts a real business outcome — Lead, Purchase, or any Meta standard event — with a `ctwa_clid` or a hashed phone/email match key, plus an optional value and currency. | | **Lead Ads** | Any instant-form entries? Ingests Meta lead-ad form submissions into the same attribution view. | | **Attribution** | Which ads earned? Reads per-ad entry counts, first-touched contacts, attributed revenue, spend, and ROAS over your chosen window — server-side, same numbers as the API. | Permissions map onto the tiles the way you would expect: every role reads connection status, campaign lists, and audiences; the writes — connect/disconnect, campaign create/pause/resume/delete, audience create/sync/delete, conversions configuration and posting — need an owner or admin. ## FAQ **Why only Meta?** Because click-to-chat ads entry points — WhatsApp, Messenger, and Instagram Direct — are surfaces Meta owns, and the attribution loop (the referral stamp on the inbound message, the closed-loop CAPI reporting) is Meta-native. Other networks do not expose the same deterministic click id (`ctwa_clid`) join, so a generic ads surface would ship weaker attribution than this one. Rather than fold that weaker attribution in, the console scopes to the network where the loop closes cleanly. **Where are Google Ads and TikTok Ads?** Not in this console, and not planned as a silent addition — any new network ships as its own connector with its own connector card and documentation, and it will be announced on the changelog. **Does the console manage my entire Meta Ads account?** No. It manages the click-to-chat campaign loop: campaign creation, audiences, conversions, and attribution. Full account management (ad sets beyond the click-to-chat shape the console creates, creative tooling, billing) stays in Meta Ads Manager. **Can I still serve customers on SMS/voice if my acquisition runs on Meta ads?** Yes — channel choice for your ongoing conversations is independent of where the ad ran. The click-to-chat destination is fixed to Meta's conversation surfaces during the acquisition step; once a contact exists, you can reach them on any channel your organization has enabled and they have consented to. **Can I connect more than one Meta ad account?** One ad account connects per organization. To switch accounts, disconnect (a typed-phrase confirmation, since it stops data flow) and re-run OAuth against the right account. ## See also * [Ads console guide](/guides/ads-console) — the full operational walk-through this page deliberately does not duplicate * [Meta Ads activation guide](/guides/ads-activation) — the segment-to-attribution loop end to end * [Ads attribution and lead ingestion (concepts)](/concepts/ads-attribution-lead-ingestion) — the attribution model * [Ads API reference](/api-reference/ads) — every endpoint behind the tiles