Platform /  Features /  

Feed history

Feature · Validate & monitor

What ran, when.

Receipts attached.

When a channel shows something odd, the first question is what shipped and when. Feed history keeps the record of every catalog run - with the source file, merge file and product catalog downloadable from each - so answers come from files, not memory.

The difference

A kept record vs. reconstructing from memory

Without GoDataFeed

  • What was in Tuesday's feed is anyone's guess
  • Debugging starts by re-creating the past by hand
  • Source data from before the fix is gone
  • Disputes settle by seniority, not evidence

With GoDataFeed

  • Every import run sits in a reviewable history
  • Each run's source, merge and catalog files download on demand
  • The data as it was is retrievable, not reconstructed
  • Questions settle by opening the file

See it work on your own catalog.

Run a free feed audit

How it works

Every import on the record - with the files to prove it.

Benefits

Debug from evidence

Open the actual file from the run in question.

Before-and-after in hand

Compare a run's data against the run before it.

Vendor disputes settled

The source file shows what the source sent.

Faster root cause

Trace an anomaly to the run that introduced it.

No hoarding exports

The platform keeps the record so you don't have to.

Institutional memory

The history outlasts any one person's recollection.

Capabilities

Run history

Import history lists every catalog run and its outcome - the record of what happened, in order, reviewable in-app.

Per-run file downloads

Download the raw source file, the merge file and the resulting product catalog from any run - the actual data as it stood, not a reconstruction.

Account activity logs

Alongside the run record, activity logs under account management track account and store actions.

Feature · Validate & monitor

Feed & Import History | GoDataFeed

A kept record of every catalog run - download the source file, merge file and product catalog from any import and debug from evidence.

Feed history

Feed history is stage six

of six.

Every published version, diffable.

Every feature works from the same catalog. Upstream stages decide what diagnostics has to say about you.

Questions

Feature · Validate & monitor

What does import history record?

Each catalog import run and its outcome, reviewable from the import section in-app.

What files can I download from a run?

The raw source file, the merge file and the product catalog produced by that run.

How do I trace when a problem started?

Walk the run history and download files from before and after the anomaly - the comparison points at the run that introduced it.

Answer from the record.

Start a 14-day trial or book a demo — we'll audit your feed free and show you your diagnostics baseline.

Start free trialBook a demo

Also in the box

Everything the monitoring loop

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.