@wix/agent-skills 1.19.1 → 1.20.0

package/skills/wix-manage/references/events/create-wix-event.md

@@ -56,6 +56,32 @@ curl -X POST 'https://www.wixapis.com/events/v3/events' \
 `title`, `location`, `dateAndTimeSettings` and `registration.initialType` are required. The event
 is created published (`status: "UPCOMING"`).
 
+**What comes back** — the created event under `event`; the id you need for every follow-up call is
+`event.id`:
+
+```json
+{
+  "event": {
+    "id": "<EVENT_ID>",
+    "title": "Summer Gala",
+    "slug": "summer-gala",
+    "status": "UPCOMING",
+    "location": { "name": "Grand Hall", "type": "VENUE", "locationTbd": false },
+    "dateAndTimeSettings": {
+      "startDate": "2026-09-15T19:00:00Z", "endDate": "2026-09-15T22:00:00Z",
+      "timeZoneId": "America/New_York", "recurrenceStatus": "ONE_TIME"
+    },
+    "createdDate": "...", "updatedDate": "..."
+  }
+}
+```
+
+Update, cancel, publish and clone return the same `{ "event": { ... } }`; delete returns
+`{ "eventId": "..." }`. Some fields are returned only when the request's `fields` array asks for
+them: `"DETAILS"` adds `shortDescription`, `"TEXTS"` adds `description`, `"REGISTRATION"` adds
+`registration` (including `rsvp.limit`), `"URLS"` adds `eventPageUrl`. Without `fields`, read the
+result from the top-level fields above and do not treat a missing `registration` as an error.
+
 > **Do not add `"draft": true` unless the user asked for a draft.** Draft events require the
 > `WIX_EVENTS.READ_DRAFT_EVENTS` permission, and without it every follow-up call fails `403` —
 > adding ticket definitions, querying the event, fetching it by slug, even publishing it. The
@@ -154,6 +180,26 @@ curl -X POST 'https://www.wixapis.com/events/v3/ticket-definitions' \
 | Free | `{ "fixedPrice": { "value": "0", "currency": "USD" } }` |
 | Donation, with a minimum | `{ "guestPrice": { "value": "5.00", "currency": "USD" } }` |
 
+The response is the definition under `ticketDefinition`:
+
+```json
+{
+  "ticketDefinition": {
+    "id": "<TICKET_DEFINITION_ID>",
+    "eventId": "<EVENT_ID>",
+    "revision": "1",
+    "name": "General Admission",
+    "limited": true, "initialLimit": 100, "actualLimit": 100,
+    "pricingMethod": { "fixedPrice": { "value": "25.00", "currency": "USD" } },
+    "feeType": "FEE_ADDED_AT_CHECKOUT",
+    "saleStatus": "SALE_STARTED"
+  }
+}
+```
+
+Keep `revision` — `PATCH /events/v3/ticket-definitions/{id}` requires the current value, and it
+increments on every update.
+
 - **`feeType` is required** — `FEE_ADDED_AT_CHECKOUT` or `FEE_INCLUDED`.
 - **`value` is a string.** `"value": 10` fails `400 Unexpected value for field value`.
 - **No writable `free` flag** — `pricingMethod.free` is read-only; a free ticket is a `fixedPrice`

package/skills/wix-manage/references/events/manage-wix-events.md

@@ -1,6 +1,6 @@
 ---
 name: "Manage Wix Events — Publishing, Cancelling, Cloning and Counting"
-description: "Operates on events that already exist with the Wix Events V3 API — publishing a draft, cancelling, deleting, cloning, updating an event's date or details, and counting events. Use when the user wants to publish or cancel an event, duplicate one, move an event's date, or count their events. Creating an event, its tickets or a recurring series is a separate recipe."
+description: "Operates on events that already exist with the Wix Events V3 API — finding an event by title, publishing a draft, cancelling, deleting (one or by filter), cloning, updating an event's date or details, and counting events. Use when the user wants to find, publish or cancel an event, duplicate one, move an event's date, delete events in bulk, or count their events. Creating an event, its tickets or a recurring series is a separate recipe."
 ---
 
 # Manage Wix Events — Publishing, Cancelling, Cloning and Counting
@@ -28,6 +28,36 @@ curl -X POST 'https://www.wixapis.com/apps-installer-service/v1/app-instance/ins
 `appDefId` nests under `appInstance`, not at the root — at the root it fails with
 `400 appInstance must not be empty`. See [Install Wix Apps](../app-installation/install-wix-apps.md).
 
+## Find an event
+
+Every action below takes an `eventId`. When the user names the event instead, look it up with
+`POST /events/v3/events/query` — `title` supports `$eq` and, for several names at once, `$in`; there is
+no contains match:
+
+```bash
+curl -X POST 'https://www.wixapis.com/events/v3/events/query' \
+  -H 'Content-Type: application/json' \
+  -H 'Authorization: <AUTH>' \
+  --data-binary '{
+    "query": {
+      "filter": { "title": { "$eq": "Open House" } },
+      "paging": { "limit": 100 }
+    },
+    "fields": ["DETAILS"],
+    "includeDrafts": false
+  }'
+```
+
+`filter` and `paging` are siblings under `query`; `paging` nested inside `filter` fails `400`. Matches
+come back in `events[]` with the id at `events[].id`, and `pagingMetadata.total` is the count.
+
+> **Keep `includeDrafts: false` unless the user is asking about draft events.** Setting it to `true`
+> needs `WIX_EVENTS.READ_DRAFT_EVENTS`, and a caller without it gets
+> `403 Requires WIX_EVENTS.READ_DRAFT_EVENTS permission` rather than more results — so do not flip
+> it as a precaution on an ordinary lookup, and do not probe for it and fall back. If the user does
+> want drafts and the call returns that `403`, say draft events are not readable from this
+> connection instead of answering from published events alone.
+
 ## Publish, cancel and delete
 
 | Action | Call | Resulting `status` |
@@ -35,10 +65,27 @@ curl -X POST 'https://www.wixapis.com/apps-installer-service/v1/app-instance/ins
 | Publish a draft | `POST /events/v3/events/{eventId}/publish` | `UPCOMING` |
 | Cancel | `POST /events/v3/events/{eventId}/cancel` | `CANCELED` |
 | Delete | `DELETE /events/v3/events/{eventId}` | — |
+| Delete several | `POST /events/v3/bulk/events/delete-by-filter` | — |
 
 Publish and cancel take an empty body. Publishing is irreversible — a published event cannot
 return to `DRAFT`. Cancelling closes registration but keeps the event; deleting removes it.
 
+Publish, cancel, clone and update all return `{ "event": { "id", "title", "slug", "status", ... } }`
+— the same event object [Create an Event](create-wix-event.md#create-the-event) shows in full.
+Delete returns `{ "eventId": "..." }` and the bulk delete below returns `{}`.
+
+To delete a set of events in one call, `POST /events/v3/bulk/events/delete-by-filter`:
+
+```json
+{ "filter": { "filter": { "id": { "$in": ["<EVENT_ID>", "<EVENT_ID>"] } } } }
+```
+
+The request's one field, `filter`, takes a whole query-shaped object — the same object Query Events
+takes under `query`, with the conditions under its own `filter` key — not a bare condition map. That
+is why the key appears twice: `filter.filter.<field>`. A single level,
+`{ "filter": { "id": { "$in": [...] } } }`, is not the documented shape. Resolve the ids with the
+query above first; one `DELETE` per event also works but costs a call each.
+
 > **Draft events need the `WIX_EVENTS.READ_DRAFT_EVENTS` permission.** Without it, publishing a
 > draft fails `403` — as does querying it, fetching it by slug, or adding ticket definitions to
 > it. If you hit that `403`, the event was still created; the way forward is to create events
@@ -104,6 +151,9 @@ even when the site has events, so it is not the way to answer "how many events d
 - **An invalid enum value reports as a missing one** — a value outside an enum returns
   `<field> value is required` rather than "invalid value". If a field you *did* send is reported
   as required, suspect the value, not its presence.
+- **`includeDrafts` stays `false` unless the request is about drafts** — see
+  [Find an event](#find-an-event). The `WIX_EVENTS.READ_DRAFT_EVENTS` note on the Query Events
+  reference describes the permission; it does not mean the caller has it.
 - Dates are always ISO-8601 strings, never `{seconds, nanos}`, and `timeZoneId` is required
   whenever `dateAndTimeSettings` is sent — see [Create an Event](create-wix-event.md).
 

package/skills/wix-manage/references/google-ads/manage-campaign-lifecycle.md

@@ -1,10 +1,10 @@
 ---
 name: "Manage Campaign Lifecycle"
-description: "Manages existing Google Ads campaigns on a Wix site: list/get, launch (first activation) vs resume (reactivate after a pause), pause a running campaign — optionally with a scheduled auto-resume date — update name/budget/targeting, change the daily budget, delete permanently, and read status history / change log. Use when the user wants to 'pause my Google ad', 'resume my campaign', 'stop the campaign', 'change my daily budget', 'rename the campaign', 'delete this campaign', 'list my Google Ads campaigns', or 'why did my campaign status change'. Requires an existing Google Ads account and campaign. REST base https://www.wixapis.com/google-ads/v1."
+description: "Manages existing Google Ads campaigns on a Wix site: list/get, launch (first activation) vs resume (reactivate after a pause), pause a running campaign — optionally with a scheduled auto-resume date — update name/budget/targeting, change the daily budget, delete permanently, and read status history / change log. Use when the user wants to 'pause my Google ad', 'resume my campaign', 'stop the campaign', 'change my daily budget', 'rename the campaign', 'delete this campaign', 'list my Google Ads campaigns', or 'why did my campaign status change'. Requires an existing Google Ads account and campaign. REST base https://www.wixapis.com/_serverless/pa-google/v1."
 ---
 # RECIPE: Manage Campaign Lifecycle
 
-Operate on campaigns that already exist. Base URL: `https://www.wixapis.com/google-ads/v1`; `<AUTH>` = `Authorization` header, and body calls also need `Content-Type: application/json`.
+Operate on campaigns that already exist. Base URL: `https://www.wixapis.com/_serverless/pa-google/v1`; `<AUTH>` = `Authorization` header, and body calls also need `Content-Type: application/json`.
 
 **Answer directly.** When the user asks *how* to do something, give the endpoint, an example request, and the key behavior right away — use `{campaignId}` as a placeholder rather than asking which campaign. Only pause to confirm when you are about to **execute** a launch, resume, or delete on the user's behalf (those spend money or are irreversible); explaining how never requires confirmation.
 
@@ -21,14 +21,14 @@ Operate on campaigns that already exist. Base URL: `https://www.wixapis.com/goog
 
 ```bash
 # Launch (first activation)  → status LIVE
-curl -X POST 'https://www.wixapis.com/google-ads/v1/campaigns/{campaignId}/launch' -H 'Authorization: <AUTH>' -H 'Content-Type: application/json' -d '{}'
+curl -X POST 'https://www.wixapis.com/_serverless/pa-google/v1/campaigns/{campaignId}/launch' -H 'Authorization: <AUTH>' -H 'Content-Type: application/json' -d '{}'
 
 # Pause a running campaign (settings + data preserved) → status PAUSED
-curl -X POST 'https://www.wixapis.com/google-ads/v1/campaigns/{campaignId}/pause' -H 'Authorization: <AUTH>' -H 'Content-Type: application/json' \
+curl -X POST 'https://www.wixapis.com/_serverless/pa-google/v1/campaigns/{campaignId}/pause' -H 'Authorization: <AUTH>' -H 'Content-Type: application/json' \
   -d '{ "scheduledResumeDate": "2024-04-15T08:00:00.000Z" }'
 
 # Resume a paused campaign → status LIVE
-curl -X POST 'https://www.wixapis.com/google-ads/v1/campaigns/{campaignId}/resume' -H 'Authorization: <AUTH>' -H 'Content-Type: application/json' -d '{}'
+curl -X POST 'https://www.wixapis.com/_serverless/pa-google/v1/campaigns/{campaignId}/resume' -H 'Authorization: <AUTH>' -H 'Content-Type: application/json' -d '{}'
 ```
 
 - **Pause** stops delivery immediately without losing configuration. Optional body fields: `scheduledResumeDate` (ISO 8601 — the campaign **auto-resumes** at that time; pass `null` to cancel a scheduled resume), `resumeReminderDate` (dashboard reminder), `turnAutoRenewOff`. Send `{}` to pause with no auto-resume. To temporarily stop a campaign, **pause it — never delete**.
@@ -39,7 +39,7 @@ curl -X POST 'https://www.wixapis.com/google-ads/v1/campaigns/{campaignId}/resum
 `PATCH /v1/campaigns/{id}` — send only the fields you're changing, plus the required `id` and `accountId`. Budget is in **micros** (`20000000` = $20.00/day).
 
 ```bash
-curl -X PATCH 'https://www.wixapis.com/google-ads/v1/campaigns/{campaignId}' -H 'Authorization: <AUTH>' -H 'Content-Type: application/json' \
+curl -X PATCH 'https://www.wixapis.com/_serverless/pa-google/v1/campaigns/{campaignId}' -H 'Authorization: <AUTH>' -H 'Content-Type: application/json' \
   -d '{ "campaign": { "id": "...", "accountId": "...", "name": "New name", "budget": { "amountMicros": "20000000" } } }'
 ```
 

package/skills/wix-manage/references/google-ads/manage-campaign-success-guide.md

@@ -1,39 +1,45 @@
 ---
 name: "Manage a Campaign Success Guide"
-description: "Retrieves and manages the campaign success guide for an existing Wix Google Ads Performance Max Leads campaign. Offer it after creating a supported campaign, even while it is learning or has no metrics; that proactive offer requires approval before retrieval. A direct request to improve a campaign, see what to fix next, or show the guide is already approval to retrieve it. Also use when a user reports completing or wants to reopen a guide item. Treat a clear completion report as an actionable update request even when phrased as a statement. Covers campaign selection, prioritized guide retrieval, and suggestion status updates without redundant confirmation. REST base https://www.wixapis.com/pa-platform/suggestions/v1."
+description: "Campaign Success Guide for existing Wix Google Ads Performance Max Leads campaigns. Use after creating a supported campaign, even while it is learning or has no metrics, and whenever users ask how to improve a campaign, what to fix next, to view the guide, or to mark or reopen a recommendation. Covers campaign and site selection; prioritized actionable recommendations; deduplicated, destination-specific Editor and Google Ads navigation; offers to perform supported work after approval; Merchant Center and Business Profile connection follow-ups; and suggestion-status tracking."
 ---
 # RECIPE: Manage a Campaign Success Guide
 
-A campaign success guide is a prioritized list of improvements for an **existing** Google Ads `PERFORMANCE_MAX_LEADS` campaign. Offer it as a useful next step after [creating a Performance Max campaign](create-performance-max-campaign.md). Once Create Campaign returns the campaign ID, ask whether the user wants to retrieve the guide; call the API only after they approve. There is no need to wait for the campaign to leave `LEARNING` or generate performance metrics because the guide analyzes the landing page, campaign configuration, and relevant site connections rather than depending on campaign performance data.
-
-Also use this recipe for requests such as "How can I improve my campaign?", "What should I fix next?", "Show my campaign success guide", "I made the call-to-action button clearer as the success guide recommended", "Mark this recommendation complete", or "Reopen that guide item."
+A campaign success guide is a prioritized list of improvements for an **existing** Google Ads `PERFORMANCE_MAX_LEADS` campaign. Offer it as a useful next step after [creating a Performance Max campaign](create-performance-max-campaign.md). Once Create Campaign returns the campaign ID, ask whether the user wants to retrieve the guide; call the API only after they approve. The guide does not use campaign performance metrics. It evaluates landing-page content, campaign configuration, and Wix site connections, so `LEARNING` status and an empty analytics history do not block it.
 
 A direct request to improve a campaign, see what to fix next, or show its success guide is itself approval to retrieve the guide once the campaign is identified. Do not ask whether the user wants the guide after they have already made one of those requests. Separate approval is needed only when you proactively offer the guide after campaign creation.
 
-This differs from [Get AI Campaign Suggestions](get-campaign-suggestions.md), which generates keywords, budgets, locations, copy, images, and other inputs used while **building** a campaign. Do not route pre-campaign keyword, budget, creative, or targeting generation here.
+Treat a broad request such as "How can I improve my Google Ads campaign?" as a Campaign Success Guide request for an existing campaign. Route here before offering generic optimization advice, querying analytics, or generating the pre-campaign inputs covered by Get AI Campaign Suggestions. If the conversation does not identify a Wix site or campaign, explain that you will use the guide and ask one focused question that resolves the missing identity; do not probe site-scoped APIs first.
 
-Base URL: `https://www.wixapis.com/pa-platform/suggestions/v1`. `<AUTH>` is the `Authorization` header; body calls also need `Content-Type: application/json`.
+This differs from [Get AI Campaign Suggestions](get-campaign-suggestions.md), which generates keywords, budgets, locations, copy, images, and other inputs used while **building** a campaign. Do not route pre-campaign keyword, budget, creative, or targeting generation here.
 
 ## Resolve the campaign
 
-The guide endpoints require a campaign UUID, but users often provide only a campaign name or say "my campaign."
+The guide endpoints require a campaign UUID, but users often provide only a campaign name or say "my campaign." Google Ads calls operate on the current Wix site from the call context; the site is not a request-body field. Use an already-selected site context without asking the user to repeat it. If there is no unambiguous current site, ask which site to use instead of probing several sites. Follow the rest of this resolution flow only when retrieving or updating a guide. If the conversation already contains the guide recommendations and the user only wants them presented, do not block the action plan on campaign identity; resolve only the site context needed for relevant navigation.
 
-1. If the user provides a campaign UUID, use it.
-2. Otherwise follow [Manage Campaign Lifecycle](manage-campaign-lifecycle.md) and call:
+Site listing is for resolving navigation metadata only. Never use account-wide site listing to hunt for a campaign before retrieving or updating a guide. A current-site ID in the available context counts as an unambiguous selected site even when the user's prompt does not repeat its name. If no current-site ID is available, ask which site to use.
+
+1. If the campaign UUID is known, use it in the current site context.
+2. Otherwise, list campaigns once for the current site using the Campaign API's public serverless route:
 
    ```bash
-   curl -X GET 'https://www.wixapis.com/google-ads/v1/campaigns' \
+   curl -X GET 'https://www.wixapis.com/_serverless/pa-google/v1/campaigns' \
      -H 'Authorization: <AUTH>'
    ```
 
+   Use this full URL exactly once. The `/_serverless/pa-google` prefix is part of the public endpoint. Do not retry with a relative URL or another service prefix, or probe another site when the documented call returns an error.
+
    Read each campaign's `id`, `name`, `campaignType`, and `status`.
-3. Select a campaign only when one result clearly matches the user's wording. If none or multiple plausibly match, show concise choices and ask the user to choose; never guess.
+3. Select a campaign only when one result clearly matches the user's wording. If several campaigns on that site plausibly match, show concise campaign choices and ask the user to choose; never guess.
 4. Continue only for `campaignType: "PERFORMANCE_MAX_LEADS"`. If the selected campaign has another type, explain that campaign success guides currently support Google Ads Performance Max Leads campaigns only. For a supported campaign, do not gate guide retrieval on `status` or query analytics first: `LEARNING` and missing performance metrics are not reasons to wait.
 
 The common flow always sends `platformType: "GOOGLE"`; do not ask the user to provide it.
 
 ## Retrieve or create the guide
 
+Skip this call when the conversation already contains a retrieved guide or its recommendations; immediately present the supplied result using the next section instead of retrieving it again or asking for campaign identity. When the user paraphrases recommendation labels, map them to the closest unambiguous suggestion types in the translation table. Wording such as "still need to" or "still to do" means those items are `OPEN`.
+
+When the user only wants a supplied guide presented, this article already contains the response behavior. Do not read the linked action recipes until the user accepts an offer to perform that action; unnecessary recipe reads delay the answer and can prevent the navigation block from being returned.
+
 ```bash
 curl -X POST \
   'https://www.wixapis.com/pa-platform/suggestions/v1/campaign-success-guides/get-or-create' \
@@ -67,6 +73,76 @@ Present only the suggestions the API returns and preserve their order; `suggesti
 
 `OPEN` means pending action. `COMPLETED` means the user marked the item completed; it does **not** mean the API changed the site or campaign for them.
 
+## Present the guide as an actionable plan
+
+Do not return a bare list of task labels. Turn the returned suggestions into a compact action plan while preserving the API's order:
+
+Use this output structure:
+
+1. A numbered suggestion list with no navigation URLs or Markdown links inside the suggestion items.
+2. One grouped offer for the supported work the agent can perform after approval.
+3. A **Next actions** block after the complete suggestion list and offer, containing each relevant destination link exactly once.
+
+This structure is mandatory even when only one suggestion uses a destination. Never put the Editor, Google Ads, or another shared navigation link inline with a suggestion.
+
+1. Name the campaign and link `campaignSuccessGuide.url` as the analyzed landing page when present.
+2. For every returned suggestion, show its user-facing label, tracking status (`Pending` for `OPEN`, `Marked complete` for `COMPLETED`), and one concrete next step. Do not show enum values unless they help resolve an ambiguity.
+3. For each `OPEN` item, distinguish work the agent can help perform from work the user must finish in Wix. Prefer an offer to do supported work over instructions that make the user do the same operation manually.
+4. Do not offer work for `COMPLETED` items unless the user asks to reopen them.
+5. Put each unique navigation link after the suggestions as a destination-specific CTA. Do not group every URL under a generic **Open in Wix** label or reuse that label for unrelated destinations. Name the actual page or action—for example, **Go to Editor**, **Go to Google Ads**, or **Connect Google Business Profile**. Deduplicate by destination: if two or ten tasks require the Editor, include the Editor CTA **once**, at the bottom, and never repeat it beside individual tasks. Apply the same deduplication to the Google Ads dashboard or any other shared destination.
+
+The navigation block is part of the guide, including when the user supplied or paraphrased the recommendations. Before responding, resolve the destinations required by the `OPEN` items. Resolving navigation is read-only and does not require approval, including when the user says not to change anything yet. Use the selected site's `id` and `editUrl` from available site context. If the current-site ID is known but `editUrl` is absent, look up the site's navigation metadata through an available site-listing capability once; select only the result whose `id` or `metaSiteId` exactly matches that current-site ID, then read its `displayName`, `editUrl`, and `editorType`. Do not inspect other sites for campaigns. When no current-site ID is known and the lookup returns exactly one site, use it for navigation. When several sites are available and none is selected, present the action plan immediately and ask which site's CTAs to add. If an item belongs in the Editor or Google Ads, include that destination once unless the destination is genuinely unavailable; do not omit navigation merely because no API call was needed to obtain the guide.
+
+### Which action to offer
+
+| Suggestion types | Response behavior |
+| --- | --- |
+| `CLEAR_CTA_COPY`, `ABOVE_THE_FOLD_CTA`, `HEADER_MATCH`, `CONVERSION_POINT`, `GOOGLE_REVIEWS`, `TESTIMONIAL`, `CONTACT_AND_CREDIBILITY`, `FAQ_SECTION`, `MINIMIZE_FORM_FIELDS`, `SOCIAL_CHANNELS` | These change visible landing-page content. Briefly describe the edit and point to the single **Go to Editor** CTA after the suggestions. If the current environment has a site-editing capability that can safely make the specific change, offer to make it after the user approves; otherwise do not imply that marking the suggestion complete will edit the page. |
+| `MOBILE_OPTIMIZATION`, `SITE_SPEED` | Offer to inspect the problem and recommend a concrete fix first; these broad findings are not a safe one-click mutation. Include the single Editor link when the resulting work belongs there. Do not promise an improvement before identifying the actual cause. |
+| `GOOGLE_ADS_SEARCH_THEMES` | Offer to generate relevant search themes, show the proposed set, and apply the approved set to the existing campaign by following [Get AI Campaign Suggestions](get-campaign-suggestions.md) and [Manage Campaign Lifecycle](manage-campaign-lifecycle.md). Updating the campaign is a mutation, so do not apply themes merely because the guide returned this item. |
+| `GOOGLE_MERCHANT_CENTER_CONNECTION` | Offer to link the Merchant Center account using the account flow below. Reuse an already-linked Merchant Center account ID when present; otherwise ask the user for the ID. Get approval before the account update. Explain that the link begins as `PENDING` and its owner may still need to approve it in Google. |
+| `GOOGLE_BUSINESS_PROFILE_CONNECTION` | Offer to check the connection and start it by following [Connect a Wix Site to Google Business Profile](../google-business-profile/connect-google-business-profile.md). Be explicit that the agent can initiate the flow and provide its authorization URL, but the site owner must finish Google's consent in their browser. |
+
+After the tasks, make one closing offer that groups the supported actions you can take; do not append a separate approval question to every item.
+
+For a Merchant Center connection, first read the selected site's Google Ads account:
+
+```bash
+curl -X GET 'https://www.wixapis.com/_serverless/pa-google/v1/accounts/current-site' \
+  -H 'Authorization: <AUTH>'
+```
+
+Read `account.id`, `account.merchantCenterAccountId`, and `account.merchantCenterAccountLinkStatus`. If `merchantCenterAccountId` is present, use it as the existing connection context. If it is absent, ask the user for the account ID shown in Google Merchant Center; the Google Ads account API does not list candidate Merchant Center accounts. After the user confirms the ID and approves the mutation, follow [Install Google Ads and Create an Account](install-and-create-account.md) and update `merchantCenterAccountId` on `account.id`.
+
+### Build destination-specific CTAs
+
+- **Editor:** Include this only when at least one returned `OPEN` item requires landing-page or mobile editing. Use the exact `editUrl` from the selected site context or the single matching result from the site-navigation lookup described above; prefix a relative value with `https://manage.wix.com`. Never construct or guess an Editor URL, and do not substitute the public landing-page URL for an Editor link. If the site is `EDITORLESS` or has no `editUrl`, say that an Editor link is unavailable instead of inventing one. Label the CTA **Go to Editor** or name the more specific editing action; do not label it **Open in Wix**.
+- **Google Ads:** When a returned item belongs in Google Ads, use the verified route from [Google Ads Dashboard Navigation](google-ads-dashboard-navigation.md): `https://manage.wix.com/dashboard/{metaSiteId}/google-ads`. Label the CTA **Go to Google Ads** or name the specific campaign action.
+- **Other destinations:** Name the destination or action in the CTA, such as **Open Forms dashboard**, **Review site speed**, or **Connect Google Business Profile**. Never make several unrelated links look like the same generic action.
+- Include only relevant destinations and list each URL once. Authorization URLs created by a later connection flow are task-specific; return one only after the user accepts that offer and the flow creates it.
+
+Example when several tasks share the Editor:
+
+```markdown
+## Campaign success guide
+Landing page: [Request a quote](https://www.example.com/request-a-quote)
+
+1. **Clarify the main call to action — Pending**
+   Make the button describe the conversion, such as “Request a quote.”
+2. **Move a call to action above the fold — Pending**
+   Place the primary button where visitors see it without scrolling.
+3. **Configure Google Ads search themes — Pending**
+   **I can help with this:** I can propose relevant themes and apply the set you approve.
+
+I can take care of the search-theme update after you review the proposed set.
+
+### Next actions
+- [Go to Editor]({editUrl})
+- [Go to Google Ads](https://manage.wix.com/dashboard/{metaSiteId}/google-ads)
+```
+
+Each link has its own destination-specific CTA, and the Editor URL appears once even though the first two recommendations both use it.
+
 ## Translate suggestion types for the user
 
 Keep the enum value unchanged in API calls, but use these labels when explaining the guide:
@@ -95,9 +171,9 @@ The update endpoint identifies the suggestion by its **`type`**, not its suggest
 
 Before executing an update:
 
-1. Identify the campaign and a suggestion `type` currently present in its latest guide.
+1. Identify the campaign and a suggestion `type` currently present in its latest guide. Use the current-site ID directly and follow the campaign-resolution flow above; listing that site's campaigns once is valid context resolution, but account-wide site listing is not. Ask one focused site or campaign question only when the current context or campaign results leave more than one plausible target. Do not probe several sites or guess, because the same recommendation type can exist on multiple campaigns.
 2. Match the user's wording to one returned suggestion and infer the requested status only when it is clear: a statement that they completed the recommendation means `COMPLETED`; a request to reopen it means `OPEN`.
-3. Execute immediately when the campaign, suggestion, and status are unambiguous. Ask one targeted clarification only when any of them is unclear; never guess.
+3. Execute immediately when the campaign, suggestion, and status are unambiguous. The completion statement is approval for this tracking-status update; do not ask a redundant confirmation question. Ask one targeted clarification only when identity, suggestion, or intended status is unclear; never guess.
 
 Mark an item completed:
 
@@ -112,6 +188,24 @@ curl -X POST \
   }'
 ```
 
+```json
+{
+  "campaignSuccessGuide": {
+    "id": "7d4a9c2e-86f1-4b37-a2d5-9e18c6f043ab",
+    "suggestions": [
+      {
+        "type": "CLEAR_CTA_COPY",
+        "status": "COMPLETED"
+      },
+      {
+        "type": "FAQ_SECTION",
+        "status": "OPEN"
+      }
+    ]
+  }
+}
+```
+
 Reopen the same item by sending:
 
 ```json
@@ -132,7 +226,7 @@ If a mutation times out with an unknown outcome, do not retry automatically. Ret
 | `PLATFORM_NOT_SUPPORTED` | Use `GOOGLE`; do not substitute another platform value. |
 | `CAMPAIGN_TYPE_NOT_SUPPORTED` | Explain that success guides currently support Google Ads Performance Max Leads campaigns only. |
 | `SUGGESTION_NOT_FOUND` | Retrieve the latest guide and choose a `type` actually present; do not keep retrying stale data. |
-| Authentication or permission error | Stop after the first rejected campaign or guide call and explain that the current collaborator cannot access or modify it. Do not try alternate base URLs, infer that Google Ads is not installed, or probe other endpoints to bypass authorization. |
+| Authentication or permission error | Stop after the first rejected campaign or guide call and explain that the current collaborator cannot access or modify it. Do not try alternate base URLs, infer that Google Ads is not installed, or probe other sites or endpoints to bypass authorization. |
 
 ## References
 

package/skills/wix-manage/references/seo/manage-content-plan.md

@@ -1,6 +1,6 @@
 ---
 name: "Generate and Read a Wix Site's Content Plan"
-description: Generate an SEO content plan and read its blog post topics, or troubleshoot an existing content plan flow stuck at KEYWORD_RESEARCH while polling GetContentPlanFlow. Use this recipe for both generation and stalled-flow questions: it explains the intentional pause, the Create Content Plan release request, missing flow IDs, and the exact public API paths and response fields.
+description: "Generate an SEO content plan and read its blog post topics, or troubleshoot an existing content plan flow stuck at KEYWORD_RESEARCH while polling GetContentPlanFlow. Use this recipe for both generation and stalled-flow questions: it explains the intentional pause, the Create Content Plan release request, missing flow IDs, and the exact public API paths and response fields."
 ---
 
 # Generate and Read a Wix Site's Content Plan