Google Ads

Google Ads is a connector: it links a MeDo app to one Google Ads account, so the app can list accessible customers, read performance reports, look up a campaign, and create reviewed paused drafts or pause and enable campaigns. Everything the app sees comes from the account you connected.

#What you can build

• A performance dashboard. List the owner's accessible customers and show customer, campaign, ad, or keyword metrics for an explicit date window.
• A manager account picker. List child accounts under a manager (MCC) and open reports on one client account — not on the manager itself.
• A campaign review page. Look up one campaign by ID or exact name, then pause or enable it after someone confirms.
• A launch workspace. Preview a paused Search campaign with a daily budget, ad group, ad copy, location, or conversion action, then create it only after confirm.

Google Ads fits when the app needs the owner's real advertising accounts. It is not an account-setup tool, a bidding engine, or a place for each visitor to log in with their own Ads account — see Limits.

#Build examples

Copy one of these into the prompt box. The first one is the smallest useful starting point.

Use @Google Ads to build a private website console that lists my accessible customers, then shows an account report for a selected customer and date range.

Use @Google Ads to build a private manager console that lists sub-accounts under my MCC and shows a campaign report for one client account.

Use @Google Ads to build a private campaign review page where I look up one campaign by ID or name and pause or enable it only after I confirm.

Use @Google Ads to build a private launch workspace that creates a paused Search campaign with a daily budget on my client account after I confirm the name and amount.

The wording matters: say who the tool is for and what it should do. "A private ads console for the account owner" produces a different app from "a page that lists campaigns".

#Prepare and connect

You need a Google account that can already open the Ads accounts the app should use. No API key, no Google Cloud project, and no billing setup are involved. MeDo cannot create a new Ads account, attach billing, or complete advertiser verification for you.

1. Open Skills & Connectors in the sidebar and search for Google Ads.
2. Open the Google Ads card and click Connect.
3. Sign in to the Google account and approve the access MeDo asks for. The flow may also ask for a Customer ID — use the manager (MCC) ID if you have one, otherwise the client account ID.
4. The button changes to Connected. That is the success state; you do not need to copy anything back into the app.

If you start building before connecting, MeDo notices and shows a Google Ads connection button under its reply. You can connect there instead. If no button appears, use the connector card described above.

#Use it in your app

• The app uses the owner's connected Google Ads account, not each visitor's own Ads account. Every visitor who reaches an account or report view sees the same connection. Keep those pages behind your app's own sign-in, and restrict them to the people who should have that access. A page titled "private" is not access control on its own.
• Reports and writes belong on a client account. A manager (MCC) ID is for listing children. Asking a manager ID for spend, clicks, or campaign changes fails. Copy the customer ID the connector returns; do not invent IDs.
• The accessible-customer list is not the full MCC tree. It shows accounts the Google user can open directly. To pick a child under a manager, list sub-accounts first.
• Reports need an explicit date window. Empty keyword or ad rows usually mean that account has no objects in range, not that the connection failed.
• Writes are confirmed first, and they are not retried. MeDo previews the customer, name, budget, status, ad copy, or location and waits for an explicit confirm. If the result is unknown, read the account again before creating another object. A retry can add a second campaign, budget, ad, or conversion action.
• New Search campaigns, ad groups, and responsive search ads start paused. Enabling a campaign is a separate confirmed step.
• App-owned notes stay in the app. Launch checklists, review status, and comments belong in your app's own tables, keyed to a real customer, campaign, budget, or ad-group ID. They are not Google Ads fields.

#Limits and troubleshooting

"Connection required" appears in the app. The Google Ads connection belongs to the app owner. Ask the owner to open the connector card and click Connect, then reload.

A report or write says the request was for a manager. Switch to a client customer ID from the sub-account list. Do not send reports or campaign changes to the MCC.

A write result is unknown. Do not click again. Look up the campaign or conversion by name or ID first.

Visitors can see ads data when they should not. The connection is shared. Add sign-in and server-side restrictions to the app; see Managing access & roles.

#Related

• Connector catalog — the other connectors and what they are for.
• Skills & Connectors — how Skills are called, priced, and limited.
• Managing sign-in & users — give an app its own accounts before exposing connected data.