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

  1. Checking that the app is enabled with the correct configuration options in the data pipeline tab. You can find the correct configuration options in the app'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 app 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 app 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 apps that enable you to capture data from other tools. Functionally, these apps 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 it to PostHog. Our tutorials on capturing new RSS items and events from Calendly webhooks 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?

If you're migrating a large amount of data (20 million rows or 10k requests per minute), please contact sales@posthog.com to make sure you aren't rate limited.

When you do a migration, be sure to set the historical_migration value to true like this:

Terminal
curl -v -L --header "Content-Type: application/json" -d '{
"api_key": "<ph_project_api_key>",
"historical_migration": true,
"batch": [
{
"event": "batched_event_name_1",
"properties": {
"distinct_id": "user distinct id",
},
"timestamp": "[optional timestamp in ISO 8601 format]"
}
# ...
]
}' https://app.posthog.com/batch/

See our migration docs for more information.

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.

Questions?

Was this page useful?

Next article

Build an app

Note: You can create apps for both self-hosted and PostHog Cloud, but releasing an app on PostHog Cloud requires a review process. Read more about the review process in the tutorial . We are currently not reviewing new apps while we build a new export system . We will update these docs with more information as that work is completed. PostHog makes it possible to build your own apps and integrate with other platforms. So, if App Store is missing something you need then you may still be…

Read next article