ScreenshotNeo

BlogGuides

ChangeTower alerts not arriving by email: troubleshooting guide

Check ChangeTower notification preferences, monitor settings, and recipient access to find why an expected email alert is missing.

By the ScreenshotNeo team4 October 20266 min read

When ChangeTower alerts are not arriving by email, first check Settings → Notification Preferences for the alert category you expect. Then verify that the monitor is scheduled, email alerts are enabled for that monitor, and a qualifying page change has actually been detected. If the event appears in ChangeTower’s in-app Notifications page but no email arrives, the monitor may have detected the change; the remaining delivery issue needs account-specific investigation by ChangeTower support.

This guide follows ChangeTower’s published help instructions. Those sources explain notification preferences, monitor setup, team subscriptions, and the support route, but do not document email delivery logs or confirm mailbox-specific causes. [notification preferences] [monitor setup]

1. Check the notification category

  1. Sign in to ChangeTower and open Settings → Notification Preferences.
  2. Find the category related to the missing email, such as Change detected, Monitor started, or Domain scan completed.
  3. Enable the relevant checkbox and save if the page asks you to. ChangeTower says preference changes apply automatically.
  4. Check the wording and selected category in your own account if the current interface differs from these labels.

Preferences are category-specific. Receiving one type of ChangeTower email does not establish that every alert category is enabled. [ChangeTower notification preference instructions]

2. Confirm the monitor could have generated an alert

ChangeTower’s setup guide describes change alerts as event-triggered: the monitor checks a page on its selected frequency or schedule and compares it with its starting snapshot. A newly created monitor may stay quiet until the page actually changes. No email before a qualifying change is not, by itself, evidence of a delivery failure.

  1. Open the relevant monitor and confirm that it is active and has a schedule or frequency configured.
  2. Verify that it monitors the intended page and the relevant content or change type.
  3. Check whether the page changed after the monitor’s baseline snapshot. A change that happened before the baseline may not count as a new change.
  4. Allow for the configured check schedule. The cited documentation does not provide a universal alert delivery-time guarantee.
  5. Look at the in-app Notifications page for an event at the expected time.

ChangeTower’s first-alert guidance says the page must actually change before a change alert is sent. [Create your first monitor]

3. Check email settings on the monitor

Account-wide notification preferences and monitor-level email settings are separate checks. In the monitor’s Details section, confirm that email alerts are enabled for this specific monitor. Also recheck its schedule and target URL. [ChangeTower monitor setup guide]

4. Verify the recipient and team subscription

If the alert should go to a teammate or shared address, check each part of that recipient’s access:

  • The intended person or address has the appropriate workspace or team membership.
  • The invitation was accepted, if the person was invited.
  • The person is subscribed to the monitor when monitor subscription is required.
  • The person’s own notification preferences allow the relevant alert category.

ChangeTower’s monitor subscription article gives instructions for subscribing users, but it dates from March 2023 and describes team notification management as a premium feature. Plan entitlements and interface labels may have changed, so verify what is currently available in your account. [Subscribing users to monitors]

5. Use the in-app notification to narrow down the issue

Find the expected event on ChangeTower’s Notifications page, if available:

What you find What it suggests Next step
No matching event The expected event may not have been generated, or the monitor, schedule, or alert criteria may need review. Recheck the monitor, schedule, target page, and whether a qualifying change occurred.
Matching event is present, email is missing The event was recorded in-app, but this alone does not show where email delivery failed. Confirm preferences and recipient settings, then contact ChangeTower support with the evidence.

This is a diagnostic distinction based on the documented Notifications page and support route. It does not prove whether an email was generated, rejected, bounced, or filtered; the public documentation reviewed does not expose those delivery details. [monitor setup and notifications] [ChangeTower contact and support]

6. Contact support with useful evidence

If the notification appears in-app but the email is missing, or the settings look correct and the expected event is absent, contact ChangeTower support for account-specific investigation. Include:

  • The monitor name and page URL.
  • The change you expected the monitor to detect.
  • The approximate time the monitor checked or the event appeared.
  • The intended recipient address, shared mailbox, or team member.
  • Whether the event appears in the in-app Notifications page.
  • The alert category and the relevant preference and monitor settings you checked.

ChangeTower’s contact page lists email support and says it replies within one business day on every plan. That is the vendor’s stated response target, not a guarantee of resolution time. [ChangeTower contact page]

Common troubleshooting mistakes

  • Assuming a new monitor must send an immediate change email: the setup guide says a change alert comes after the page changes. Check the baseline and schedule.
  • Checking only account preferences: email can also be disabled in the monitor’s Details section. Verify both places.
  • Checking only the monitor owner’s settings: a teammate may need access or a monitor subscription and has their own notification preferences.
  • Treating no email as proof that the monitor failed: first look for the event in-app and confirm that a qualifying change was detected.
  • Assuming a mailbox rule is the confirmed cause: the reviewed ChangeTower sources do not identify spam filtering, allowlists, sender addresses, SPF/DKIM, or mailbox provider policies as causes for this issue.

As general email hygiene, you can check your usual inbox folders and any rules your organization has configured. Treat that as a recipient-side check, not a documented ChangeTower-specific fix. If it does not explain the missing message, support may need to investigate delivery status.

Performance, reliability, and cost considerations

For this issue, the practical timing factor is the monitor’s configured check schedule: the alert depends on a qualifying change being detected. The available sources do not state a universal email latency, delivery rate, or failure rate, so this guide cannot promise when a message should arrive or identify the cause from silence alone. ChangeTower says email support replies within one business day on every plan; that is a support response target, not a delivery or resolution guarantee. [monitor setup guide] [support contact page]

There is no browser screenshot setup needed to diagnose a missing ChangeTower email. If you also need a clean visual record of the monitored page or its changed state, ScreenshotNeo is a website screenshot API and MCP server for developers. It removes cookie and consent banners, newsletter popups, and chat widgets before capture; its capture settings can be turned off individually. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and each response indicates the page verdict and billing status. See ScreenshotNeo and its API documentation.

Or skip the browser setup

Make one GET request to capture a page as an image or PDF. For example, this cURL request saves a WebP screenshot of the page:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://changetower.com -o changetower.webp

Use the same endpoint from Python:

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://changetower.com"},
    timeout=90,
)
open("changetower.webp", "wb").write(r.content)

Or from Node.js:

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://changetower.com'
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await import('node:fs/promises').then(fs => fs.writeFile('changetower.webp', Buffer.from(await res.arrayBuffer())));

Use your API key in place of YOUR_API_KEY. ScreenshotNeo removes cookie banners, popups, and chat widgets before the shot; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. Sign up for free screenshots.

FAQ

Why did I get other ChangeTower emails but not a change alert?

Notification categories can be enabled separately. Check the preference for the specific alert type and the email toggle on the monitor.

Should a newly created monitor send a change email right away?

Not necessarily. ChangeTower’s setup guide says a change alert follows an actual page change after the monitor has a starting snapshot.

Can I tell from the public documentation whether ChangeTower sent or bounced my email?

No delivery logs or mailbox-specific diagnosis are described in the sources cited here. If the event is recorded in-app and settings are correct, contact support with the event and recipient details.

Where can I review current alert settings?

Check Settings → Notification Preferences for categories and the monitor’s Details section for its email setting. Interface wording can change.