When you run a founder account and a business account, a promising post can disappear into whichever platform you checked last. Our cross-channel analytics work aimed to make comparison easier across channels and organizations, so the team could decide what deserved another version.
Progress update from 24 July 2026. Several analytics and custom-view refinements were in development; external MCP access was not established as publicly available. Linked guides describe today's product.
TL;DR
Clipflow updates
- Analytics refinements covered date ranges, platforms and different post types.
- Custom views were being extended across multiple organizations, with parent and child project filtering.
- Internal tools for project overview, channel lookup and post creation were groundwork for further agent workflows.
Putting it to work
- Compare a similar period and content type before deciding a channel is working better.
- Use promising posts as evidence for a new brief, rather than copying a headline metric into the strategy.
Ask a specific question of the numbers
Imagine you operate a hospitality business and also publish through the founder's account. A behind-the-scenes clip attracts attention on one account, while a straightforward explanation of booking gets questions on the other. Both may be useful, but they are doing different jobs.
Start with a period you can compare fairly. Look at the format and channel, then open the posts that stand out. The analytics guide explains how to explore those results in the current product.
An overview spanning accounts lets people compare results without sharing passwords. The team can identify an interesting post together, then return to its actual content to understand what happened.
Ask whether the opening, subject or example made the difference. For the booking explanation, useful questions might be more valuable than broad reach. For the behind-the-scenes clip, attention may justify a follow-up that explains the offer more clearly.
Platforms expose different information for different post types. A missing metric is not evidence that nobody took that action. Avoid treating a cross-platform overview as though every source provides an identical set of measurements.
Turn the finding into work someone can own
Create a follow-up brief tied to the useful idea. Ask the editor for a different opening, a clearer demonstration or an answer to a question raised in the comments. That is a concrete assignment, unlike asking for more content that performs well.
Custom-view development was intended to help teams see relevant projects across organizations. Use a view around the work that needs attention, keeping the brand and responsible person clear.
Internal agent tools were another part of the week's progress. Their existence did not mean customers could connect an external MCP client that day. For current in-app agent capabilities, use the AI Agents guide.
This week: AI security and ease of use both matter when introducing a powerful system. For content teams, the practical test is whether the shared view makes the next decision clearer without hiding the context behind it.
Subscribe to the Clipflow YouTube channel for more updates here.
Follow Ken on Instagram here.
Follow Darrell on Instagram here.
