Troubleshooting and FAQs

Last updated:

|Edit this page

My connector isn't working, what do I do?

  1. Checking that the connector is enabled with the correct configuration options in the data pipeline tab. You can find the correct configuration options in the connector's documentation by searching for it in the destinations, transformations, or filtering sections of the docs.

  2. Click "Logs & metrics" and go to the Metrics tab to check that the connector is processing events without errors.

  3. Check the Logs tab to see if there are any errors.

  4. Go to the data management tab to check if there any ingestion warnings.

  5. If the connector relates to an external service, check that the external service is working correctly. Make a request to the relevant API endpoint. You can also use a tool like webhook.site to check that PostHog sends events as expected.

How do I capture data from another application?

We deprecated the functionality of PostHog connectors that enable you to capture data from other tools. Functionally, these connectors were a cron which ran every minute (or more) and pulled data from another tool.

There are two options for recreating this functionality:

  1. Set up a cron of your own. You can use a tool like val.town to easily set up scheduled tasks that capture data from other tools and send them to PostHog. Our tutorials on capturing new RSS items, events from Calendly webhooks, and GitHub stars are examples of this.

  2. Use our data warehouse. PostHog's data warehouse enables you to import and use data from platforms like Stripe, Hubspot, and Postgres natively in PostHog. See our docs for more information.

How do I track when users do an event for the first time?

There are a few ways to capture a user doing an event for the first time. We cover a few of these in our tutorials on tracking new and returning users and first touch attribution.

  • Create a cohort matching users who have done an event for the first time recently.
  • Use a custom event to set a person or event property. For example, you can set a first_seen property with the $set_once option.
  • Use HogQL to query for the min(timestamp) of an event.

How do I migrate events or rows into PostHog?

See our migration docs for the full details.

How do I do real time exports?

We don't currently support real time exports.

If you need more than the hourly interval batch exports and are on the enterprise plan, please contact our team (or email sales@posthog.com).

If you're not on the enterprise plan, check out our webhook issue on GitHub.

Where are my missing events?

See our troubleshooting guide for events not appearing in a project.

Why can't I use the UI or events API to export data?

You can, but they are rate-limited. Batch exports should be your default. The table below compares the options:

MethodWhen?Limitations
PostHog UI - click "Export" on the events tableYou need to export a small number of events3,500 events
Events APIGreat for one-off smaller exports1 day date range and 3,500 events
Batch exportsYou need to export a large number of events, can be used for continuous exportsNo limits

If that isn't clear enough, here's a decision tree you might find useful:

Yes
No
Yes
No
Do you need to export more than 3,500 events?
Use batch exports
Do you need to run regular exports e.g. once a day or once a week?
Use the PostHog UI or the Events API

Questions?

Was this page useful?

Next article

Build a transformation or destination

Transformation and destination enable you to define custom pipeline behaviors in PostHog. Transformations enable you to add more information to an event or modify existing properties. They act on single events coming into PostHog. The output of one goes into the next, creating a chain. Destinations enable you to export data to other services. They operate at the end of the pipeline in parallel with each other at the same time data is being written to ClickHouse. Example of an…

Read next article