How to Remove the Notification Feed from My Site on Wisepops?

First identify whether your Wisepops notification feed is a floating widget or a custom header embed. The documented removal method differs. Identify the feed-specific code before editing so you do not unintentionally remove other functionality.

Source: Wisepops notification-feed removal guide, checked September 6, 2026. The change and verification checklist below is editorial guidance.

Identify the implementation

The vendor specifies notification tracking code. Do not interpret that as a blanket instruction to remove every Wisepops script, particularly if other campaigns must remain available. If the installation is shared or unclear, confirm the correct removal method with Wisepops before changing it.

Remove the feed

For the default widget, remove the identified notification tracking code from its installation location.

For a custom embed, find the template, search for wisp and identify the feed’s HTML tags. The vendor instructs removing those tags. Review each match in context instead of doing an unrestricted replacement across the site.

For Shopify, the documented path is Online Store → Themes → Edit code, then the header file. Find wisp and comment out the corresponding block. Wisepops notes that some themes require additional development work.

Verify after the change

Check the published website on desktop and mobile, including any separate header layouts. Record the pages tested and whether the feed is absent.

• Header layout: Navigation, logo and other controls still work and have no unexpected gap.
• Feed visibility: The bell or embedded feed is absent on the pages where it should be removed.
• Other campaigns: Any Wisepops functionality you intended to retain still works under its normal display conditions.
• Installation scope: A second code placement is not loading the feed on another template.

If the feed remains, inspect the actual published template and code placement before deleting broader blocks. A preview of one template does not prove the change applies across the whole site. If unrelated functionality breaks, restore the preserved code and reassess the block boundary.

Keep account changes separate

Removing frontend feed code is not evidence of subscription cancellation or account deletion. Record what code changed and what was verified. If your intention is broader removal, use the vendor’s relevant uninstall instructions and check the account’s billing status separately.

Return to Wisepops help for other setup tasks.