Clouted

Measure what your supporting brand pages actually do

A tutorial page and a retail launch page shouldn't have to win on the same metric. Clouted helps teams connect reporting to why each supporting page exists and what the available data can support.

Report against the job of the page

  1. 01Agree the goal for each account

    A product support feed may surface useful questions; a local launch may aim for visits to a store locator. Use the most relevant observable signal.

  2. 02Keep account and business data separate

    Report views and available engagement at post level. Report tagged visits, leads, or purchases separately when the destination system supports them.

  3. 03Use reporting to change the calendar

    Compare formats over similar periods and look for questions that still need answers. Document what the team will change and how to check it.

Frequently asked questions

Can we combine page and official account metrics?

Report a labeled rollup if useful, but don't sum views as unique people. Keep each account's goal visible.

Can social page views prove product sales?

No. Use observable referrals or supported attribution and explain what isn't measured.

What if platforms use different view definitions?

Keep their original definitions and note the difference before comparing outcomes.

What can we report after handover?

Agree who retains access to account analytics, post history, and reports before the transition.

Plan brand social page reporting