My counter isn't updating
Work through these in order. Most "counter stuck" issues are caused by one of the first three items.
1. Is the source actually firing?
First, confirm the platform is producing events. In Shopify, place a $1 test order. In Stripe, create a test charge. In a Zap, use Zapier’s test step.
If the platform isn’t firing, the counter has nothing to count. This is the most common cause of a stuck counter, so check it first.
2. Is it pointed at the right webhook URL?
Every source has its own webhook URL. Open Sources in the web app, click the 🔗 copy icon on the source, and compare it against the URL configured in your platform. A URL copied from a different source counts — just somewhere else.
3. Test the webhook directly
POST to the source’s webhook URL from the command line:
curl -X POST "https://hooks.pingbell.io/log?id=YOUR_SOURCE_ID&amount=1"If your screens celebrate and the Activity page ticks up, PingBell is fine and the problem is upstream — the platform or Zap isn’t calling the URL. If nothing happens, the source ID in the URL is wrong or the source is archived.
4. Check the Activity page
Open Activity, pick the source, and set the range to Today. If events are arriving they show here within seconds. Each source card on the Sources page also has a 7-day sparkline — flat means nothing’s been received.
5. Is the source archived?
Archived sources don’t accept events. Check the Archived filter on the Sources page and restore it if it’s there.
6. Is the counter looking at the right window?
A counter block shows a time window — all time, today, or the last 7 days. A “Today” counter resets at midnight UTC, so a quiet morning after a busy night is correct behavior, not a bug. Check the block’s Showing setting in the board editor.
7. Going through Zapier or Make?
Check the platform’s own run history — Zapier’s task history and Make’s execution log show whether the trigger fired and whether the PingBell action ran. Polling triggers can add a few minutes of delay depending on your plan there.
Still stuck?
Email [email protected] with the source name and a rough timestamp of when events should have arrived. We can check the server side and get back to you.