Yes. The Pro data-source extension stores its config in the same _ninja_table_settings postmeta. SleekPixel reads the source type, source URL, and refresh interval from that meta and surfaces them as template fields, so you can show a 'Google Sheet' or 'SQL' badge depending on the data source.

SleekPixel parses both. The Gutenberg block stores the table id in its table_id attribute and the shortcode stores it in the id attribute. Either way, the same lookup runs and the same fields populate the OG image.

Ninja Tables fires an action on every successful refresh. SleekPixel hooks that action, identifies every post that embeds the refreshed table id, and queues an OG image regeneration in the background so the morning shares already show the new row count.

Yes. SleekPixel exposes the first row of data and any cell by row/column index as template fields. You can render the header row, the first three cells of the top row, or a specific column like 'Total' at the bottom of the dataset.

Use the Ninja Tables category taxonomy or a custom field on the CPT entry as a routing field. SleekPixel templates can switch accent color, badge text, and layout per category without duplicating the template file.

No. Regeneration runs asynchronously through Action Scheduler. The save returns immediately and the image rebuilds in the next queue tick, typically within a few seconds, with no blocking on the admin save action.

By default, SleekPixel skips drafts and only renders for published tables, since drafts are not shareable in public posts. You can opt in to draft rendering for staging environments through the integration settings page.

Locally first, then your existing CDN picks up the file from wp-content/uploads/sleek-pixel/ like any other media. There is no external SleekPixel CDN and no per-render fee.