Use a supported_destinations JSON column per tool, where each entry includes a destination slug, sync modes available, supported objects, audience compatibility, and identity field mapping depth. The destinations sheet drives per-destination pages that join every tool supporting the destination, with each tool's per-destination metadata exposed in the row.

A sync_modes JSON column carries values like upsert, insert, update, delete, mirror, and append. Per-tool pages render a chip grid, and a /reverse-etl/{destination}/ page can show a per-mode matrix across tools so readers see which tool offers mirror sync to Salesforce versus only upsert and insert.

Yes. The destinations sheet has its own ranking and verdict per destination. Per-tool pages handle solo views, and the destination ranking drives the ordered list on each /reverse-etl/{destination}/ page. Empty rankings can fall back to a templated rank derived from columns like field-level mapping depth and audience compatibility.

A warehouse_native column with values like yes, partial, and no captures whether the tool runs sync logic in the warehouse versus in its own infrastructure. The template renders a badge and a tone class, and a /reverse-etl/warehouse-native/ subset page can rank platforms for teams that need the sync to never leave the warehouse boundary.

Yes. A pricing_model enum supports values like mar_based, destination_based, capacity_based, and quote_only. The template renders the structured value as a badge and the pricing_note exposes the vendor's wording, so readers see honest framing instead of a forced dollar-per-record figure.

Add a status column with values like active, acquired, discontinued, and merged. The template renders a banner via selector mapping when status is not active, and the page can either stay live with a historical note or 301 to the closest active alternative based on a recommended_replacement column.

Yes. Map an image URL column to og:image via the meta type, so each per-tool page renders its own social card. For per-destination pages, the template can compose a destination badge OG. Pairing with SleekPixel lets the OG render on the fly from row data, overlaying tool name, destination count, and warehouse-native flag on a styled background.

Use an identity_resolution column with values like deterministic, probabilistic, hybrid, and not_supported, plus a free-text identity_note. The template renders the structured value as a badge and exposes the vendor's wording, so readers compare identity capabilities across tools without conflating different approaches.