What will you do with this file?
``` The button opens the idea type. Ideas are the right type here, because the most common answers describe a missing destination, format or filter. Bugs belong in a separate place, so a person who says the file is broken can use the bug type from the normal feedback button. ## How do you record the export type as metadata? Pass the export type and format to `setMetadata` before the widget opens. Store the kind of data, the format and the number of rows, so you can read reports by export without guessing from the message text. Do not store the file name if it contains a customer name or a company name. ```js function onExportReady(exportJob) { if (!window.EscutaProduto) return; window.EscutaProduto.setMetadata({ event: "export_download", exportType: exportJob.type, format: exportJob.format, rowCount: exportJob.rowCount, }); } ``` The export type should be a stable name, such as "transactions" or "contacts", not the label on the button. Labels change, and the stable name is what lets you compare reports across months. ## What do export answers reveal? Read the answers in clusters. Requests to send the data to another tool point to an integration or a webhook. Requests to open the file in a spreadsheet point to a format, a column order or a filter the product lacks. Requests to share the file with someone who does not have an account point to sharing or a read-only link. Requests to keep a backup point to scheduled exports. Count distinct accounts for each cluster, and note the export type in the spreadsheet. If most of the requests come from one export type, the gap is probably specific to that data. If they come from all types, the gap is in the export process itself. Escuta Produto does not connect to other tools, so an integration request is a product decision you make from the cluster, not a feature the widget offers. The [guide to the feature request or bug decision](/resources/feature-request-or-bug) helps when an export request reads more like a defect than a missing feature. ## How to act on the answers Some answers call for a small change, such as adding a column, a date filter or a clearer file name. Others need a larger project, such as a scheduled export or an integration. Put the small ones in the planned queue, and write a short note on the larger ones with the number of accounts and the destinations people named. Reply to people who asked for something specific. If you added a format, tell them where to find it. If you did not, say that the request is in the plan, and name the status. The [guide to replying to feature requests](/resources/reply-to-customer-feedback) covers how to keep the reply short and honest. ## Using export feedback in Escuta Produto Create the product, copy its public key, and add the widget to the page that starts the export. Use the open call or the data attribute for the idea type, and set the export metadata in the same code path that marks the file as ready. Each report appears in the inbox with the export type and format in its metadata and the page URL saved automatically. For the monthly read, export the inbox to CSV. The [analyze feedback in a spreadsheet guide](/resources/analyze-feedback-spreadsheet) shows how to group the answers, and the [widget docs](/docs/widget) describe the metadata and open calls in full. ## Frequently asked questions ### Why are exports a good moment to ask for feedback? An export usually means the person needs the data somewhere the product does not reach, such as a spreadsheet, another tool or a colleague. Asking what they plan to do with the file reveals the missing destination or format, which is a more useful answer than a general satisfaction rating. ### What should an export feedback prompt ask? Ask what the person will do with the file, in one short line, and offer an optional text box for what would make the export more useful. Avoid rating questions, because they measure whether the download worked rather than whether the data is useful. ### How often should you show an export feedback prompt? Limit it to once per user per week for most products, using a session flag or a stored timestamp. A prompt that appears on every download will feel like a form, and people will start skipping it, including the people who had something useful to say.