> For the complete documentation index, see [llms.txt](https://thecontentforge.gitbook.io/thecontentforge-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/patterns.md). # Patterns Patterns surfaces what's actually working in your content over time. Instead of staring at individual post metrics, you see the recurring formats, hooks, and topics that drive performance. Open it from **Intelligence > Content Optimization > Patterns**. ### What it shows Analysis is broken down **per platform**, so you can see what works on each channel rather than a blurred average across all of them. Within each platform you get a set of tabs: * **Hook Templates** - the opening structures that consistently win, ready to reuse * **Length Performance** - how post length maps to engagement, so you know when to keep it short or go long * **Topics** - which subjects your audience responds to most * **CTAs** - which calls to action actually drive action * **Features** - how specific elements (media, links, questions) affect performance * **Drift** - how your patterns are shifting over time, so you catch changes early * **Top Posts** - your standout performers for the period, with what made them work Alongside the tabs you also get: * **Cashtag, mention and hashtag cards** - side-by-side comparison of how `$` cashtags, `@` mentions and `#` hashtags affect reach and engagement * **What's Working Now** - a plain-English summary of your current winning patterns at a glance * **Optimal formula** - a recommended recipe combining your best-performing hook with the topic mix most likely to land ### How it works Patterns analyzes the analytics ingested through [Data Ingestion](/thecontentforge-docs/feature-guides/data-ingestion.md), reading across your full post history so what you see reflects genuine recurring winners rather than one lucky post. ### Workflow 1. Open Patterns after a fresh weekly upload 2. Note the 2–3 strongest formats or hooks for the period 3. Bring those into your next planning session 4. Run an [Experiment](/thecontentforge-docs/feature-guides/experiments.md) on anything you're unsure about ### Tips * Patterns gets smarter with more data - give it at least 4–6 weeks of ingested analytics before drawing strong conclusions * Don't over-fit. A format that wins for two weeks isn't a guaranteed third-week winner * Use Patterns to *start* the conversation about content direction, not end it --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/patterns.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.