Instagram Business Insights Approved After Six Rejections (2026 Case Study)

The founder of an Instagram insights product needed professional-account metrics inside the app after Instagram Login. The same two permissions had already come back not approved six times. Around mid-September the site and server were down, so a reviewer could not open the product at all. They hired us so the next attempt would not burn another row while the live app was unreachable. This instagram business insights case is the pass: Meta approved the Instagram Login pair on 23 September 2026. If your insights dashboard keeps failing while the site cannot be opened, start here.

What the Instagram insights product needed

A PDF of past submissions is not enough. Reviewers need the live product: Instagram Login, a connected professional account, and insights rendered in the app. The Permissions Reference is the list that recording has to cover for an instagram business insights package.

This job was the Instagram Login pair — not Facebook Login, and not publishing:

• instagram_business_basic — the basic Instagram Business access on Instagram Login.
• instagram_business_manage_insights — the instagram business insights read on the professional account the app is allowed to use.

No other permission sat in this decision. Publishing a photo or Reel is a different review, covered separately in the instagram_content_publish note. The Facebook Login insights family (instagram_basic / instagram_manage_insights) is a different case entirely — see instagram manage insights approved when that is the login path you actually use.

The founder needed both rows green on one card. We refused to treat an offline site as review-ready. We needed admin access on the app, a demo login, and a product a reviewer could open.

Why six prior rows came back not approved

The approval screen does not print Meta’s written feedback for those six attempts, and this page does not invent reviewer note text that was never in the thread. What the history does show is six not-approved rows for the same two permissions. The timestamps, all GMT+5:30, are 3 September 2026 at 17:07, 5 August 2026 at 21:28, 30 July 2026 at 14:08, 16 July 2026 at 07:33, 23 June 2026 at 13:00, and 2 June 2026 at 13:29.

Every one of those rows listed instagram_business_basic and instagram_business_manage_insights as new requests, and both came back not approved. Separate screencasts per permission and an earlier submission PDF already existed. None of that helps if the live product cannot be opened when the reviewer arrives.

Around 16 September the website was down. An instagram business insights review cannot be checked against a server that does not answer. That is the failure cause we acted on: site and server unreachable, so the insights screen could not be verified — independent of whatever generic banner the earlier cards carried. Work on the recording resumed only after the site was back.

Resubmitting the same unreproducible video while the product is still offline can lead to an App Review cooldown of about 7 days. That figure is widely reported. It is not a number printed on this screen. Six not-approved rows already sat above the approved card. Another identical attempt would have added a row, not an explanation.

What we fixed for App Review

The fix was operational before it was cinematic. We waited until the site answered again. Then we used admin access on the app and a demo login so the recording could be checked against the running product — login, connect a professional account, open the insights view the product already had for that account.

One screencast per permission, on a site a reviewer can actually load, is the difference this history can support. It is not a claim about a sentence Meta did not write on the earlier cards. A reviewer who cannot open the product cannot confirm an instagram business insights permission, no matter how complete an earlier PDF looked.

We kept the request narrow: the Instagram Login pair only — an instagram business insights ask, not a publishing bundle. We did not bundle publishing. We did not switch the login family mid-package. Developer Policies text last updated 3 February 2026 still expects the app to follow the Developer Docs for allowed usage; we did not invent policy section numbers for this case.

The 23 September result

Meta marked it submission approved. The line on the screen is that the review is complete and the requests and app settings were approved. Submitted at 22:14 GMT+5:30. Under new requests, both permissions show Approved and Usage guidelines:

• instagram_business_basic
• instagram_business_manage_insights

That is the instagram business insights card this case is about. Six not-approved rows for the same instagram business insights pair sat above it. Chat later confirmed the approval on 27 September; the Meta screen itself is the 23 September submission, not that later message.

Other published outcomes live on the case studies page. Do not treat this Instagram Business result as proof for content publishing, or for a Facebook Login insights scope.

If your Instagram Login insights pair keeps failing

If your product needs to pull Instagram professional insights after Instagram Login, and the card keeps saying not approved while the site was down or unreachable during review, this is exactly the kind of Meta App Review project we handle. Send the six-row history shape — or whatever count you have — and say whether the product was online when the reviewer would have watched. Do not upload another video against a dead server.

The managed path is the Instagram App Review service. Page-side Facebook work, when you need it, is on the Facebook App Review service. An instagram business insights pass on one insights product is not a template for a publishing app or for the other login family.