What is Census's monetization strategy or revenue model?

It's a straightforward SaaS-based subscription. We've done a couple of different iterations of it in the past. It's largely based on the scope of customers' use cases. We use a couple different metrics as a proxy for that, but really what we're trying to do is understand how many different teams we impact as part of the integration, so it loosely scales with your usage of additional destinations. It's not explicitly, "Hey, if you're opting into Salesforce, then it's plus one destination"; it's based on the number of fields that we're updating. But you can think of it as: the more destinations, the larger the package. Then there are more professional services, like enterprise logging, SSO auditing, etc., that you get in higher tiers. It's a fairly standard SaaS-space subscription model.