# AdexPilot user guide

Updated: 2026-10-02

Connect your store, understand your products, and turn useful insights into reviewed actions. This guide explains what AdexPilot does, where to find it, and what remains under your control.

This is public product guidance, not permission to act. Current workspace settings, evidence and approval controls govern every action.

## Get started with your store

Guide: /docs/getting-started

Set up one Shopify store per workspace and start using AdexPilot before connecting every advertising channel.

### Steps

1. **Create your workspace.** Sign in, choose a workspace name, and connect the Shopify store you manage. Another store needs a separate workspace.
2. **Let your first import finish.** AdexPilot imports available catalog, variant, inventory, order, refund, and unit-cost information. Catalog visibility and completed sales analysis are separate stages.
3. **Ask your Agent.** Start with a store summary or a product question. Add Google or Meta connections when you need their advertising evidence or catalog feeds.

### A useful first session

Open Product analytics to inspect what has arrived, then ask the Agent to explain the store using the available evidence.

- Check Connections for import progress and required setup.
- Look at sales, returns, inventory and data coverage before interpreting a ranking.
- Open Activity to see completed updates or a reason work is waiting.
- Ad channels are optional for getting started with Shopify information.

### Understand your workspace

Your store, team access, plan, credits and decisions belong to the selected workspace. Check the workspace selector before connecting an account or reviewing an action.

- One connected Shopify store per workspace.
- A different store uses a different workspace.
- Some controls require an owner or administrator.
- An available connection is not proof that every provider prerequisite is complete.

### Try asking

- Tell me what you know about my store, and what data is still missing.
- Which products should I review first and why?

**Do I need Google and Meta to start?**

No. You can use Shopify-based context first. Each advertising or search connection adds its own evidence and capabilities.

Related: /docs/connections, /docs/agent, /docs/product-analytics

## Connect the right accounts

Guide: /docs/connections

Shopify, Google Ads, Merchant Center, Meta and Search Console serve different purposes. Connect only what you need.

### Steps

1. **Connect Shopify first.** Use onboarding or Connections in the correct workspace. Review the requested access and complete the store import.
2. **Add your channels.** Connect Google Ads for advertising evidence, Merchant Center for Google catalog feeds, Meta for Meta evidence and feeds, and Search Console for organic search information.
3. **Check account selection and status.** Review the selected accounts, import status and any setup requirement in Connections. Reconnect when access expires or changes.

### What each connection adds

These connections are independent. Signing in with Google does not connect your advertising or search accounts.

- Shopify: catalog, variants, inventory, orders, refunds and available unit costs.
- Google Ads: advertising accounts, campaigns and available performance evidence.
- Google Merchant Center: the Google feed destination and available catalog status.
- Meta: available advertising-account and catalog evidence, and the Meta feed destination.
- Google Search Console: verified store-property search performance and SEO opportunities.

### Connected versus ready

A successful connection confirms access, not that campaigns or products are ready to run.

- A Google manager account still needs an eligible advertising client account selected.
- Merchant Center setup can require domain verification and shipping or tax information.
- Meta catalog and measurement setup may need additional provider-side work.
- Search Console must be bound to the correct verified store property.
- TikTok and WooCommerce are not current launch integrations; they remain coming soon.

### Try asking

- Which connections are ready, and what does each one let you do?

**Is Google Ads enough to generate a Google feed?**

No. Google catalog feeds require a Merchant Center connection. Google Ads alone is insufficient.

**Does connecting an account approve changes?**

No. Connection access and permission to make changes are separate. Review and automation controls still apply.

Related: /docs/feeds, /docs/campaigns, /docs/organic-performance, /docs/permissions

## Work with your AI Agent

Guide: /docs/agent

AdexPilot’s custom AI Agent uses your permitted store evidence to explain performance, inspect issues and help prepare next steps.

### Steps

1. **Ask a specific question.** Describe the result you want: understand a product, diagnose a feed issue, or prepare a campaign for review.
2. **Review evidence and next steps.** Read the answer, expand its sources or product details, and distinguish a suggestion from a saved draft or confirmed action.
3. **Continue through the review flow.** Use the relevant preparation or review control. Chat text does not replace required approval, account setup or permission.

### Questions you can bring to the Agent

The Agent can work with available Shopify, advertising, feed, organic search and Activity context. Its view is limited by your permissions and the data currently available.

- Summarize your store and explain missing evidence.
- Compare products using sales, advertising, inventory and refund information.
- Explain catalog issues and the last scheduled update.
- Prepare a reviewable campaign preview or inspect SEO opportunities.
- Open the workspace Agent panel from another page; use the full Agent page for longer work.

### What an answer means

A preview is a proposal to inspect, not proof that something has changed in Google, Meta or Shopify.

- Sources and coverage help you assess confidence.
- Missing unit costs leave profit unknown; they do not prevent ordinary Agent questions.
- Current data and permissions take priority over older conversation context.
- If the Agent stops, inspect diagnostics or Activity before retrying a request that may already have been accepted.
- Your conversation history holds ordinary questions and answers; Activity holds operational work.

### Try asking

- Explain my last scheduled update and any unresolved issues.
- Prepare a Google campaign preview using available products. Show any launch requirements separately.
- Why is this product spending without generating enough sales?

**Can the Agent bypass approvals if I ask?**

No. It can help you prepare work, but asking to ignore a requirement does not grant provider or billing authority.

**Will it always know actual profit?**

No. Profit analysis needs trustworthy costs and other relevant inputs. The Agent should explain what is unknown rather than inventing it.

Related: /docs/campaigns, /docs/activity, /docs/credits, /docs/assistant-connections

## Read product and store performance

Guide: /docs/product-analytics

Use Performance for the store-level picture and Product analytics for the products and variants behind it.

### Steps

1. **Choose the right view.** Performance shows store and channel trends. Product analytics lets you inspect individual products, variants and their available evidence.
2. **Check coverage and freshness.** Review the date window, currency, latest completed update and any partial or missing source information.
3. **Choose a useful action.** Investigate inventory or feed problems, review wasted spend, or prepare a test using the available evidence.

### Useful signals, with their limits

Sales, advertising spend, returns, inventory and feed status can reveal opportunities. Not every source reports on the same basis.

- Provider-reported ROAS is not the same as store-wide profitability.
- Refunds and relevant fees can change the interpretation of sales.
- Product-level attribution may be unavailable even when aggregate advertising data exists.
- Partial, stale or mixed-currency data should not be treated as complete.
- A visible subset of products is not automatically a whole-store ranking.

### Unit costs improve profit decisions

AdexPilot reads available variant unit costs from Shopify. Add or correct the cost per item in Shopify to improve future profit analysis.

- Retail selling price is not the product’s unit cost.
- Missing costs remain unknown rather than being treated as zero.
- Ordinary Agent use and campaign preparation can use other available signals.
- Profit-based scaling needs sufficiently reliable economics and supporting evidence.
- Saved Shopify changes are reflected after the relevant data update completes.

### Try asking

- Compare my products by available sales and ad evidence, and flag unknown profit.
- Which products have inventory or refund risks?

**Why does a product show unknown profit?**

One or more required cost or performance inputs are unavailable, stale or inconsistent. Inspect that product’s coverage and update the relevant source information.

Related: /docs/agent, /docs/campaigns, /docs/feeds, /docs/refresh-and-autopilot

## From campaign idea to approved action

Guide: /docs/campaigns

Preview products, prepare a campaign, review the proposal, then approve eligible creation. Creation is paused; launching is a separate decision.

### Steps

1. **Preview and choose.** Ask the Agent for a campaign preview. If performance ranking is unavailable, a catalog selection must be described as unranked. Review the products and requested settings.
2. **Prepare for review.** Choose markets and a supported budget, check the request, and confirm any displayed credit use. Preparation needs complete required analysis and current account evidence.
3. **Approve creation, then decide on launch.** Inspect the prepared proposal in Review. Eligible approved creation creates a paused campaign; enabling spend needs a separate launch approval.

### Draft, preparation, creation and launch

These are distinct stages. A campaign does not appear in your advertising account just because a preview or review draft appears in AdexPilot.

- A preview helps inspect products and the request without creating ads.
- A saved review draft can retain unresolved requirements.
- Preparation produces reviewable campaign work after required data is ready.
- Approved provider creation must return confirmation before it is described as created.
- A paused campaign does not spend; an approved launch is separate.

### Why preparation may wait

Missing unit costs alone do not stop preparation. Other requirements can still prevent a valid campaign from being prepared or created.

- Incomplete or stale saved product analysis.
- No eligible Google advertising client selected, or an unavailable Meta account.
- Unverified feed/product eligibility, unsupported product state or missing inventory evidence.
- Required market, currency, measurement or budget information.
- Unsupported request settings: current preview/MCP flows do not configure lifetime budgets, date schedules or negative keywords. A requested setting is not a configured setting.

### A practical starting request

Specify the provider, products or selection basis, market and daily budget. If you need an unsupported setting, ask the Agent to identify that limitation before preparing anything.

- Inspect the current update in Activity when analysis is incomplete.
- Use Connections to correct account setup.
- Save a review draft while unresolved requirements are investigated.
- Review the provider, products, budget and paused state before approving.

### Try asking

- Prepare a paused Google campaign proposal for these products in my selected market with a daily budget of $5. Show what still needs verification.

**Why can’t I see the preview in Google Ads?**

A preview or saved draft is inside AdexPilot. It appears in Google Ads only after eligible creation has been explicitly approved and confirmed by the provider.

**Can a test bypass account or approval requirements?**

No. A paused test still creates provider resources and must meet the current setup and approval requirements.

Related: /docs/connections, /docs/agent, /docs/credits, /docs/permissions, /docs/activity

## Automatic Google and Meta feeds

Guide: /docs/feeds

Catalog Health shows automatic destination feeds, their last successful file, provider status and product issues.

### Steps

1. **Connect the destination.** Google requires Merchant Center. Meta requires a Meta connection. A missing destination is explained in Catalog Health; it does not need an empty feed.
2. **Wait for the initial build.** After the connection is ready, AdexPilot requests the destination’s initial feed using complete Shopify source data. If the import is not ready, the build waits.
3. **Follow scheduled updates.** Connected feeds update through the existing 12-hour store refresh. Check Catalog Health and Activity for progress, waiting reasons and the next scheduled update.

### Automatic means no Generate button

Merchants do not manually generate or retry the regular catalog feed. Saving market or feed settings does not start an extra build.

- Only connected, enabled destinations are built.
- Google Ads alone does not enable a Google catalog feed.
- Saved feed changes apply in the next scheduled update.
- An initial build may wait for current work or the required source import.
- The separate supplemental-label workflow is not a manual refresh control for the catalog feed.

### Three separate statuses

A file can be generated successfully without being accepted by the provider or without every product being eligible.

- File generation: AdexPilot produced a feed from available source data.
- Provider delivery or acceptance: the destination fetched, registered or processed it where confirmed evidence is available.
- Product eligibility: Google or Meta determines whether individual listings can be used.
- Unknown provider status must stay unknown; it is not an approval.
- Inspect issue details for missing images, prices, identifiers, stock or market information. Correct the relevant source data.

### Labels and supplemental data

Labels can help organize products for review or campaign grouping. Their value depends on the available product evidence and the provider’s feed setup.

- Use labels to group test, scale, fix or stock-review candidates.
- Do not infer profitable products from missing costs.
- Check the supplemental workflow and provider setup separately.
- A label dependency is not usable for campaign targeting merely because its file exists.

### Try asking

- Why has my Google or Meta feed not generated?
- Explain file generation, provider acceptance and product eligibility for my latest feed.

**Does signing in refresh my feeds?**

No. Initial destination setup and the scheduled store cycle drive regular generation. Signing in or opening Catalog Health does not start another build.

**Are all products guaranteed compliant?**

No. AdexPilot checks and formats feed data, but provider policies, source quality, website consistency and account setup determine acceptance and eligibility.

Related: /docs/connections, /docs/refresh-and-autopilot, /docs/activity, /docs/troubleshooting

## 12-hour updates and Autopilot

Guide: /docs/refresh-and-autopilot

Scheduled data refresh and automated changes are different. Turning Autopilot off keeps data updates running while preventing new automated changes.

### Steps

1. **Keep your connections current.** Every 12 hours, eligible enabled stores enter their scheduled refresh. Connected-source data and product analysis are updated, followed by eligible feed work.
2. **Choose automation permissions.** Use Autopilot to review the available actions, provider accounts, campaign scope and limits. Connecting an account does not grant automation authority.
3. **Review each cycle in Activity.** Inspect refreshed sources, saved Autopilot disposition, proposals, confirmed actions and any credits supported by the saved evidence.

### What happens every 12 hours

The interval is a schedule, not a guarantee that all provider data becomes available at the same moment.

- Available Shopify and connected advertising information is refreshed.
- Product analysis is materialized from the completed source evidence.
- Eligible connected catalog feeds are updated after required Shopify data is ready.
- A scheduled Autopilot evaluation may run according to its saved settings and available evidence.
- Provider delays, incomplete imports, expired access or operational-access limits can leave a stage waiting or incomplete.

### What Autopilot does and does not mean

The scheduled review uses checks; a history entry does not by itself mean a paid AI scan ran.

- Off: data refresh continues, but new automated mutations are prevented.
- Enabled: only supported actions within current permissions and limits can proceed.
- Incomplete evaluation does not mean all campaigns were checked.
- No-change cycles should explain that nothing changed.
- Campaign creation and launch remain separate controlled actions; broad chat requests do not authorize them.

### SEO runs on its own schedule

Organic Performance has separate search-data availability, weekly SEO preparation and publication permissions. It is not a full SEO rewrite every 12 hours.

- Advertising permissions do not permit Shopify SEO edits.
- SEO review and automatic publication settings are separate.
- Use Activity to distinguish a store refresh, advertising evaluation and SEO batch.

### Try asking

- Was Autopilot on during the last cycle, what was checked, and what actually changed?

**Does every refresh consume AI credits?**

No. A scheduled refresh or rules-based check is not proof of paid AI work. Activity distinguishes model work and credits when the saved evidence is available.

**Why is completion later than the due time?**

The due time starts scheduled work. Imports, provider delays and recovery can make completion later. Check individual stages in Activity.

Related: /docs/activity, /docs/feeds, /docs/permissions, /docs/organic-performance

## See what AdexPilot did

Guide: /docs/activity

Activity combines operational work in one timeline: updates, checks, proposals, changes, failures and associated credits.

### Steps

1. **Open Activity.** Use the main navigation or top-bar Activity control. The default view shows the latest seven days, newest first.
2. **Filter and expand.** Choose a date range, work type, provider or status. Expand a row to inspect available coverage, reasons and linked review or result pages.
3. **Ask the Agent for context.** Use Ask Agent about this activity to retrieve the selected operation rather than guessing from its timestamp.

### A useful report for each cycle

A quiet successful refresh stays compact. Expanded detail explains the available source stages, Autopilot state and linked work.

- What was refreshed and when it completed.
- Whether Autopilot was off, skipped, evaluated or incomplete.
- What was proposed, awaiting approval, submitted or provider-confirmed.
- Which requirements remain unresolved.
- Confirmed credit usage, pending usage or unknown evidence where applicable.

### Read statuses carefully

The timeline reports saved evidence. It does not turn a proposal into a completed provider action.

- Approval is different from submission, and submission is different from confirmation.
- Processed records are different from changed resources.
- Ordinary chat Q&A stays in conversation history.
- Completed compact reports are retained for 90 days; unresolved work remains visible until resolved, subject to applicable retention and access rules.
- Older retained sources may have incomplete coverage.

### Try asking

- Explain the last cycle in plain language, including anything that did not complete.
- Which unresolved activities should I deal with first?

**Does reading Activity start work or charge credits?**

No. Viewing or retrieving saved Activity does not run a refresh, model call or provider change. Asking the Agent to explain it follows normal Agent credit rules.

Related: /docs/refresh-and-autopilot, /docs/credits, /docs/agent, /docs/troubleshooting

## SEO and Organic Performance

Guide: /docs/organic-performance

Connect verified search data, discover page opportunities and review Shopify SEO title and description changes before publication.

### Steps

1. **Connect Search Console.** Bind the correct verified property to your store. Search data uses finalized reporting dates and can lag behind today.
2. **Inspect an opportunity.** Open Organic Performance or ask the Agent. Review the page, observed search terms, coverage and proposed before/after metadata.
3. **Review publication separately.** Where publication is available, enable the required Shopify editing access and submit the proposal through Review. Advertising approval does not authorize SEO edits.

### More than generic suggestions

AdexPilot can surface search opportunities and prepare supported product or collection SEO title and description proposals. Publication requires separate permissions and a valid review flow.

- Use observed search demand and current catalog facts.
- Inspect before/after text rather than approving an unexplained rewrite.
- Missing economics remain unknown; search performance is not attributed product revenue.
- The Agent’s preview is different from saving a proposal or publishing it.
- Provider-confirmed publication and storefront visibility are separate checks.

### Optional SEO automation

Review is the default. Eligible owners or administrators can configure separate, revocable SEO automation for supported metadata changes when the required capability and editing access are available.

- Weekly preparation considers up to 20 prioritized opportunities per batch.
- Automatic changes are bounded to at most 10 pages per day with a minimum 28-day rewrite cooldown.
- Replacing existing merchant metadata or using custom brand instructions requires human review.
- Limits, exclusions, selected pages, pause and revoke controls constrain the work.
- Uncertain publications must be reconciled rather than blindly repeated.

### Results and undo

Results compare available finalized 28-day before/after windows. Timing, sample size, seasonality and other changes affect the comparison.

- Before/after changes do not prove that an SEO edit caused the result.
- Undo can restore supported metadata when no conflicting merchant edit intervenes.
- Publication status and change details stay linked from Activity.
- AdexPilot does not provide a complete technical SEO, backlink, site-speed or indexing guarantee.
- Theme edits, broader copywriting and unsupported localized publication are outside this metadata workflow.

### Try asking

- Which pages have useful organic-search opportunities?
- Preview a supported SEO title and description change, with its evidence and limitations.

**Will AdexPilot automatically improve my rankings?**

No ranking or traffic gain is guaranteed. It helps you review evidence and make controlled, supported metadata changes.

**Why are recent search dates missing?**

Search Console reports with a delay. AdexPilot uses finalized observations and shows incomplete coverage rather than treating missing days as zero.

Related: /docs/connections, /docs/permissions, /docs/activity, /docs/agent

## Use AdexPilot from an assistant

Guide: /docs/assistant-connections

Connect an assistant that supports remote MCP and OAuth to permitted AdexPilot workspace tools.

### Steps

1. **Add the remote connection.** In a compatible assistant, add https://mcp.adexpilot.com/mcp. The exact setup controls and availability depend on the assistant and your plan.
2. **Authorize your workspace.** Sign in to AdexPilot, select the workspace and review the requested permissions. The assistant can access only the tools and data your delegation permits.
3. **Ask, then review in AdexPilot.** Read permitted context or prepare supported proposals. Open the returned review link for actions that need merchant approval.

### What a connected assistant can do

Available tools can provide scoped store, product, campaign, feed, organic and Activity context, and eligible proposal preparation.

- Read permitted workspace evidence and recent operations.
- Inspect supported campaign or SEO proposal information.
- Call the AdexPilot Agent when authorized; normal credit rules apply.
- Respect current membership, role and delegated permissions.
- Manage or revoke the assistant connection from workspace Connections.

### What delegation does not permit

An assistant connection is not unlimited authority over your app or advertising accounts.

- No bypass of campaign approval or launch requirements.
- No assistant approval of Shopify publication, subscriptions or credit purchases.
- No automatic permission to enable automation.
- Billing details require both your underlying access and the delegated billing permission.
- Current external campaign constraints support daily budgets; lifetime budgets, date schedules and negative keywords are explicitly unsupported.

### Try asking

- Summarize recent permitted AdexPilot activity and identify pending decisions.

**Does every assistant request use AdexPilot credits?**

Read-only context tools do not themselves invoke AdexPilot’s model. Calling the AdexPilot Agent uses the normal authorization and credit policy. Your assistant may have its own separate pricing.

Related: /docs/agent, /docs/permissions, /docs/credits, /docs/activity

## Plans, credits and billing

Guide: /docs/credits

Know when work needs credits, review the charge confirmation and manage your workspace plan through Billing.

### Steps

1. **Check your allowance.** Open Billing for the selected workspace’s plan, balance and usage. Public Pricing shows current published plans and eligible offers.
2. **Confirm eligible work.** Where a preparation flow shows a credit quote, review it before continuing. A quote or reservation is different from settled usage.
3. **Review the final result.** Use Billing and available Activity details to distinguish settled credits, pending reservations, releases and refunds.

### What consumes credits

Credits cover eligible Agent and premium preparation work. The displayed task policy governs the merchant charge; credits are not advertising spend.

- Ordinary scheduled refreshes and rules checks do not imply a paid AI scan.
- Regular automatic catalog file generation is shown separately from paid preparation work.
- Viewing saved Activity is not an additional model charge.
- Asking the Agent for a new explanation follows the normal Agent billing policy.
- Pending or unknown settlement should not be presented as a confirmed charge.

### Subscriptions and access

Shopify hosts subscription and eligible credit-pack approval. Paid access follows verified billing status, not merely opening a checkout link.

- Use the current Pricing page and in-app Billing rather than old plan screenshots.
- Eligible free offers show their exact allowance and expiry in the current offer.
- Credits, plan capacity, permissions and provider readiness are different requirements.
- An expired trial or restricted operational access can pause work even when a provider remains connected.
- See the refund policy or contact Support for a billing issue.

### Try asking

- Explain the credit status of this activity without treating reservations as separate charges.

**Do credits pay Google or Meta for ads?**

No. Provider advertising spend is separate from AdexPilot’s subscription and credits.

**Where is Billing?**

Use Billing in the workspace navigation. The canonical workspace address ends in /billing; older settings/billing links remain compatible.

Related: /docs/activity, /docs/permissions, /docs/campaigns, /docs/troubleshooting

## Permissions, privacy and control

Guide: /docs/permissions

Workspace membership, provider access, approvals and automation permissions each control a different part of AdexPilot.

### Steps

1. **Choose the correct workspace.** Inspect the store and your role. Reading a report does not imply permission to change settings or manage billing.
2. **Grant only the access you need.** Review connection permissions, supported approval controls and any separate automation or SEO authorization.
3. **Pause or revoke when needed.** Use the relevant automation and connection controls. Revocation prevents new work within that authorization; inspect accepted or uncertain work in Activity.

### Separate controls, one clear decision

The Agent’s recommendation cannot replace merchant permission.

- A connection gives access to provider data, not blanket authority to make changes.
- Campaign creation and launch need distinct approval.
- Advertising automation is limited by supported actions, accounts and caps.
- SEO editing and automation require separate authorization.
- An assistant delegation cannot exceed the merchant’s own workspace access.

### What you should share with Support

Provide the workspace, affected page, approximate time, visible status and a redacted screenshot or operation reference.

- Never send passwords, access tokens, feed credentials or payment details in chat.
- Avoid including private customer/order information unless essential and requested through the appropriate support channel.
- Do not assume another workspace or member can see your private Agent work.
- Read the Privacy Policy for data handling and the applicable account controls.

### Try asking

- What permissions are required for this proposed action?

**Can enabling Autopilot authorize SEO edits?**

No. Advertising permissions and SEO publication permissions are separate.

Related: /docs/connections, /docs/refresh-and-autopilot, /docs/assistant-connections, /docs/credits

## Find the next useful step

Guide: /docs/troubleshooting

Understand waiting, incomplete and failed states before retrying or changing your setup.

### Steps

1. **Open the relevant activity.** Inspect the latest update or affected operation and read its specific reason, coverage and stage.
2. **Check the source or connection.** Correct the account, Shopify data, provider setup or access requirement identified by the issue. Opening a page does not refresh the source.
3. **Contact Support if unresolved.** Use Support in the app sidebar. Include the operation reference, time and a redacted screenshot; email support@adexpilot.com if you cannot sign in.

### Common questions

Different problems need different fixes. A generic connected badge or successful file does not prove the whole workflow is ready.

- Feed not generated: check Merchant Center or Meta connection, enabled settings and completed Shopify import.
- Feed generated, products not eligible: inspect provider status and product issues; generation is not acceptance.
- Saved analysis incomplete: inspect Product analytics coverage and the latest scheduled update.
- No paused campaign in your account: check whether only a preview/draft exists or creation was actually approved and confirmed.
- Agent stopped: inspect the visible reason and diagnostics; do not assume a provider action completed.
- Search data missing: verify the property and finalized coverage; recent dates may not be available yet.

### Avoid duplicate work

An uncertain response means the outcome needs checking, not that an action definitely failed.

- Check Review and Activity before submitting the same action again.
- Use reconnection controls for expired provider access.
- Regular catalog feeds have no merchant Generate or Retry action.
- Rate-limit messages require waiting for the shown retry duration; repeated bursts can extend the problem.
- Keep secrets out of screenshots and support messages.

### Try asking

- Explain this failed or waiting activity, and tell me the exact next step.

**Is a healthy status proof that my campaign was created?**

No. Look for the specific approved operation and provider confirmation. General service or connection status does not prove a campaign exists.

Related: /docs/activity, /docs/connections, /docs/feeds, /docs/campaigns
