Platform /  Features /  

Supplemental data

Feature · Optimize & transform

Add fields. Touch nothing.

The store stays the store.

Campaigns need fields the store was never built to hold - promo copy, custom labels, seasonal attributes. Supplemental data layers them onto the catalog from a separate source, joined by SKU, without editing the store.

The difference

Layered data vs. polluting the source

Without GoDataFeed

  • Campaign fields get crammed into store attributes
  • Seasonal copy edits risk the live storefront
  • Custom labels require developer time to add
  • Undoing a campaign means another store edit

With GoDataFeed

  • Campaign fields live in a supplemental file, joined by SKU
  • The storefront never carries feed-only data
  • Custom labels update from a sheet, not a sprint
  • Removing a campaign is removing a file

See it work on your own catalog.

Run a free feed audit

How it works

Layer promo copy, custom labels and seasonal fields without touching source.

Benefits

Campaign agility

Promo fields turn on and off without store deployments.

Cleaner storefront data

The store schema stops absorbing marketing fields.

Segmentation levers

Custom labels feed the campaign structures channels use.

Marketing self-serve

A spreadsheet update replaces a developer ticket.

Reversible

Campaign data leaves as cleanly as it arrived.

SKU-precise

Enrichment lands exactly on the products it targets.

Capabilities

Supplemental sources

Add a file alongside the main import - promo text, badges, seasonal fields - matched to products by SKU and merged into the feed.

Custom labels for campaigns

Populate custom label fields to segment campaigns by margin band, seasonality or promotion - the levers bidding strategies read.

Feed-only enrichment

Everything added stays in the feed layer. The store's catalog remains exactly what the storefront needs it to be.

Feature · Optimize & transform

Supplemental Feed Data & Custom Labels | GoDataFeed

Layer promo copy, custom labels and seasonal fields onto your catalog from a separate source, joined by SKU - the store stays untouched.

Supplemental data

Supplemental data is stage three

of six.

Add data your store doesn't hold.

Every feature works from the same catalog. Upstream hands off clean data; this stage shapes it for each channel.

Questions

Feature · Optimize & transform

How does supplemental data attach to products?

By a shared identifier - typically SKU. The supplemental file joins the imported catalog and its fields become available to every feed.

What do teams use it for?

Promo copy, custom labels for campaign segmentation, seasonal attributes, badge text - fields that matter to feeds but don't belong in the store.

Does it modify my store?

No. Supplemental data merges in the feed layer only - the source platform is never written to.

Enrich without editing the store.

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.