Manage Campaign Success Guide

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.

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.

This differs from Get AI Campaign Suggestions, 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.” 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.

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:

   bashCopy

   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 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.

The first call may analyze the landing page, campaign configuration, and relevant site connections and can take up to 120 seconds. Later calls normally return the saved guide unless campaign changes require another analysis. Wait for the request; do not retry prematurely. If execution times out with an unknown outcome, report the uncertainty and retrieve the guide later instead of immediately triggering another analysis.

Present only the suggestions the API returns and preserve their order; suggestions is already in priority order. An empty array means no currently detected items need attention, not an API failure. Show campaignSuccessGuide.url when it helps identify the analyzed landing page.

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

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:

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 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: 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:

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:

Mark an item completed or reopen it

The update endpoint identifies the suggestion by its type, not its suggestion id. A clear statement that the user completed a specific guide recommendation—for example, “I made the call-to-action button clearer as the success guide recommended”—is an actionable request to mark that item COMPLETED, not merely an FYI. Do not require the user to turn it into a question or ask for redundant confirmation.

Before executing an update:

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. 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:

Reopen the same item by sending:

The response wraps the updated guide as { "campaignSuccessGuide": { ... } }. Treat that returned guide as the new source of truth: report the changed tracking status and summarize remaining OPEN suggestions in priority order. Do not claim the underlying recommendation was implemented. Do not update multiple items unless the user’s wording clearly identifies all of them.

If a mutation times out with an unknown outcome, do not retry automatically. Retrieve the guide later to determine the current status first.

Errors

References

• Suggestions API introduction (opens in a new tab)
• Get or Create Campaign Success Guide (opens in a new tab)
• Update Campaign Success Guide Suggestion Status (opens in a new tab)