Managing usage
Understand how Knock meters usage across plans and how to manage usage in your account.
Knock plans vary in terms of usage models: notification-based plans meter usage on messages sent, while recipient-based plans meter usage based on monthly notified recipients. Regardless of plan, usage may be accrued in any Knock environment. See our pricing page for current plan pricing and included volumes. Contact support for questions about your Knock plan, or contact sales to discuss enterprise pricing.
Message counts
#A message is counted each time a notification is successfully delivered to a single user on a single channel. A workflow that notifies a user by both email and in-app results in two messages. If a channel step is not executed, there is no associated message. A channel step may be skipped due to user preferences, missing data, or other workflow logic.
Due to the nature of guides, guides usage is metered separately and based on active guides users. A user is considered an active guides user if they have received at least one guide in a given month.
Non-production usage
#While using Knock, you'll often send messages in non-production environments to test changes. To avoid unexpected usage from testing, we recommend using sandbox mode or setting channel conditions in your non-production environments.
Sandbox mode
#When a channel is in sandbox mode, Knock does not pass messages downstream for delivery. Sandboxed messages are rendered for preview in the Knock dashboard, but do not count toward usage.
Enable sandbox mode in a channel's configuration to apply it across an environment, or use the workflow test runner's sandbox setting to apply it for a single run, regardless of how the channel itself is configured.
Channel conditions
#Channel conditions enable you to scope a channel's delivery to specific conditions per environment. For example, you might set a condition on your email channel to restrict sending to recipients on your own domain while in a non-production environment. Unlike sandbox mode, channel conditions gate delivery selectively rather than suppress it entirely. Any message that satisfies a channel condition may contribute to usage.