Case study ยท Brooklyn Botanic Garden

How OG Pilot event remakes could help Brooklyn Botanic Garden unlock $225K in ticket revenue

Day 9 of #100DaysOfOGRemakes looked at Brooklyn Botanic Garden events: bonsai workshops, fall foliage mornings, lightscape walks. The event pages set a mood. The Open Graph images were static snapshots without the date, the time, or a reason to stop scrolling. This remake is a concept generated in OG Pilot. The $225K figure is the scenario's model of a 3ร— click lift on ticket sales, not a reported result from the garden.

The problem: tranquil events, silent previews

A garden photo with no event name looks like a random picture of plants. The reader cannot tell if the walk is this weekend or last season. Generic images omit the timing, so the share has no urgency. The page itself has the details. The crawler cached a file that left them out. People scroll past that card because it does not say what to do or when.

The sample previews on this case study put the event metadata on the image: the name, the date, the place, and a prompt to get tickets. They were built so a team could duplicate the template instead of commissioning a new poster for every listing. See more templates in the gallery, or generate one from a single event URL if you want a file before you connect a domain.

What could change if the card named the event

Ingesting the garden's visual language into a template means each new event fills the same layout. A share can then carry Lightscape, a class, or a seasonal walk with the facts still readable at chat size. The revenue model multiplies visits from those shares and applies a ticket conversion. It is there to make the missing date expensive. It is not a promise that any venue will see that dollar figure.

Retail and audio versions of the same idea: Nike, where the campaign creative never reached the unfurl, and Office Ladies, where the tile was empty. Events are the strictest of the three because a card without a date is actively misleading. Agencies hit this every time a cultural client adds a listing and the old homepage image is still the og:image.

Confirm the live tags

Debug the event URL and read og:title, og:description, and og:image together. A pretty file with the wrong date is worse than a plain one. The API can pass event fields into a signed image URL. MCP lets an agent debug the page or generate a replacement after you create an account for generation. Rails and Astro guides show where that URL should be printed in the layout.