No. SleekPixel reads the ig_campaigns and ig_campaign_meta tables that ship with the free Email Subscribers plugin. The Pro version adds extra fields like UTM parameters and tracking pixels, which SleekPixel can render if you choose, but the base archive image works on the free version with no API key.

Generated images write to uploads/sleekpixel/email-subscribers/{campaign-id}.png under your standard WordPress uploads directory. The file path is fully predictable, so you can include it in a CDN cache warmup script or audit which campaigns have rendered at any time without consulting the admin.

Editing the row in ig_campaigns triggers SleekPixel to invalidate the cached PNG via the save_post hook chain. The next request, whether from a Twitter unfurl bot or a human refresh, regenerates the image with the new subject. The canonical URL does not change, so existing shares still resolve to the updated card.

Yes. The template field for segment size accepts either a static number, a custom field on the campaign row, or a SQL fragment that runs against ig_contacts with the campaign list_ids applied. Results are cached alongside the PNG so the count does not run on every social crawler hit, only on regenerate.

When list_ids contains more than one segment, the rendered footer reads the combined unique contact count by default. You can switch to showing the largest segment name plus a small overflow indicator like plus 3, or to listing every segment name comma separated, depending on the template you pick.

Clearing the WordPress object cache does not by itself wipe the PNG cache, because the PNG is a file on disk rather than a cache key. To force regeneration use the SleekPixel admin clear button, the WP-CLI command sleek pixel clear, or simply edit the ig_campaigns row, which invalidates the file automatically.

Drip and onboarding sequences from Email Subscribers store each step as its own row in ig_campaigns with a parent sequence ID. SleekPixel treats each step as an individual campaign for image purposes, so a five-step sequence produces five PNGs, each with the step name as headline and the sequence name as subhead.

Yes. SleekPixel registers a sleekpixel_image field on the rest API response for any post type or table it has a template for. Headless front ends consuming the Email Subscribers archive over REST receive the absolute image URL as part of the campaign payload without an extra request.