How to respond to frequently asked questions

Here's how to respond to common customer requests. These usually arrive in the form of new contact form submissions but may also be asked by existing customers too.

Can you increase my rate limits?

Here's how we'd break down use cases:

  • if the use case is exporting all the data so they can do further transformation or activation in other tools -> use batch exports
  • if the use case is ultimately going to be accessing our API programmatically with a pre-defined query -> use endpoints product
  • if the use case is essentially wrapping PostHog and allowing the customer to query whatever they want (in other words, if they want a different UI for querying PostHog data) -> use /query API endpoint

See RFC #438 for more context.

Do you have plans to add more hosting options outside of the US and EU?

Right now, no. The vast majority of our customers are happy to host on one or the other, with EU being the preferred domain for GDPR compliance. This is not a "never", just not in the near future.

Do you have a dummy account we can mess around with?

No, the best way to trial PostHog is to start sending your own data into it. When a trial is filled with dummy data, which isn't relevant to the specific team, the overall engagement and success of the trial is lower.

Does PostHog follow the MEDDPICC sales methodology?

Yes! But like everything we do here, it's not what you would expect. At PostHog, MEDDPICC means "Make every deal a delightful PostHog implementation - Charles Cook"

Community questions

Was this page useful?

Questions about this page? or post a community question.