Troubleshooting

Common product issues and the checks support runs first.

Use this page to diagnose embed visibility problems, no-data states, reactions that are not logging, and OAuth connection failures.

Setup guide Contact support

Common issues

Covers the highest-frequency support cases in the current product surface.

Ingest lag

~1 min

Allow the first event a short delay before assuming a failure.

Fallback

Support

Escalate with workspace slug, page URL, and reproduction steps.

Widget not appearing in Notion

Start by validating the embed block and the generated URL.

Make sure you added the widget using the /embed block rather than a mention or regular link.
The embed URL must point to the page-specific embed endpoint copied from the Pages list row.
Notion may cache embedded content. Try a hard refresh with your platform shortcut.
Make sure the page exists in your workspace and its domain matches the configured site.

Widget is embedded but no data appears in the dashboard

Most first-event issues are configuration or test-path problems rather than ingestion failures.

Confirm that tracking is enabled for the page in the Pages view.
It can take about one minute for the first event to appear in the dashboard.
Test with a real visit in a private or incognito window, not just the app shell.
Editing mode in Notion may suppress the embed. Make sure the page is published or shared as a guest link.

Reaction buttons are visible but clicks are not recording

Verify that the page binding and tracking state line up with the active embed.

Reaction buttons appear at the bottom of the embed widget.
Reactions are only tracked for pages with tracking explicitly enabled.
Make sure the page URL matches the page registered in Notionalysis exactly.
Check the Reactions report to confirm events are not being recorded silently.

The widget shows a Notionalysis watermark

Watermark visibility is a plan-gated setting exposed in the widget controls.

The watermark appears on Free workspaces. Upgrade to Pro or Business to remove it, then manage visibility in Settings / Widget or the billing flow.

Data counts look lower than expected

The reporting model prioritizes explicit page tracking and session-aware deduplication.

Notionalysis counts real page view events from enabled pages only.
Duplicate events from the same client session are automatically deduplicated.
Disabled pages contribute nothing to report totals.

I accidentally disabled tracking for a page

Tracking state is not retroactive. Re-enabling only affects future events.

Go back to Pages and re-enable tracking for that page. Events that occurred while tracking was disabled are not collected retroactively.

Notion shows as disconnected after reconnecting

This usually means the OAuth flow was completed against the wrong account or did not finalize cleanly.

Run the OAuth flow again from Settings / Integrations / Reconnect Notion.
Make sure you authorize the intended Notion account and workspace during the flow.
If the problem persists, contact support.

Escalation checklist

Include the page URL, workspace slug, browser, and whether the page is published.

If the issue is visual, include a screenshot of the embed block inside Notion.