AI in the platform
- The AI Shelf
- AI title optimization
- AI categorization
- Feed audits
- ChatGPT Feed
- Perplexity Feed
AI resources
Platform / Features /
Per-channel overrides
Feature · Map & syndicate
Same everywhere else.
Sometimes one channel needs a different title, a different category, a different price field. Per-channel overrides scope that divergence to a single feed - the catalog stays canonical for everyone else.
The difference
not as lost revenue.
Without diagnostics
✕
Rejections sit unread in each channel's own dashboard
✕
Errors surface as impression drops, weeks later
✕
Triage by error code, not by what it costs
✕
Fixes made channel-side, lost on the next feed run
With GoDataFeed diagnostics
✓
Every channel's feedback in one view, per SKU
✓
Errors ranked by the revenue the affected SKUs drive
✓
Each error linked to its data fix in the rules engine
✓
Fixes made at the source, inherited by every channel
How it works
Fix the data. Same screen.
Triage
not by error code.
A missing GTIN on your best seller outranks a warning on a discontinued SKU. Diagnostics sorts channel feedback by the sales the affected products actually drive — so the queue starts with what matters.
See triage in the product tour →
Fix at the source
to its data fix.
Each rejection opens the rule or field that caused it. Fix it once in the master catalog and every channel inherits the correction on the next sync — no channel-side patches that vanish on the next run.
Read: the error playbooks →
Watch the loop
per channel.
The history view shows eligibility as a trendline per channel, annotated with feed runs and rule changes — so you can see exactly which change moved the number.
See a live history view →
Also in the box
needs.
Alerting
Eligibility drops and sync failures to email or Slack, thresholds yours.
Feed history
Every published version diffable — what changed, when, by which rule.
Pre-submission validation
The same rulebook checks, run before publishing instead of after.
Error playbooks
Each channel error mapped to its fix, linked from the row.
Scheduled reports
Weekly eligibility digest per store, for the people who don't log in.
API access
Diagnostics data in your own BI, if that's where your team lives.
Part of the pipeline
of six.
Every feature works the same catalog. Upstream stages decide what diagnostics has to say about you.
1
Store connectors
Ingest the catalog whole, variants intact.
3
Rules engine
Fix attributes once, at catalog scale.
4
Channel templates
Maintained mappings for 200+ channels.
5
Pre-submission validation
Catch errors while they're free.
Browse all features →
Questions
How current is the diagnostics data?
Channel feedback is pulled on every feed run and on a fixed polling cadence between runs — for most channels that means diagnostics reflect the channel's state within the hour.
Which channels report into diagnostics?
Every channel with a feedback API — Google, Amazon, Meta, Walmart, Microsoft and most marketplaces. File-only channels show submission status and validation results instead.
Can my agency see diagnostics across all client stores?
Yes — the multi-store workspace rolls diagnostics up across stores, with per-store permissions for client access.
Is revenue-at-risk triage available on every plan?
Diagnostics is in every plan; revenue-at-risk ranking requires order data, which comes with any store connector that syncs sales.
Start a 14-day trial or book a demo — we'll audit your feed free and show you your diagnostics baseline.