How to build a weekly feedback digest across products

What goes into a weekly cross-product digest?

A digest is a short summary of the week's feedback across every product you run, written in a form you can read in one sitting. It has three parts: the counts by product and type, the new bugs worth a look, and a note on anything that changed in ratings or status. The digest is not a dashboard. It is a snapshot you write down, so the team can compare one week with the next.

You can build it from the inbox alone, but a single spreadsheet makes the comparison easier, because every product sits in the same table. Escuta Produto gives you that table through a CSV export for each product.

How do you export each product's feedback?

Open each product in the dashboard and use its CSV export. The file is UTF-8, so accents and emoji survive, and it opens directly in Excel and Google Sheets. The filename combines the product's slug with the date, such as acme-notes-feedback followed by the export date, so the files sort themselves when you save them in one folder.

The export has one row per feedback item and these columns: id, created_at, kind, status, rating, message, name, email, page_url, country, source, user_agent and metadata. The status is the current status at the time of export, so the file is a snapshot of today, not a history of changes. Internal notes are not included in the export, so keep the notes in the inbox and use the CSV for counts.

Set one fixed time for the export, such as Friday afternoon. The same time each week keeps the comparisons honest.

How do you combine several exports in a spreadsheet?

Use one of two layouts. The first pastes every product's rows into one sheet and adds a product column, so you can filter or pivot on it. The second keeps one tab per product and adds a summary tab that reads from each one. The first is simpler to maintain. The second is easier to read when the products have very different volumes.

For the first layout, add the product name as the first column before you paste each file, then paste the rows underneath. Convert the created_at column to a real date so you can filter to the last seven days. Then count with a formula like this, where column C holds the kind and column A holds the product name:

=COUNTIFS(A:A,"Acme Notes",C:C,"bug")

Copy the formula across the summary table, changing the product name and the kind. Four products and four kinds make a 16-cell table that fits on one screen.

What should the digest count each week?

Track a small set of numbers and keep them the same every week, so a change means something. A useful set is:

Measure	Why it matters
New items in the last seven days, by product	Shows where attention is going
New bugs, by product	Bugs come first in triage
Ideas still in New	The backlog that needs a decision
Average rating of the week's items	A quick read on how people feel
Items closed this week	Shows the queue is moving

For example, suppose product A got 9 items this week and product B got 2, with 3 bugs between them. The digest makes that visible in one table, and the team can decide whether product A needs a longer slot, instead of guessing from the last alert they remember.

How do you handle the metadata column?

The metadata column holds the JSON you sent with each item, such as a user id, a plan or an app version. In the export it is plain text, so a spreadsheet will not split it into fields for you. If you need a field such as appVersion in the digest, the simplest route is a helper column that extracts the value, or a short script that reads the JSON.

If that sounds like more work than the digest justifies, skip the metadata in the weekly digest and read it only when you investigate a specific item. Metadata earns its place when you ask a question the counts cannot answer, such as whether one app version produces more bugs than the rest.

What does the 15-minute review look like?

Run the review on the same day each week, with the summary table open. Spend the time like this:

1. Three minutes on the counts. Note any product whose new items doubled, and any that dropped to zero.
2. Five minutes on the new bugs. Open each one from the inbox, check the page URL and browser, and decide to fix, plan or write a note.
3. Four minutes on the ratings and the ideas still in New. Look for one idea that repeats across products.
4. Three minutes to write down one decision for next week, such as which product gets the longest slot.

Keep the digest as a single file in a shared folder. Next week, the file tells you what was true last week, which is the comparison that the inbox cannot give you on its own.

Running the export step in Escuta Produto

Export each product from its dashboard page on the same day each week, save the files into one folder named by week, and combine them using the layout you chose. The first run takes longer while you set up the sheet. After that, each week takes the export time plus the 15-minute review.

The notifications guide explains how alerts reach your channel, which is the live signal that sits beside the digest. For a view of how the same products compare by volume and trend, read feedback metrics for a portfolio of products. To decide which product's slot gets the most time each week, read the feedback routine for running five products. The API reference covers the fields if you want to pull feedback into your own script instead of exporting by hand.