Get detailed website feedback reports directly into Notion. When your team and clients find issues, they can annotate them directly on your website. No need for clients to install anything. Your team gets a detailed report straight into Notion.

Before you start: make sure you have at least one Table or Database set up in Notion where you want to collect website feedback.

On the Marker.io dashboard, create a project, entering the project name and the website where you wish to collect feedback.

Select the Notion integration, then allow Marker.io to access your Notion database.

Marker.io fetches your native Notion fields into your widget form. You can show/hide fields and preset values. For example, set the default Priority to Medium and let reporters change it as needed.

Separately from your Notion connection, Marker.io controls who can see and manage feedback for this project via Manage access (top-right of the project's Widget or Feedback view).

Two ways to grant access:

Admins always have access regardless of this setting. This is separate from your Notion project access covered in Permissions & troubleshooting below: someone can have full access in Marker.io without access to the underlying Notion project, or the other way around.

Go to your project's Widget > Installation and choose how to install.

Tip: click Try on demo website first to test-drive the widget before installing anything on your real site.

Once installed, anyone who can view your website, whether staging or live, will see the Marker.io feedback widget. If you used the browser extension method, remember: each reporter needs the extension installed in their own browser before they can see the widget.

Reporters can submit feedback directly to your Notion project without leaving their website. Their feedback automatically includes detail-rich technical data.

Say the Contact Us button is broken on the About Us page. The reporter clicks the widget and is presented with a screenshot and a feedback form to complete. The screenshot can be annotated, and the form can be as simple or as complex as you wish. We recommend keeping it simple for non-technical reporters.

You can review feedback both in Marker.io and in your Notion project. In Notion, feedback arrives with a clear screenshot and automatically captured technical data:

We also provide links to console logs, network requests, and a session replay video of what the reporter did just before submitting, so your dev team has the complete context.

The "Contact via Marker.io" link opens the Feedback Page, where you can reply to the reporter. They'll receive an email where they can reply too. Marker.io syncs these replies to Notion as comments on the original block, keeping pages clean and organized (see the resync note below if you're not seeing this behavior yet). Comments made directly in Notion don't sync back to Marker.io the same way. Reply from the Feedback Page if you need the reporter to see it.

When you mark an issue "Completed" in Notion, Marker.io automatically updates the status to Resolved in Marker.io and emails the reporter to let them know. No need to update things in two places.

To manage your status sync settings:

Want to learn more about how Notion handles statuses? Check out Notion's Status Property guide.

We take your data and the security of our systems seriously, using industry-standard security practices to connect with your account. See our latest security policy at marker.io/security.

Admin permissions are required on the Notion project you wish to connect with. If the connected account is later removed, or its role is downgraded, sync will silently stop working. This is the most common cause of "issues stopped syncing" reports.

We recommend creating a dedicated Marker.io Bot user in Notion rather than connecting a personal account, so sync doesn't break when an individual leaves the team or changes roles. See [[Create a Service Account or Dedicated User for your integration]].

If issues have stopped appearing in your Notion database:

Try the following, in order:

If you don't see your Notion database in Marker.io after connecting the integration (see "Create a Marker.io project" above), add the Marker.io connection directly in Notion:

Notion's one-way relations are backlinks to a linked page. They don't count as a true "relation" since the linked page isn't related back to the original. Because of this, the sync needs to be a two-way relation for it to appear as a field in Marker.io. You'll also need to make sure both databases are shared with Marker.io, as covered in "I don't see my database" above.

For example, if Database 01 has a Relation field pointing to Database 02:

Click Edit property and make sure Show on Database 02 is toggled on:

For more detail, see Notion's two-way relations guide.

You can organize feedback as subtasks under a primary task using Notion's parent/sub-item functionality.

Enabling subtasks in Notion:

Enabling this introduces Sub-item and Parent Item fields on your Marker.io forms. Decide whether these should be pre-selected and hidden from reporters, or editable. Letting reporters choose the parent item can encourage more detailed feedback but needs more moderation.

If you've used Marker.io with Notion for a while, you'll notice feedback updates (like comments) appearing as new content blocks at the end of your Notion page rather than as comments. To fix this, resync your account:

If you manage multiple Notion accounts, see [[Managing Multiple Integrated Accounts]] for how to set this up cleanly without accounts overwriting each other.

Invite your team to collaborate on a dedicated Notion project today with Marker.io, where anyone can report bugs and feedback in seconds. See [[Get started with Marker.io]] for more on getting the most out of your setup.

If you have any questions, comments, or corrections, chat with us at the bottom right of our web pages.