How to Measure Opt-In Rates for Tone-Triggered Campaigns

A tone-triggered campaign only works for people who have said yes. Before a phone can respond to an inaudible tone, the person has to have the app, allow it to listen, and often allow it to send notifications. That makes opt-in the first number every brand should understand, and the one that most often gets reported loosely. This guide gives brands and agencies a clear way to define, track, and report opt-in rates so a pilot's results mean something to the people paying for it.

Why "opt-in rate" needs a definition

"Opt-in rate" can mean several different things, and teams often mix them up. One person means the share of app users who allowed the microphone. Another means the share of an event audience who joined the experience. Both are useful, but they answer different questions. Agree on the definitions in writing before launch, and keep them the same across every report.

Map the opt-in funnel

Break the path into steps, and measure each one as a share of the step before it:

1. Audience reached. How many people were in the venue, store, or broadcast audience during the campaign window. Use the best source you have, such as ticket scans, store traffic counts, or audience estimates, and label which one you used.
2. App users present. How many of those people had the supporting app installed and opened it during the window.
3. Microphone permission granted. How many app users allowed the app to use the microphone. Tone recognition needs it, and both iOS and Android ask the user before an app can use it.
4. Notification permission granted, if the experience relies on alerts.
5. Tone detections. How many devices detected at least one tone.
6. Actions taken. How many people tapped, redeemed, entered, or watched what the tone unlocked.

Each step is its own rate. "Microphone opt-in" is step 3 divided by step 2. "Audience participation" is step 6 divided by step 1. Report both, and say which is which.

Instrument it before launch

Opt-in numbers are only as good as the events behind them. Before the campaign goes live:

• Log the permission prompt and its result as separate events: prompt shown, allowed, denied, and changed later in settings.
• Log tone detections with the campaign, location, and time, so you can match them to a specific moment.
• Tie actions to the tone that triggered them, so an offer redemption can be traced back to a store, a sponsor moment, or a broadcast segment.
• Respect the user's choices. Collect only what the experience needs, explain it plainly, and follow the app's privacy policy and applicable law.

Improve opt-in the right way

The biggest lever is usually the moment you ask. A permission prompt that appears with no context is easy to deny. A short screen that explains what the person gets, such as a sponsor offer or bonus content, and when the app will listen, gives them a reason to say yes. Our consent and permission UX checklist covers how to design that moment.

Other levers to test:

• Promote the experience in the space, with signs, announcements, or on-screen prompts that tell people what to open and why.
• Ask at a relevant time, such as right before a halftime moment, instead of at first launch.
• Make the reward clear and worth it. People opt in for something they want.

Change one thing at a time, and compare the rate before and after, so you know what worked.

Report it in a way clients trust

When you share results with a brand or sponsor, keep it simple:

• Show the full funnel, with counts and rates at each step.
• State the data source and time window for every number.
• Separate estimates, such as audience size, from measured events, such as detections.
• Note anything that affected the result, such as a late announcement or a venue Wi-Fi issue.

Agencies packaging tone work for clients can build this report into every offer. See how agencies can package tone activations for more.

Frequently asked questions

What is a good opt-in rate for a tone campaign?

It depends on the audience, the venue, the reward, and how the ask is made. Set a baseline in your first pilot, then measure changes against it.

Why does the app need microphone permission?

The phone has to listen for the inaudible tone to recognize it. iOS and Android both require the user to allow microphone access first.

Should we track people who deny permission?

Track the count of prompts shown and denied so you can measure the rate, without collecting more data than the experience needs.

Can GhostTones help set up measurement?

Yes. GhostTones works with brands and agencies to plan tone moments, the consent flow, and the measurement plan before a pilot launches.