Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Since I added a consent prompt to my app, my analytics numbers collapsed

Short answer

Analytics can only count users after collection is switched on, so users who decline or never see the prompt drop out of your numbers. Apple separates tracking permission from analytics that stays within your own apps. Ask your developer what each prompt switches off, and compare the numbers from before and after.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • My user numbers fell sharply the week the consent prompt was released.
  • Some screens or events show far fewer users than my sales suggest.
  • New installs appear in the store but not in analytics.
  • Our reports before and after the update cannot be compared.
  • Nobody knows which prompt controls which tool.

Why does this happen?

  1. Collection is switched off until the user agrees

    Firebase documents a setting that keeps Analytics collection off until you get end-user consent, and a call that turns it on afterwards. Until then, nothing is collected from that user.

  2. The choice is remembered and overrides the default

    Firebase says the runtime setting persists across app launches and overrides the value in the app's settings file. A user who declined stays uncounted until the app switches collection on again.

  3. Withdrawing consent removes user properties

    Firebase says that if a user withdraws consent for Analytics or ad storage, Google Analytics deletes all user properties, including their ad personalization consent, unless your app restores it.

  4. Apple's tracking prompt is a different thing from analytics

    Apple requires permission for tracking, which it defines as linking your app's data with data from other companies for advertising or measurement. It says the identifier for vendor can be used for analytics across apps from the same provider without the tracking prompt. If both are set up as one switch, analytics can be turned off by a prompt that was only meant for ads.

  5. A tool or SDK is wired to the wrong prompt

    An analytics or ad SDK can be started before the answer is known, or never started at all after a decline. The result is gaps that depend on the order the app runs things in.

What can I do about it today?

  1. Write down the release date of the promptThe date of the drop and the date of the release should match. If they do not, the cause is probably something else.
  2. Compare against numbers you trustStore installs, sales or support requests are not affected by the prompt. If those held steady while analytics fell, the prompt is the likely cause.
  3. Ask for a one-page listAsk your developer to list every prompt in the app and which tools each one turns on or off.
  4. Do not remove the prompt yourselfIf it was added for a legal or policy reason, removing it can create a new problem. Decisions about what you must ask are for your own adviser.
  5. Mark the date in your reportsA note on the date the data changed stops people drawing the wrong conclusions from the before and after charts.

When should I bring someone in?

  • Your decisions depend on analytics that now look wrong.
  • The app has several tools (analytics, ads, crash reports) and nobody knows which prompt covers which.
  • You need to change what the prompt controls, without breaking store rules.

How do I handle it?

  1. Map prompts to toolsI list each prompt, each tool that starts after it, and what happens on yes, no and no answer.
  2. Test every outcomeI run the app with accept, decline and never-seen cases and check what is collected each time.
  3. Separate analytics from advertising trackingWhere the store rules allow it, analytics that stays within the app is kept apart from tracking for ads, so one answer does not switch off both.
  4. Explain the legal side as a question for your adviserI do not give legal advice. I tell you what the app does, and you decide the rules with your own adviser.
  5. Annotate the dataThe change date is recorded so old and new numbers are read correctly.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Do I have to show the Apple tracking prompt for analytics?

Apple's page says the prompt is for tracking, meaning linking your data with other companies' data for advertising or measurement, or sharing with data brokers. Whether your app does that depends on its tools, so ask your developer, and your adviser for legal questions.

Can I recover the missing data?

Not for users who were never counted. What you can do is fix the setup going forward and mark the date of the change.

Is this legal advice?

No. I describe what the technology does. What you are required to ask users is a question for a qualified adviser.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.