Monitoring
User feedback
Install Blipit.showFeedback() or one POST
After an error, ask the user what they were doing. The browser SDK opens a small native dialog; any other client posts to the feedback endpoint. Feedback is linked to the event's issue and shown on the issue page and on the Feedback page.
1Browser dialog
Opens a labelled form (name, email, message) that defaults to the last captured event. Escape closes it, and it shows a busy label while sending.
window.addEventListener("error", () => {
Blipit.showFeedback({ title: "Something went wrong. What were you doing?" });
});2Direct API
curl https://in.blipit.io/api/v1/feedback \
-H "Content-Type: application/json" -H "X-Blipit-Key: <public key>" \
-d '{"message":"The pay button did nothing","email":"ana@example.com","event_id":"9f1c4b6d8e2a47f0b3c5d7e9a1b2c3d4","url":"https://shop.example.com/checkout"}'3Keep the reporter in the loop
Every report gets a reference per project (BR-1, BR-2 and so on) that the widget shows after sending. When the reporter leaves an email, Blipit sends a receipt in their language with a link to follow the report. On the report page, Reply to reporter emails your message while Internal note stays with your team, and moving a report to In progress, Done or Won't fix offers an email you can edit or skip. Choose receipts, statuses, the sender name and the Reply-To address under Project settings, Bug report widget. Every email has a one-click unsubscribe, one address gets at most 10 an hour, and reporters without an email get no email. Odoo users see their own reports under Blipit, My reports. In an internal note, type @ to mention a teammate who can open the report: they get an email with the note and the report shows as unread for them. Mentions never reach the reporter.
5Service desk
Bug reports work as a service desk: reporters hear about every step with their reference, and your team gets targets, alerts and a report on how it is doing. Set it up under Bug reports, Service desk settings.
- Every plan: emails for Received, Under review, In progress, Waiting on you, Fixed, Won't fix and Reopened, never for priority, label or assignee changes. Changes within a few minutes become one email, and all emails about a report stay in one thread.
- Solo and up: a page listing a reporter's reports in your workspace with a reply box, Waiting on reporter with a reminder and auto-close, saved replies that fill in the reporter's name, reference and link, following reports, and merging duplicates.
- Team and up: response and resolution targets per priority in your business hours and holidays, paused while waiting on the reporter, with Due soon alerts to the assignee and Overdue alerts to owners and admins; a one-click satisfaction question after a fix; teams; and the service desk report with medians, p90, SLA met and satisfaction side by side.
- Scale: targets per team, for example an outside IT provider's contract, team comparison and figures per team member.
Good to know
- Fields: message 1 to 5,000 characters (required), name up to 128, a valid email, event_id of 32 hex characters, and a page URL kept without its query string.
- The Feedback page lists everything newest first. Text is always rendered as text, never as HTML or links.
- Limit: 60 feedback posts a minute per key.
- Bug reports in the dashboard sidebar shows how many reports are new to you, and the browser tab shows it too, like (3) Blipit. A report stops counting once you open it or it leaves New; Mark all as read on the Bug reports page clears the count.
- The Track this report link in every email opens a private page in the reporter's language with the reference, the status history, your replies and the screenshot they sent. There they can add a message and one image (PNG, JPEG or WebP up to 3 MB, at most 5 images per report and 10 messages a day). Their message appears in the report's activity marked From reporter and is announced to the assignee, or else to the people who get bug report emails, Slack, Teams and webhooks (type bug_report.reply). The page is not indexed by search engines and only opens the report its link was made for. Before anything is shown, the page emails a 6-digit code to the reporter (valid 10 minutes, 5 tries); after it is entered, that browser can open the report for 7 days and the link leaves the address bar. Reports sent without an email can only be followed in the app they came from. In Odoo, reporters follow and answer their reports in the report's chatter under Blipit, My reports.
- Reporters can also simply reply to any of these emails. The reply goes to an address made for that report, Blipit removes the quoted earlier mail and signatures, ignores out-of-office and other automatic replies and mail from any address but the reporter's, and adds the rest to the report as a message from the reporter, with the same notices and the same limit of 10 messages a day.
- Reply to reporter and Internal note take attachments: click Attach, drop files on the box or paste an image. Images (PNG, JPEG, WebP) and PDFs up to 3 MB and WebM or MP4 videos up to 60 MB, at most 10 files per message and 30 per report, each with its upload progress and a button to remove it. Files on a reply to the reporter appear on their tracking page, as thumbnails and links in the reply email, and in Odoo; files on an internal note never leave your team.
- In Odoo, Blipit, My reports opens each report on one screen: the status, when it was reported and last updated, the latest reply from your team with its files, what the user reported (description, page, browser and system) and a gallery of their screenshots, screen recordings and session replay next to every file your team sent. Everything opens full screen with arrow keys, swipe, zoom and download, and the conversation stays in the chatter beside it. File links expire after 15 minutes and the replay link after 10, and each one opens only that report's file for that user.
Stuck? Email support@blipit.io. Keys and the project id for each project are under API keys in app.blipit.io.