Posthog Release Notes

We’ve upgraded our account security with several two-factor authentication (2FA) features:

• Updated 2FA setup and verification
• Organization-level 2FA requirements for all members
• Session-based 2FA verification with configurable enforcement
• 2FA bypass for domains with SSO enforcement
• Support for switching between organizations when 2FA is required

Check out your PostHog settings to set up and configure 2FA.

We’ve added Meta Ads as a supported data source for marketing analytics. You can pull campaign and performance data – like clicks, impressions, costs, and reported conversions – directly from Meta Ads into PostHog to create insights.

Configure who can access an insight or dashboard in the Access control panel. Within dashboards, users will only see data for insights they have permission to view, even if they have access to the dashboard.

Want to see if your ads are increasing shareholder value? If you run ads on LinkedIn or Reddit, you can now import them as a data source. Connect them as a source in data pipelines.

Automatically create new GitHub issues when error tracking reports a new issue using the alerts feature. You can create templates to customize the title, description, and PostHog issue ID.

When joining two tables, a test query will be performed first to surface potential issues. This validation step will:

• Surface any errors from this test query
• Warn you when key column types don't match
• Warn you if the query doesn't return any rows

Errors will block you from performing joins, but not warnings.

You can now export heatmaps to a PNG, use the built in editing tool to highlight important areas, and use them to write “I told you so” messages to your coworkers. We also shipped a handsome new UI. If you haven’t tried heatmaps, enable the feature preview.

Sometimes rapid clicks are signs of excitement, not rage. You can now exclude elements from rageclick detection using the new .ph-no-rageclick class, letting you filter out false positives like clicking "next" or "previous" buttons too quickly. We've also added a rageclick configuration with a css_selector_ignorelist setting to our JS web SDK. You can use it to create a custom list of CSS selectors to exclude, giving you more control over which elements trigger rage clicks.

You can mark certain funnel steps as optional. These steps will still appear in your insights, but users who skip them won't be excluded from the downstream analysis. Click on the three dots menu besides a funnel insight step to mark it optional.

If you’re looking for an issue that started appearing on a specific date, or you’re tracking down a problem caused by a recent release, you can filter by issues first seen. This lets you filter by first seen date ranges and exact dates.