Analytics & reporting

Proof the program is working

Engagement, contributions, and care: the numbers a program takes to council.

Reporting in the Civic Collection admin

A living guide is also a record of its use

Every visit, tour, and contribution is a signal the collection is being found and used. The guide gathers those signals into a picture you can hand to a council or a funder. No spreadsheet of your own to keep.

An engagement summary in the admin

Three things a program has to answer for

Is it being found, is the community engaged, is it being cared for?

  • Reach and engagement

    Visits, artworks viewed, tours taken, and saves: evidence the collection is reaching people, not sitting quiet.

  • Community activity

    What people are photographing, flagging, and proposing, drawn from the moderation queue.

    Explore community contributions →
  • Care and condition

    Condition and maintenance posture across the collection, ready for the reporting percent-for-art funding expects.

    Explore collections management →

Council-ready, not spreadsheet-ready

The numbers come out of the guide already shaped for the audiences that matter: a council presentation, a funder's report, a percent-for-art obligation. Defend the budget you have and make the case for the one you want.

See a live guide →
A reporting summary shaped for a council update

Built for the people who defend the program

Metrics that respect the audience and the collection.

  • One place, not three

    Reach, participation, and care in a single view, not stitched together from separate tools.

  • Measured with respect

    Aggregate patterns over individual tracking: privacy-respecting by default.

  • Yours, in full

    Every record and its history exports at any time. We don't hold your collection hostage.

  • No analyst required

    Pull the numbers yourself, through the same simple admin your team already publishes with.

FAQs

What can you actually measure?

Reach and engagement (visits, artworks viewed, tours taken, saves), community contribution activity from the moderation queue, and the condition and care posture of the collection.

Is this available today?

Analytics is built into the demo environment, and it's the part worth seeing live. Book a demo and we'll walk through the reporting on a real collection, so you see exactly what a program gets.

Do you track individual visitors?

No. Reporting is built on aggregate patterns, not individual tracking: privacy-respecting by default, in keeping with how public-sector guides should treat the people who use them.

Can we use it for council or percent-for-art reporting?

That's what it's for. The numbers come shaped for a council update, a funder's report, or a percent-for-art obligation: evidence the collection is being found, used, and cared for.

Do we need a developer or an analyst?

No. The reporting lives in the same simple admin your team already uses to publish: no developer in the loop, no separate analytics tool to learn.

Do we own the data?

Always. Your catalog and its history are yours, exportable in full at any time.

Ready to make the case for the collection?

Analytics is best seen live. We'll walk you through it.