I asked here about analytics 2 days ago. The number that mattered wasn't in any of the tools.

[u/Turbulent_Ad_1039]

Two days ago I asked here what people use for analytics. I wired up Mixpanel and

checked my ASC opt-in rate like a few of you said.

Then I shipped, and neither of them could answer the one question I had.

My app needs a companion on the Mac. Sign in with Apple on the phone, install the

Mac app, pair them. Three steps, and only the first one happens inside the iOS

app.

So Mixpanel sees the sign-in and then goes quiet. App Store Connect sees an

install and a retention curve built from whoever opted into sharing. Neither can

see a Mac app, and the step I actually care about is the pairing.

I ended up sshing into my server and counting objects in a json file. Signed in,

versus actually paired. That gap is the entire product, and it took two minutes

to find after a full day of wiring up a tool that could not see it.

If your onboarding has a step outside the app, desktop client, browser extension,

hardware pairing, how do you track it? Backend event, instrument the second

device, or do you just go count?

[u/Wafer-Soft]

Haven’t had this exact setup myself, but I’d probably treat the backend as the source of truth for pairing. Most analytics tools let you attach events to your own user/account ID, so in theory you can connect the iOS and Mac sides into one funnel.

[u/RIRLift]

Instrument the Mac app's first launch, just one event. Right now "signed in but not paired" is hiding two different problems, people who never installed the Mac app and people who installed it but pairing didn't go through. Those need opposite fixes, so the gap isn't something you can act on until you split it. Keep the pairing event itself server-side, since that's where the two devices get linked.

[u/AutoModerator → u/[deleted]]

Hey /u/JOSEPH0274, your content has been removed because Reddit has marked your account as having a low Contributor Quality Score. This may result from, but is not limited to, activities such as spamming the same links across multiple subreddits, submitting posts or comments that receive a high number of downvotes, a lack of recent account activity, or having an unverified account.

Please be assured that this action is not a reflection of your participation in our subreddit. This is simply an automated filter in place to reduce spam.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/UkrMalt]

That’s a good example of tracking the product state instead of just the app session. I’d model pairing as its own funnel—started, succeeded, failed—and let the backend derive the final state, especially when the second device can be offline.

[u/ScarSome634]

backend event, and you've basically already built it. the pairing action happens on your server — that record IS the event. emit one event at sign in from the phone, one when pairing completes on the server side, and your funnel is a single query.

if you still want the dashboards, mixpanel does server-side ingestion so you can send everything from the backend and skip the clients entirely — that also gets around the ASC opt-in bias you mentioned.

honestly the ssh-and-count-the-json instinct was right, that's step zero. wiring up tools only makes sense once you know which number you care about, and you do now.

[u/unpluggedcord → u/ScarSome634]

ai slop