Integration Health

The Integration Health report is the status board for your connections. It shows whether every channel is syncing reliably, when each last ran, and what is going wrong, so a broken sync never quietly costs you sales with stale prices or missing stock. What acting on it enables: catch a failing sync before customers see outdated data, diagnose the root cause from the error message without digging through logs, and ensure your channel coverage is working as expected at all times.

​

What you see

The four summary tiles at the top give an instant read on channel status across your account:

​

What good looks like

The per-channel failure rate is the key signal to watch. The report uses these thresholds to color the failure rate: Items synced is a secondary health check: a channel with a low item count relative to your catalog size may be syncing less data than expected, even if its failure rate is low.

​

Per-channel detail table

The table shows every connected channel with:

• Channel name and sync type: import, export, or a specific data type (e.g., products, prices, stock).
• Last sync: shown as a relative timestamp (“2 hours ago”, “3 days ago”). A last sync of “never” means the integration has not completed a run since it was connected.
• Status chip: Healthy, Degraded, or Failing, colored to match.
• Items synced (30d): total records processed in the last 30 days. Use this to confirm syncs are moving the volume you expect.
• Failure rate: percentage of sync runs that produced an error. Color-coded by the thresholds above.
• Last error: the most recent error message, truncated. Hover to see the full message. This is the fastest way to diagnose what is wrong without logging into the platform.

The Items synced by channel bar chart ranks channels by volume, making it easy to see which integrations are your most active and which may not be pushing as much data as expected.

​

Reading the results

• One channel failing, others healthy: the issue is isolated to that integration’s credentials, configuration, or the destination platform. Start with the last error message and credential check.
• Multiple channels degraded at the same time: may indicate a network issue, a backend overload event, or a change in your catalog that caused widespread validation failures (e.g., a bulk import that added products with missing required fields).
• Failure rate rising gradually: token expiry is a common cause; many platforms rotate API keys on a fixed schedule. A gradual rise rather than a sudden spike is the typical pattern.
• Items synced drops sharply: a sync may have succeeded (low failure rate) but pushed fewer items than usual, which can happen if a filter changed or the product selection narrowed. Worth investigating even if status shows healthy.

​

Merchant Center drift

For Google Merchant Center, WISEPIM does not only track whether the export ran. Every night it reads your listings back from Google and compares what Google is serving with what the exporter would send. Three fields are compared: title, price with its currency, and availability. The image Google holds and Google’s own item-level issues are captured alongside so you can see them, but they are not compared. A mismatch becomes a Channel drift alert in the alert feed, titled “Google is serving different data for ”. The drift panel shows the value In WISEPIM next to the value Live on Google Merchant Center and the most likely cause: the last sync failed, a change is pending the next sync, or unknown. Price and availability drift are critical, title drift is a warning. The scan runs for projects with a successful Merchant Center export in the last 14 days and covers up to 500 products per profile and 5 profiles per project per night. It waits while an export is running, and a value Google does not report counts as a match, so an empty field never shows up as drift.

​

Act on what you find

​

Related