• Product
  • Pricing
  • Docs
  • Using PostHog
  • Community
  • Company
  • Login
  • Table of contents

  • Handbook
    • Start here
    • Meetings
    • Story
    • Team
    • Investors
    • Strategy overview
    • Business model
    • Objectives
    • Roadmap
    • Brand
    • Culture
    • Values
    • Small teams
    • Goal setting
    • Diversity and inclusion
    • Communication
    • Management
    • Offsites
    • Security
    • Brand assets
    • Team structure
    • Customer Success
    • Exec
    • Experimentation
    • Growth
    • Infrastructure
    • Marketing
    • People & Ops
    • Pipeline
    • Product Analytics
    • Session Recording
    • Website & Docs
    • Compensation
    • Share options
    • Benefits
    • Time off
    • Spending money
    • Progression
    • Training
    • Side gigs
    • Feedback
    • Onboarding
    • Offboarding
      • Product Manager ramp up
    • Merch store
      • Overview
      • How to interview
      • Engineering hiring
      • Marketing hiring
      • Operations hiring
      • Design hiring
      • Exec hiring
      • Developing locally
      • Tech stack
      • Project structure
      • How we review PRs
      • Frontend coding
      • Backend coding
      • Support hero
      • Feature ownership
      • Working with product design
      • Releasing a new version
      • Handling incidents
      • Bug prioritization
      • Event ingestion explained
      • Making schema changes safely
      • How to optimize queries
      • How to write an async migration
      • How to run migrations on PostHog Cloud
      • Working with ClickHouse materialized columns
      • Deployments support
      • Working with cloud providers
      • How-to access PostHog Cloud infra
      • Developing the website
      • MDX setup
      • Markdown
      • Jobs
      • Overview
      • Data storage or what is a MergeTree
      • Data replication
      • Data ingestion
      • Working with JSON
      • Query performance
      • Operations
        • Overview
        • sharded_events
        • app_metrics
        • person_distinct_id
    • Shipping things, step by step
    • Feature flags specification
    • Setting up SSL locally
    • Tech talks
    • Overview
    • Product metrics
    • User feedback
    • Paid features
    • Releasing as beta
    • Our philosophy
    • Product design process
    • Designing posthog.com
    • Overview
    • Personas
    • Testimonials
    • Value propositions
      • Content & SEO
      • Sponsorship
      • Paid ads
      • Email
      • Press
    • Growth strategy
    • Customer support
    • Inbound sales model
    • Sales operations
      • Managing our CRM
      • YC onboarding
      • Demos
      • Billing
      • Who we do business with
    • Growth reviews
  • Table of contents

  • Handbook
    • Start here
    • Meetings
    • Story
    • Team
    • Investors
    • Strategy overview
    • Business model
    • Objectives
    • Roadmap
    • Brand
    • Culture
    • Values
    • Small teams
    • Goal setting
    • Diversity and inclusion
    • Communication
    • Management
    • Offsites
    • Security
    • Brand assets
    • Team structure
    • Customer Success
    • Exec
    • Experimentation
    • Growth
    • Infrastructure
    • Marketing
    • People & Ops
    • Pipeline
    • Product Analytics
    • Session Recording
    • Website & Docs
    • Compensation
    • Share options
    • Benefits
    • Time off
    • Spending money
    • Progression
    • Training
    • Side gigs
    • Feedback
    • Onboarding
    • Offboarding
      • Product Manager ramp up
    • Merch store
      • Overview
      • How to interview
      • Engineering hiring
      • Marketing hiring
      • Operations hiring
      • Design hiring
      • Exec hiring
      • Developing locally
      • Tech stack
      • Project structure
      • How we review PRs
      • Frontend coding
      • Backend coding
      • Support hero
      • Feature ownership
      • Working with product design
      • Releasing a new version
      • Handling incidents
      • Bug prioritization
      • Event ingestion explained
      • Making schema changes safely
      • How to optimize queries
      • How to write an async migration
      • How to run migrations on PostHog Cloud
      • Working with ClickHouse materialized columns
      • Deployments support
      • Working with cloud providers
      • How-to access PostHog Cloud infra
      • Developing the website
      • MDX setup
      • Markdown
      • Jobs
      • Overview
      • Data storage or what is a MergeTree
      • Data replication
      • Data ingestion
      • Working with JSON
      • Query performance
      • Operations
        • Overview
        • sharded_events
        • app_metrics
        • person_distinct_id
    • Shipping things, step by step
    • Feature flags specification
    • Setting up SSL locally
    • Tech talks
    • Overview
    • Product metrics
    • User feedback
    • Paid features
    • Releasing as beta
    • Our philosophy
    • Product design process
    • Designing posthog.com
    • Overview
    • Personas
    • Testimonials
    • Value propositions
      • Content & SEO
      • Sponsorship
      • Paid ads
      • Email
      • Press
    • Growth strategy
    • Customer support
    • Inbound sales model
    • Sales operations
      • Managing our CRM
      • YC onboarding
      • Demos
      • Billing
      • Who we do business with
    • Growth reviews
  • Handbook
  • Marketing
  • Marketing channels
  • Sponsorship

Sponsorship

Last updated: Oct 17, 2022

On this page

  • Developer influencers
  • Commercial sponsorship
  • Copy bank
  • Charitable sponsorship
  • Open source sponsorship
  • Projects we sponsor regularly
  • Request sponsorship

We do three types of sponsorships - commercial, charitable, and open source. Our objectives with commercial sponsorships are to:

  • Enhance word of mouth - this is our most effective acquisition channel
  • Reach more relevant communities, especially those users that are not active on social media
  • Make more effective use of our budget in less popular channels

Measuring attribution directly is basically impossible with sponsorship activities, so we try hard to make sure we are targeting the right channels by validating opportunities properly first. One way we do this is to ask engineers on the team who are close to our target user for their personal recommendations for content they know and like.

Developer influencers

We are trying out developer influencers as a new channel in Q4 2022 to figure out if this could be a fruitful channel for us to reach a new audience. We are working with Yard, an agency, to partner with YouTube creators with relevant audiences. If this experiment goes well, we will do more here (and update this page with what we've learned does and doesn't work well).

Commercial sponsorship

We currently sponsor a mixture of newsletters and podcasts. We did a big burst of sponsorship activity in Q2 and Q3, and are now just doing a small number of ongoing newsletter sponsorships.

You can view the sponsorship tracker here (internally public only).

Copy bank

We maintain a sheet here of various types and lengths of copy that we use for our campaigns - if you end up creating new copy, please add it to this sheet!

Charitable sponsorship

We are looking to partner with charities who are aligned with our mission of increasing the number of successful products in the world. These partners are likely to focus on giving greater access to under-represented groups in tech.

We currently sponsor:

  • Django Girls - $500/month

Open source sponsorship

PostHog is an open-source product analytics platform built on top of many other amazing open-source projects. We believe in open-source and the open-core model. However, many open-source projects go underfunded.

We are investing in open-source, not just as a business, but directly via sponsorship in key projects we benefit from every day. We're doing this for three reasons:

  1. We want valuable open-source projects to continue to be maintained and enhanced
  2. We fundamentally rely on some open-source projects, and it's essential they continue to be maintained and enhanced
  3. We believe the PostHog brand will benefit from the sponsorship

In addition to sponsoring key projects, we also provide a $100/month budget for every team member to sponsor projects that have helped them.

Projects we sponsor regularly

Project we useAuthorWhy does PostHog sponsorSponsored viaAmount/month
rrwebyz-yuPowers our session recording functionalityGitHub Sponsors$100
graphile/workerbenjiePowering scheduled jobs, retries and other logic for the plugin-serverGitHub Sponsors$100
Django REST FrameworkencodePowers the PostHog REST APIsDirectly$400
Webdriver manager for pythonSergeyPirogovPowers parts of our subscriptions and exportsGitHub Sponsors$15
alexwooormWe use it for improving the content we writeGitHub Sponsors$5

Request sponsorship

If you know of a project that is fundamentally important to PostHog, add the project to this page via an edit page suggestion/pull request. We'll then assess the proposal. If we decide to sponsor, we'll set up the sponsorship via either Open Collective or GitHub. Finally, we'll merge the pull request.

Questions?

Was this page useful?

Next article

Paid & SEO

As we believe in product-led growth , paid ads are not at the heart of our marketing strategy in the long term. Instead, we see them as an important way to kick start and then amplify the work we are doing in other areas of marketing and product. We work with an agency, Hey Digital to manage paid ads. Specifically, they help us with: Paid ad tactics and monthly media plan Creating paid ad assets for each channel Manage paid channels on our behalf We communicate with them via a shared…

Read next article

Authors

  • Charles Cook
    Charles Cook
  • Paul D'Ambra
    Paul D'Ambra
  • leggetter
    leggetter

Share

Jump to:

  • Developer influencers
  • Commercial sponsorship
  • Copy bank
  • Charitable sponsorship
  • Open source sponsorship
  • Projects we sponsor regularly
  • Request sponsorship
  • Questions?
  • Edit this page
  • Raise an issue
  • Toggle content width
  • Toggle dark mode
  • Product

  • Overview
  • Pricing
  • Product analytics
  • Session recording
  • A/B testing
  • Feature flags
  • Apps
  • Customer stories
  • PostHog vs...
  • Docs

  • Quickstart guide
  • Self-hosting
  • Installing PostHog
  • Building an app
  • API
  • Webhooks
  • How PostHog works
  • Data privacy
  • Using PostHog

  • Product manual
  • Apps manuals
  • Tutorials
  • Community

  • Questions?
  • Product roadmap
  • Contributors
  • Partners
  • Newsletter
  • Merch
  • PostHog FM
  • PostHog on GitHub
  • Handbook

  • Getting started
  • Company
  • Strategy
  • How we work
  • Small teams
  • People & Ops
  • Engineering
  • Product
  • Design
  • Marketing
  • Customer success
  • Company

  • About
  • Team
  • Investors
  • Press
  • Blog
  • FAQ
  • Support
  • Careers
© 2022 PostHog, Inc.
  • Code of conduct
  • Privacy policy
  • Terms