Every report becomes a GitLab issue. The screenshot and all the details are already on it, so your team can start fixing right away.

Your visitor clicks on the page, marks what is wrong and presses send. The GitLab issue is made for them.
Draw, highlight and type on a screenshot, so nobody has to explain where the bug is.
Pick the widget colors, position and fields to match your site.
Paste one small snippet, or use the browser extension on sites that are not yours.
Everything your developers need is written on the GitLab issue for them.
Description
Reported by: Emma Cole (emma@brewly.com)
Source URL: brewly.com/shop/house-blend
Issue details: Open in PinMarks
I click Add to cart and nothing happens. The cart stays empty.
Console: 2 errors, 1 warning
TypeError: Cannot read properties of undefined
Session replay: View recording
Device type: Desktop
Browser: Chrome 126
Screen size: 1920 × 1080
OS: macOS 14
Viewport size: 1440 × 812
Zoom level: 100%
Custom metadata
• plan: Pro
• userId: u_4821
Screenshot
screenshot.png · added by PinMarks
Comments
Sam
Found it. Fix goes out today.
Browser, system, screen size and the page link are put on the issue automatically.
The marked-up screenshot comes with the report, so you see exactly what the person saw.
Errors from the browser console are summed up on the issue, so you can see what broke.
Add things like user ID or plan with the JavaScript SDK. They show up on every issue.
Pick the GitLab project for each PinMarks project.
Watch the steps the person took, then open the recording from the GitLab issue. Anything they typed stays hidden.
Pick your coffee club plan
Fresh beans on your doorstep. Change or pause whenever you like.
Sip
$9/month
Brew
$19/month
Roast
$39/month
Keep working in GitLab like you always do. PinMarks keeps the person who reported the bug in the loop.
Close an issue on GitLab and the report is closed in PinMarks. Reopen it and the report opens again.
A comment on one side shows up on the other.
Clients and teammates can reply from PinMarks without a GitLab login.
Stop sending feedback by email and shared files. Clients comment right on the page, and your team sees it in GitLab.
Clients open a link and leave feedback without making an account.
Every chat stays with the report it belongs to.
Paste one snippet on a local, staging or live site, or skip the install and report from any page with the extension.
Works in Chrome, Edge and Firefox.
Find out moreGet started
No credit card and no developer needed to set up. Three steps and you are collecting feedback.
Create your account and get 15 days to try every feature of your plan. No credit card needed.
Create your account →Name your project and connect your tracker if you use one, such as Jira, ClickUp or GitHub.
See integrations →Paste one snippet on your site, or use the browser extension, and collect your first report.
Read the install guide →FAQ
Everything you need to know before you start collecting feedback.
Open Integrations in your project, choose GitLab and sign in in the small popup window. Then pick the project where new issues should go.
The title, the description, the page link, who reported it and the marked-up screenshot. Browser, system and screen size, console errors and any custom details you send are added too.
Yes. Comments go both ways, and status changes follow in both directions. Syncing changes back from GitLab is on the Pro and Enterprise plans.
Yes. People only use the PinMarks widget or the browser extension. They never need a GitLab login to send feedback.
Yes. You can send every report to GitLab automatically, or read them in PinMarks first and send only the ones that matter with one click.
Start collecting visual feedback today — fix bugs faster and keep your whole team in the loop.
15-day free trial · No credit card · Cancel anytime