PostHog Handbook Library / Marketing

481 words. Estimated reading time: 3 min.

# Social media

> Got a launch, Beta, GA, or project you want promoted on social? Tag Liam Graham in Slack and use the checklist below to give him the information he needs.

### Who controls our social accounts

Liam Graham owns and runs PostHog's main social media accounts. If you need something posted from an official account, want a reply sent from one, or have a question about our presence on a platform, he's your point of contact.

When we promote a launch on social, Liam Graham needs a handful of things to turn it into great posts.

### What to share

In the initial (or second) message you share about a launch, Beta, GA, or project, add this bullet list where you'd normally tag Liam Graham:

- ELI5 of what's getting promoted, and how you want it presented on social.
- Messaging doc(s). Do you have email copy that lives somewhere? A general messaging doc? Send both if you have them.
- Link(s) to the main video or photo asset(s). As a gentle reminder, 4:5 aspect ratio is best for graphics and photos, and 9:16 is best for video.
- Link(s) to the blog article, if we've got one.
- When should the first post on social go live?
- Confirm the OpenGraph image is updated on the product page. See OpenGraph images below.

That's the whole ask. If something doesn't apply (for example, there's no blog post yet), just say so.

### Where and when to send it

You should aim to give as much notice as you can, but ideally at least a week. You can share the checklist in either of two places:

- A widely broadcast Slack message you're already sending out about the launch.
- Post in either the #team-marketing or #team-editorial Slack channels

In both cases, tagging Liam Graham.

We want to make sure we're being transparent with this, so you should avoid sending this information by DM.

### OpenGraph images for product pages

Every _product_ page should have a custom OpenGraph (OG) image, so that when someone shares a link on social media it shows a purpose-built visual rather than defaulting to the website homepage image or, worse, showing up as a missing image.

- What's needed: a custom OG image for each product page. This is an art request rather than a copy request, so there's usually no messaging doc to go with it.
- Good examples: the Feature Flags and Session Replay product pages already have working OG images that render correctly. Use these as a reference for what we're aiming for.
- Design guidance: because these render on small screens, keep designs and copy simple – bright colors and chunky text work best.
- Check your work: paste the product page URL into opengraph.xyz to preview how the OG image renders across platforms.

If you can sort the OG image yourself for a product as you pick up assignments, that's one less thing to coordinate.

Canonical URL: https://posthog.com/handbook/marketing/social-media

GitHub source: contents/handbook/marketing/social-media.md

Content hash: `8d5631b2ce329381`

Static reader notes

- `MDX_COMPONENT_STATIC_ADAPTER`: Adapted interactive MDX components for static reading: TeamMember.