At a glance
Feed Ingestion Success (last 24h) is the percentage of feed import lines Fruugo accepted across its twice-daily ingestion in the last 24 hours. It is the health gauge for the pipe that carries your catalogue from BigCommerce through Feedonomics into Fruugo’s 40+ country marketplaces. A reading below 95% signals a schema or VAT-metadata regression that is silently dropping listings before they ever reach buyers. Watch this gauge as the first vital sign of your Fruugo distribution.
| What it counts | The share of feed import lines accepted by Fruugo’s twice-daily ingestion over the trailing 24 hours. |
| Sample type | Gauge, accepted lines as a percentage of submitted lines |
| Why it matters | A healthy feed keeps your catalogue live across every locale. A dip means listings are being dropped or rejected before they reach buyers. |
| Reading the value | Closer to 100% is healthy. Below 95% is a regression worth investigating; the shortfall tells you roughly what proportion of lines failed. |
| Currency | percent |
| Time window | 24H |
| Alert trigger | <95% |
| Sentiment key | fru_feed_ingestion_health |
| Roles | owner, operations, engineering |
Calculation
The gauge divides the number of feed lines Fruugo accepted by the total lines submitted across the twice-daily imports in the trailing 24 hours, expressed as a percentage. Rejected and skipped lines, whether from schema faults, missing VAT metadata, or policy breaches, count against the success rate. Because Fruugo imports the same feed for all locales, a single recurring fault can pull the whole percentage down.Worked example
A representative reading of Feed Ingestion Success (last 24h) for a typical merchant on Fruugo. On 12 Mar 26 the gauge reads 92% (illustrative), down from a steady 99%, after a Feedonomics mapping change left a category’s HS commodity codes blank and Fruugo rejected those lines on VAT grounds. Roughly 1 in 12 submitted lines failed, quietly shrinking the live catalogue. Engineering sees the dip on the gauge before sales drop. Vortex Mind investigates which transform broke and which fields are empty, and Ask Viq answers “what is the top rejection reason in the last import” in plain English so the team patches the feed and restores the rate on the next pass.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
fru_xc_feed_rejection_vs_listings | Cross-channel sibling: Listings Failing Feedonomics Validation. |
fru_rejected_listings | Listing Health sibling: Rejected / Reviewing Listings. |
fru_vat_compliance_gaps | Listing Health sibling: Listings Missing VAT Metadata. |
fru_active_listings | Listing Health sibling: Active Listings (across all locales). |
fru_alert_account_health_drop | Nerve Centre alert: Feed Ingestion / VAT-Gap / Cancel Threshold. |
Reconciling against Fruugo Merchant Portal
Where to look in Fruugo’s own dashboard: Open the Fruugo Merchant Portal and review the feed import history for the latest twice-daily ingestion. The accepted and rejected line counts there are the raw inputs to this gauge. The Portal reports per-import; Vortex IQ rolls the last 24 hours into a single percentage. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Portal shows a single import; this gauge blends both imports in 24 hours | Either | Average the Portal’s two latest imports before comparing. |
| Portal counts warnings differently from hard rejections | Vortex IQ lower | Confirm whether warning lines are treated as failures in your setup. |
| Latest import still processing when the Portal was viewed | Either | Re-check once the Portal marks the import complete. |
fru_xc_feed_rejection_vs_listings to see whether failures start upstream at Feedonomics, and fru_rejected_listings to see which listings the failures removed from sale. Vortex Mind traces a dip back to the specific transform or field at fault.
Known limitations / merchant FAQs
Q: How often does this card update? It refreshes after each of Fruugo’s twice-daily imports, keeping a rolling 24-hour view that blends the two most recent ingestion results. Q: Why might the Fruugo Merchant Portal show a different picture? The Portal reports each import separately, while this gauge blends the last 24 hours into one figure. How warning lines versus hard rejections are counted can also shift the percentage. Q: How does this relate to the sibling cards? This gauge measures the pipe’s overall health;fru_xc_feed_rejection_vs_listings shows whether failures begin upstream in Feedonomics, and fru_rejected_listings shows the listings removed as a result.
Q: Can I customise the alert threshold?
Yes. The default trips below 95%, but you can tighten or loosen it to reflect how much line-level churn is normal for your catalogue and feed.