Cloud Counters: Using Pro on Your Phone, Laptop, and Volunteers' Phones Without Losing Your Count

I run gates and capacity tracking for live events. Most of my counter setups look like this: a laptop in the production trailer, my phone in my pocket, an iPad at the front-of-house desk, and a handful of staff phones at the gates. Everything needs to read off the same total.

This is the situation Pro is built for. It is also the situation that confuses people the first week they upgrade, because if you keep using the regular tool pages on a phone after you sign up, nothing looks different — you are still on the free landing page, your local count is still saved on that one device, and none of the new features are visible. The free pages exist for visitors who haven't signed up. Once you have an account, the dashboard is where your real counters live.

What follows is the route I send to every new client on day one. None of it is hard. All of it goes wrong if you skip a step.

You created a counter while signed in on your laptop. You want to use it on your phone. Here is the entire process.

1. On your phone, sign in. Go to digitaltallycounter.com/login and use the same email and password you used on the laptop. The phone browser does not need to be the same one you use on the desktop — you can sign in from Safari on your iPhone while Chrome on the laptop is still open.

2. Open the dashboard. Every cloud counter you have created is listed there, grouped by type. Tap the counter you want, and you are looking at the same count that is sitting in front of you on the laptop. Tap to add to it. Refresh the laptop page if you want to confirm — the new number will be there.

That is it. There is no second account, no app to download, no pairing step. The same login on a different device sees the same data.

If you do this and the count on your phone shows zero while your laptop shows seventeen, you are almost certainly still on the free landing page. The URL bar on your phone will read something like /counters/tally-counter — that is the page anyone can use without signing up. The path you want has /cloud/counters/ in it, which is the URL pattern for your saved counters. The dashboard always sends you to the right place.

Single-user, multiple-device is the simple case. You sign in everywhere, every counter is yours, and the cloud handles the syncing.

A few practical notes from running this configuration for the last year:

Clicks are saved as soon as you make them. There is no save button. If you tap the increment ten times and then put your phone in your pocket, all ten are already in the database. Closing the browser tab is fine.

The counter does not poll constantly to refresh from other devices. If you are making changes on the laptop while watching the phone, the phone will not update in real time — you will see the new total the next time the page reloads or the next time you interact with it. For most of my use cases this is not a problem, because either I am the only one clicking or I am at one device for an extended stretch.

The history log below each counter (more on this below) does refresh after every interaction, so when I have been using the laptop and pick up the phone, the first thing I look at is the log to see what changed while I was away.

If you sign out on a device, your count is not deleted. It stays in the cloud. The next time you sign in anywhere, it is still there.

This is the harder case and the one that actually pays for itself. I have a gate volunteer at door A, another at door B, and I want both their clicks rolling up into one count without giving them my password.

Open any cloud counter and click the share icon in the header — it is the icon shaped like a chain link or three connected dots, depending on the counter type. A modal opens with two sections: View links and Edit links.

View links generate URLs that anyone can open to watch the count update in real time. They cannot change anything. I use these for the production team, sponsors who want to know how the night is going, and the front-of-house manager who likes to keep a tab open. View-only is also useful for an OBS overlay if you are streaming.

Edit links generate URLs that allow whoever opens them to add to or subtract from the count. The volunteer at door B taps a link, types their name into a one-line field at the top of the page, and starts clicking. Their clicks land in your counter the same way yours do. Their name is recorded against every click.

When you generate either type of link, give it a name first. The text box reads "Optional name" and it is, technically, optional. Skip the names and you will have a list of share links that all look identical and you will revoke the wrong one. Name them after the person, the location, the role — "Door A volunteer," "Booth 4 iPad," "Marketing director Sarah." Make it easy to identify weeks later when you are cleaning up.

Links can be revoked one at a time, or you can flip the master toggle for the whole section to revoke every link of that type at once. The toggle asks you to confirm before doing the bulk revoke, because doing it accidentally during a live event would ruin your day.

I default to view links and only generate edit links for people who genuinely need to record clicks. This is not paranoia, it is logistics. Once a person has an edit link, they can add or subtract — and you cannot stop a well-meaning volunteer from "correcting" the count if they think it is wrong.

Use a view link when:

• The recipient is a stakeholder who wants visibility into the running total but is not actively counting (your client, the venue manager, the sponsor, the box office).
• You are putting the count on a TV or stream and need a URL the broadcasting setup can load.
• You want a paper trail for someone without giving them write access.

Use an edit link when:

• The recipient is doing the counting and you cannot be at every gate yourself.
• You need each person's clicks attributed to their name in the log.
• You want the option to revoke their access cleanly when their shift ends.

A practical pattern I use at multi-day events: at the beginning of each day, generate fresh edit links named for that shift's volunteers. At the end of the day, revoke the whole edit-link section. Day two starts with a clean list. Anyone who needed access last night does not still have it tonight.

Nothing breaks if you skip the daily rotation — but if a volunteer's phone gets handed to someone else, or their account gets compromised, you are not protected by the link still being live. Treating these like single-shift access tokens reduces that risk to almost nothing.

Every interaction with a cloud counter writes a row to the history below it. Increment, decrement, target change, reset — each one shows up with a timestamp and who did it.

For your own clicks, the log says "by You." For clicks coming through an edit link, it shows the name the visitor typed in. If they did not type anything, it shows "Anonymous," which is one of the better arguments for telling your volunteers to fill the field in.

What I actually use the log for:

Reconciling against the gate count. If my counter shows 1,847 and the box office shows 1,851, I can scroll the log and see what time the discrepancy opened up. Usually it is one of the gate volunteers double-clicking. Sometimes it is a refund that was not pushed through. The timestamps narrow it down fast.

Knowing who is awake. If door B has not registered a click in twenty minutes during a peak rush, either no one is coming through that door (worth knowing) or the volunteer has stepped away (also worth knowing).

Cleaning up after the fact. Decrements show up in the log too, with the same attribution. If the count was wrong by ten, I can see who walked it back ten times in a row at 9:42 p.m. and ask them about it the next day.

The log is durable. Revoking the share link does not erase the rows that link generated — the volunteer's name stays attached to the clicks they made, even after the link is gone. This is intentional. You should not lose your history because you cleaned up your share-link list.

Five things I see clients hit in their first month, in rough order of frequency:

1. "I am signed in but I see the free version." You are on the public landing page for that counter type, not the cloud version. Open the dashboard, find the counter you created, click "Open." Bookmark the resulting URL. The free landing pages exist for visitors who haven't signed up, and they look almost identical to the Pro counter pages, which is genuinely confusing on day one.

2. "My phone shows a different number than my laptop." Either you are on the free landing page on one of them (see above) or you have not refreshed the page on the device that is behind. Reload, or click the counter once — the cloud value will sync into the display.

3. "My volunteer's clicks are not showing up." Confirm they are using the edit link, not the view link. View link URLs go to /counters/watch/...; edit link URLs go to /c/[token]/edit. The view-only page looks like the counter and shows the live count, but tapping the buttons will not change anything — there is no error, the click just does nothing on the server. If you sent the wrong type of link, generate a fresh one and revoke the old one.

4. "I can't find where to sign out." Top-right corner of any page on a desktop browser — the round avatar button with your initial in it, next to the Dashboard link. Click it; the menu has Sign out at the bottom. On a phone, the avatar moves into the hamburger menu under "Account."

5. "I want to see this on a TV." Generate a view link and load the URL on the TV's browser. Most modern TVs have a basic browser; if yours does not, plug in a laptop or a small streaming stick and load the URL there. The view-only page refreshes on its own (every fifteen seconds for standard counters, every minute for the People Counter view), so once it is loaded you can leave it. The page is designed to be readable from across the room — large numbers, plain layout, no chrome.

View-only share links auto-refresh on a timer, so the TV in the production trailer or the tab on your sponsor's laptop is never far behind. You do not have to do anything to make this happen.

For the standard cloud counter view (the page that loads from a /counters/watch/... URL), the page does a hard reload every fifteen seconds. The visible count updates with it. This is fine for most uses — if your client glances at the screen, what they see is at most fifteen seconds old.

For the People Counter view (the /p/... URL pattern), the page silently re-fetches the count from the server every sixty seconds and updates the displayed numbers in place. There is no flash or reload — the totals just tick over.

The owner pages (your dashboard counter views, where you have edit access) do not currently poll on a fixed schedule. They update whenever you interact with the counter or refresh the page. If you are sitting on a phone watching the count change while someone else clicks from another device, you will see their changes the next time you tap, refresh, or scroll-to-refresh.

The "Pro" tier covers cloud sync, share links, history, timeline graphs, and ad removal. Pro is the top active tier — there is no higher plan above it, and the older Solo/Team tiers were folded into Pro a while ago.

If you are on Ad-Free instead of Pro, you have removed the ads but you do not have cloud sync. If your counter is not appearing on your dashboard, that is the first thing to check. Visit your subscription page — your active plan is listed at the top.

Most of what makes Pro counters useful at a real event is not the feature list. It is the fact that you do not have to consolidate at the end of the night. Three volunteers clicked, one stakeholder watched, the count is correct, the log shows where it came from. That is the whole point.

If you have not yet generated a share link, do that first. Open one of your counters, click share, generate a view link with your own name on it, open the URL on your phone in incognito mode. You will be looking at your own counter as a stranger would. That is what your volunteers will see. Once that loop makes sense, the rest of the system makes sense too.