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 integration is producing events. In Shopify, place a $1 test order. In Stripe, create a test charge. In HubSpot, move a test deal through the trigger stage.
If the source isn't firing, the counter has nothing to count. This is the most common cause of a stuck counter, so it's worth checking first.
2. Is the integration still authorized?
OAuth tokens expire. An integration that worked yesterday can silently break if the upstream tool revoked the token. Check the integration's status in your PingBell dashboard: Counter → Sources. If any source shows “token expired” or “authorization required”, reconnect.
3. Are the events passing your filters?
If you set a filter on the counter (e.g. “only orders over $100”), events that don't match are dropped silently. Check your filter config under Counter → Filters. Temporarily remove all filters and see if events start flowing; if they do, narrow the filter from there.
4. Check the event log
Every counter has an event log at Counter → Activity. This shows every event received, whether it was counted, and if not, why (“filtered out”, “duplicate”, “schema error”, etc.). If events appear in the log but don't increment the counter, the reason is there.
5. Test the webhook URL directly
For custom webhook integrations, you can POST a test event from the command line:
curl -X POST https://api.pingbell.io/v1/counters/<id>/events \
-H "Content-Type: application/json" \
-d '{"value": 1, "metadata": {"test": true}}'
A 200 OK confirms the endpoint works. Anything else
— 401, 404, 422 — points at the specific problem.
6. Are you over the rate limit?
Default rate limit is 100 events per second per counter. If you're bursting above that (unusual), events are queued and processed in order but with added latency. Contact support if you need a higher limit.
7. Is the counter archived or paused?
Archived counters do not accept new events. If you recently archived the counter (or your trial expired and the counter paused), incoming events are rejected with a 410 Gone response.
Still stuck?
Email [email protected] with the counter ID and a rough timestamp of when events should have arrived. We can pull the server-side logs and respond within a few hours.