The useful takeaway
A public preview helps you evaluate an experience. Your agreed product scope determines what is available to your organization.
Resource library / A more practical starting point.
The expanded library brings use cases, sample briefings, measurement definitions, editable templates and integration planning into one place. Start with the decision you need to make, then move to an example or working tool. The material is designed for evaluation without requiring access to private customer information.
For editorial teams, the sample briefings show the separation between observation, interpretation and action. For product teams, the Integration Guide provides a scope and acceptance framework. For commercial teams, the sponsor recap and evaluation scorecard help make the evidence behind a recommendation visible.
Product naming / Meet Briefing.
Briefing is the shorter name for the product previously presented as Narrative Briefing. The public navigation and product descriptions now use Briefing. Existing product links continue to point to the same experience.
The product story remains focused on a decision-ready read: what changed, why it may matter, the supporting evidence and the next action. See Sample Briefings for fictional examples of that structure, or explore the product showcase to discuss the experience you would want for your team.
How to read availability language.
A feature description explains an intended job. A public preview demonstrates an experience. A customer rollout requires the relevant scope, source access and delivery arrangements to be agreed. These are different stages, and a product page should not be treated as a substitute for your engagement terms.
This page covers public-facing product and website changes. It does not publish internal roadmaps, customer deployments, service guarantees or release dates for unannounced capabilities. Check Status for public service communications and contact Support for an issue affecting your account.
Follow the changes relevant to your work.
Keep the product question specific when asking about an update: name the experience, the source coverage you need and the destination you want to use. That makes it easier to distinguish a presentation change from a change that affects your workflow.
Use the product-update signup in the site footer if you would like to receive published news. For an active evaluation, contact the team with your existing brief so new information can be assessed against the criteria you already agreed.
References & further reading
Examples are illustrative unless explicitly identified as source observations. Availability depends on approved sources and customer configuration.
Social Intel / Read the source alongside the result.
The public Social Intel experience lets you inspect a bounded post sample alongside available metrics and source context. Use it to evaluate whether the presentation helps your team ask better questions. Read the stated sample and calculation before interpreting a rank or rate.
The preview is not a promise of complete historical coverage or every platform metric. If your use case needs account-specific history, repeated observations or a particular output, define those requirements explicitly during evaluation. The Measurement Guide explains why these distinctions matter.