Skip to main content
Use this catalog to explore message definitions and their current known configuration, including messages that have no performance yet. Use daily message performance for engagement and attributed revenue.
  • Grain: One row per (sm_store_id, source_system, message_id).
  • Identity: message_identity_kind distinguishes a native send, a reusable message definition and a reporting group. These represent different things; counting catalog rows does not count delivered messages.
  • Refresh: The whole catalog refreshes, so changes to older definitions can appear. This is current known configuration, not a history of every edit.
  • Coverage: Includes available definitions from configured Klaviyo, Postscript, HubSpot and Omnisend sources. Available fields differ by provider, and missing metadata remains unknown. Postscript rows retain their reporting-group identity; HubSpot publication and Omnisend workflow definitions do not establish a recipient delivery.

What to explore

Compare the mix of campaigns, flows and message channels; inspect audience labels and segment counts; and find which definitions have variation or experiment settings. These settings describe how a test was configured. They do not establish a winning variant or causal lift.

Join to performance

Join using all three catalog keys. A native provider ID alone is not a cross-provider or cross-store key. Existing daily performance covers Klaviyo and Postscript; a catalog entry for another provider does not add that provider’s performance to the report.

Interpretation limits

A subject stays unknown when variations are missing or disagree. Scheduled times for recipient-local or optimized sends may be reference times rather than a single global send time. Provider experiment percentages can describe different allocations, so check provider_ab_test_percentage_kind before comparing them. Catalog metadata does not establish recipient-level exposure, actual delivery windows or historical configuration at the time of an event.

Columns