Overview
You may encounter two primary issues when using the Marker.io widget on certain browsers, especially Firefox and Safari:
The Marker.io widget does not display.
The widget appears, but it doesn't recognize that the user is logged in or fails to acknowledge a login attempt.
These problems often arise due to browser privacy settings that block cookies and cross-site scripting. To ensure the Marker.io widget functions correctly and recognizes logged-in users, follow the steps outlined below to:
Allow third-party cookies
Enable cross-site tracking
Note:
We're exploring the possibility of identifying users via tokens instead of cookies. If this aligns with your needs, vote on that feature here.
Google Chrome
Allow all cookies and enable cross-website tracking.
Managing Third-Party Cookies in Google Chrome
Option 1: Temporarily Enable Third-Party Cookies
Open the Website:
Navigate to the website where you wish to enable cookies.
Click the Eye Icon:
In the URL bar of your browser, look for an 'eye' icon.
Click this icon to temporarily allow third-party cookies for your current session.
Option 2: Permanently Allow Third-Party Cookies for Specific Sites
Access Chrome Settings:
Click the three dots in the top right corner of Chrome.
Select Settings.
Navigate to Privacy Settings:
In the Settings menu, go to Privacy and Security.
Cookie Settings:
Click on Site Settings, then Cookies and Site Data.
Add Trusted Websites:
Choose Allow third-party cookies.
Select Add and enter the URLs of websites you trust.
Example: Add '[*.]app.marker.io'.
Important Notes:
Temporarily enabling cookies is session-specific and will reset after the browser is closed.
Adding websites to the 'Allow' list in Chrome settings will permanently enable cookies for those sites, enhancing their functionality.
Google Chrome on Android
On your Android phone or tablet, open the Chrome app
To the right of the address bar, tap the three dots > Settings.
Site settings > Cookies.
Turn Cookies on.
Privacy and security > Do Not Track > Turn the setting off
Google Chrome & Incognito on a computer
At the top right, click the three dots > Settings.
Under “Privacy and security,” click Cookies and other site data.
Select: Allow all cookies.
Turn “Send a Do not track request with your browsing traffic” off.
💡 Top tip:
If you like to use incognito for testing and reporting feedback, consider having two tabs open on one browser window.
Tab 1 is logged into app.marker.io
Tab 2 is the website you are reporting feedback on
See the 3 dots at the bottom of the reporting widget. This is to inform you that you are a “known” user on Marker.io!
Google Chrome on iPhone & iPad
By default, cookies are allowed. This cannot be changed.
Navigate to your device Settings > Chrome > Turn ON Allow cross-website tracking.
Firefox: Allow all cookies and allow cross-website Tracking
Firefox on Android:
3 dot menu > Settings > Privacy > Cookies > Enabled
Firefox on a computer
Menu button > Options > Privacy & Security > Cookies and Site Data >
Manage Exceptions.
Allow: marker.io and app.marker.io
Firefox on iPhone and iPad
By default, first-party cookies are allowed, and third-party are blocked. This cannot be changed.
Navigate to your device Settings > Firefox > Turn ON Allow cross-website tracking.
Safari: Allow all cookies and allow cross-website Tracking
Safari on Mac
Click the Safari menu > Preferences > Privacy tab
Under website tracking:
Uncheck Prevent cross-site scripting
Uncheck Block all cookies
Safari on iPhone & iPad
Navigate to Settings > Safari
Turn OFF “Prevent cross-site tracking.”
Turn OFF “Block all cookies.”
Note: It's essential to add exceptions for both marker.io and app.marker.io in your browser settings to ensure the Marker.io widget displays correctly and recognizes user logins.
People searched the following terms to find this article.
The widget is not showing on mobile when I log in.
Why can't I see the widget as an authenticated user?
How to report with Marker.io using Chrome in incognito mode
When selecting Logged in users only. This feature does not seem to work on Firefox.
I have tried logging in using the quick code, and also the username/password.