The Criteo OneTag integration for WooCommerce fires viewItem, viewBasket, and trackTransaction events from Woo pages, and maps products to Criteo's product feed via meta. Partner ID, account ID, and audience config live in wp_options (typically woocommerce_criteo_settings), while per-product audience or category overrides live in postmeta on product posts. The default admin shows a single settings screen and no per-product audit.

SleekView reads product posts and joins the Criteo-specific postmeta keys so a marketing audit can show SKU, category, audience override, and whether the product is excluded from the Criteo feed. A second view joins wc_orders with the order-time meta that captures whether the trackTransaction event fired successfully, so finance and growth see match coverage in the same table where orders live.

Inline edits go through WooCommerce CRUD, so changing an audience override on a product fires save_post_product and the plugin's filter that decides which audience tag to emit. Bulk-mark hundreds of clearance products as excluded from the Criteo feed in one pass instead of clicking into each one.

Criteo's value depends on tag coverage being clean: viewItem fires on product pages, viewBasket on cart, trackTransaction on the order-received page, and product feeds carry the right audience mapping per SKU. When any of those slip, attribution silently degrades and the ad team only notices weeks later in a Criteo dashboard. The default WooCommerce-Criteo integration ships a settings screen for the account credentials and not much else, so audit work means writing SQL or opening products one at a time.

SleekView turns the audit into a list view, with audience override, feed inclusion, and order-time tag-fire status as columns. Paid acquisition catches missing audience overrides before the quarterly review, analytics catches missing trackTransaction events before they become a reconciliation problem, and finance gets a clean view of Criteo-attributed revenue alongside the rest of the wc_orders data. None of this requires patching the plugin.

SleekView reads the meta the plugin already writes and surfaces it where the ops team can act on it.