Bottom line:

  • Official: native Alibaba.com data support is still integrating—this is not only your store.
  • Recommended path: browser extension → agent reads real pages → verify key figures before use.
  • Unchecked numbers stay out of buyer replies, board reports, and ad budget decisions.

Ops asks Accio to “check the store,” then impressions and inquiries disagree with My Alibaba. The common-ops FAQ already states the cause and the fix. Trade-assistant API setup: connect the assistant. This page only covers bad reads.

1. What official docs say about connecting Alibaba.com

  • Q: Can we connect Alibaba.com / Taobao / Tmall now?
  • A: Native Alibaba.com international data support is still integrating. For now, ask the agent to open a browser, visit the store backend, and operate or analyze there.

Treat “perfect local warehouse sync” as not the current state. The reliable path is read the live backend page.

2. Official three steps when analytics look wrong

  1. Confirm the browser extension is installed.
  2. Ask the agent to read from the real web page.
  3. Ask it to verify key data item by item.
  • Use desktop + Chrome (extension integration is desktop-capable per install help)—see desktop vs web.
  • Log into the seller backend first, then point the agent at a specific page (stats, inquiry list)—not a vague “analyze my store.”
  • Require a table: field | agent value | backend value | match? Red rows never enter the weekly report.

3. Connectors and reconnect

Sidebar → Features → Connectors → authorize. Common ops mentions Gmail, X, LinkedIn, Ins, GitHub, Alibaba.com, Feishu, and more. On failure: network → API key → Reconnect; some platforms need periodic re-auth.

4. Scheduled patrols still need the same gate

Daily store patrols can run on a schedule, but outputs still pass “live page verify.” See scheduled tasks. Automation only makes the job appear on time; accuracy still needs the extension.

5. Who may publish a number

UseRaw agent OK?Who checks
Internal triageOK to skimOps glances at backend
Board report / ad budgetNoOps + finance each sign a line
Buyer-facing performance claimsNoDo not use unverified agent stats

6. Common misreads

  • Switching to a pricier model will not finish Alibaba.com data integration by itself.
  • Forcing extension-dependent flows in the web app—move to desktop.
  • Assuming Taobao/Tmall/Alibaba.com share one finished connector—international data is still integrating.

7. Stop conditions

  • Agent cannot open your logged-in backend page → fix extension/login first.
  • Key rows mismatch → leave the report blank or “pending export.”
  • Connectors keep failing → finish network/key/reconnect, then send the error text to Accio support instead of creating duplicate authorizations.

FAQ

Why don’t agent impressions match My Alibaba?

Official: native Alibaba.com data support is still integrating. Install the browser extension, read real pages, verify key fields one by one.

Can I connect Alibaba.com / Taobao / Tmall natively?

Official: Alibaba.com international data support is still integrating. For now, ask the agent to open the browser and work on the live store backend.

Which apps are in Connectors?

Common ops lists Gmail, X, LinkedIn, Ins, GitHub, Alibaba.com, Feishu, and more—see the in-app authorization page for the full list.

Connector failed—what first?

Network → valid API key → Reconnect. Some platforms need periodic re-auth.

Is this the same as connecting the trade assistant?

No. Trade-assistant install/auth is a separate guide. This page is only the “numbers look wrong / extension / still integrating” path.

Related reading

Field notes from Corpable Marketing Limited for Alibaba.com sellers. Not legal, tax, or audit advice. Platform rules and Accio capabilities follow current official notices and the client UI. Membership fees go to ALIBABA.COM HONG KONG LIMITED—Corpable does not collect them.