Analytics onboarding
Analytics reporting is only as complete as the data sources you’ve connected. Onboarding is a one-time setup in the FDX control panel — and if you’re using FDX Enrichment, complete it before you roll enriched content out widely, so you have a clean baseline to compare against.
Reporting starts accumulating data from the moment you connect. Connecting a week before your first large rollout gives you a real “before” picture instead of a reconstructed one.
What you get, depending on what you connect
Google Ads gives you the core enrichment story: impressions, clicks, CTR, spend, conversions, and ROAS, filterable by campaign, ad group, and custom label. The custom-label filtering is what makes A/B testing readable — it’s how you separate your test group from your control.
A BigCommerce store, if you have one, adds on-site reporting: sessions, page views, orders, revenue, and conversion rate, with channel and landing-page breakdowns. This is optional. If your storefront isn’t on BigCommerce, you’ll skip it and rely on paid-media reporting plus your own site analytics.
Both together gives you the reconciled picture — paid media and on-site behavior side by side, including traffic from AI assistants and crawlers separated into its own channel.
The setup wizard
Connecting sources is a four-step wizard. Not every step applies to every account.
Select your FDX database
Choose the database holding the catalog you’re enriching. If you run several, connect the one whose performance you want to report on first — you can repeat this setup for others.
Authenticate BigCommerce (optional)
If you have a BigCommerce storefront and want on-site reporting, authenticate here. If you don’t, skip this step — you’ll go straight to connecting paid media, and everything else works normally.
Select your BigCommerce store
Only applies if you completed the previous step. Pick the store that matches the catalog in your selected database.
Authenticate paid media
Connect Google Ads. This is where enrichment’s effect on ad performance shows up first, and it’s what makes the custom-label reporting behind A/B testing work.
Who needs to do this
Connecting paid media requires signing in to the ad account, so whoever holds those credentials needs to be involved. In practice this is often a different person from whoever runs enrichment — if that’s you, loop in your paid media owner early rather than at the point you want to report results.
Once you’re connected
Reporting begins collecting data going forward. Give it time to accumulate before drawing conclusions.
Analytics still can’t tell which of your products are enriched until you tag them — UTM parameters on your feed product URLs, and custom labels in Google Merchant Center. That tagging is required and doesn’t happen automatically. See Measuring impact in Analytics, and do it before you enrich if you can.
Then head to Measuring impact in Analytics for the reports, or Proving enrichment works for what to look at and how to build a comparison that holds up.