Platform / Features /
Audit log
Feature · Teams & operations
On the record.
With several hands on the same feeds, yesterday's mystery change needs a source. Activity logs record account and store actions - who did what, when - so multi-user teams answer from the log, not from recollection.

The difference
Without GoDataFeed
With GoDataFeed
How it works
Who changed what, when - across every store you manage.
Benefits
Unexplained changes stop being unexplained.
Trace a regression to an action, not a suspicion.
Respond to what happened with the record.
The log speaks so nobody has to.
More hands on the account stays manageable.
Actions on the account are documented by default.


Capabilities
Activity logs under account management record actions across the account - the running record of who did what.
With per-store users in a shared workspace, the log ties actions to the people who took them.
Activity logs cover the who; import history covers the what-ran - together they reconstruct any timeline.
Feature · Teams & operations
Activity logs record who did what, when, across your account and stores - so multi-user teams debug and answer clients from the record.

Audit log
of six.
A timestamped record of every change.
1
Ingest the catalog whole, variants intact.
2
Fix attributes once, at catalog scale.
3
Maintained mappings for 200+ integrations, current when specs drift.
4
Catch errors before they ship, while they're free.
5
Push validated feeds on schedule, price and stock current.
6
Read every channel' feed's verdict back on one screen.
Questions
Actions across the account and its stores - the record of who did what, with timestamps.
Pair the activity log with import history: match the change to the run where behavior shifted, and the cause usually names itself.
Account-level oversight lives in account management, alongside stores, users and billing.
Start a 14-day trial or book a demo — we'll audit your feed free and show you your diagnostics baseline.
Also in the box
needs.
Eligibility drops and sync failures to email or Slack, thresholds yours.
Every published version diffable — what changed, when, by which rule.
The same rulebook checks, run before publishing instead of after.
Each channel error mapped to its fix, linked from the row.
Weekly eligibility digest per store, for the people who don't log in.
Diagnostics data in your own BI, if that's where your team lives.