Instagram account not showing in Ads Manager: the causes, and when you do not actually need it
The empty Instagram dropdown blocks more launches than any policy. Usually it is a connection or permission issue; sometimes the right answer is that you can launch without it, because Meta runs Instagram ads on your Page identity.
First, the part nobody tells you
You do not need a connected Instagram account to run ads on Instagram placements. Meta's own help page ("Run ads on Instagram with your Facebook Page") walks through it: at the ad level you connect a Facebook Page in the Identity section, and "the Page that you've connected has automatically been selected to be the voice of your ads on Instagram."
What Meta creates under the hood is a Page-backed Instagram account. Meta's developer documentation describes it plainly: "That Instagram account gets the name and profile picture from the Page, and can be used to run ads. However it cannot perform any organic activities, such creating non-ad posts, commenting, or liking."
The trade-off is real but small for pure performance ads: taps on your profile go nowhere useful and you cannot reply to comments from that identity. For a brand building an Instagram presence, connect the real account. For "the dropdown is empty and the batch has to go out", the Page is enough.
The causes when the account should be there and is not
Work down this list in order; each step gates the next.
1. The Instagram account is not linked to the Page you selected
The identity dropdown shows Instagram accounts connected to the selected Facebook Page. Right Page, no link: empty dropdown. Fix it in the Page's settings (Linked accounts) or in the business portfolio, then reselect the Page in Ads Manager.
2. It lives in another business portfolio
Meta is strict here: "Each Instagram account can only be added to one business portfolio." Agencies hit this when a client's Instagram was once claimed by an old agency's portfolio; it must be removed there before it can be added where the ad account lives. Adding it requires "full control of the business portfolio" per Meta's help.
3. You do not have the asset permission
Even with everything connected, Meta scopes visibility: "Only people with access to this Instagram account's ad accounts can use it to advertise." If a colleague sees the account and you do not, this is it; fix it in the portfolio's people-and-assets settings.
4. The account type
A personal Instagram account behaves differently from a professional (business or creator) one in business tooling. Converting to professional in the Instagram app is free and reversible, and it is the state Meta's business flows assume.
Once connected, Meta's help notes the upside for future launches: "New campaigns and ad sets will automatically include Instagram as a placement, and you can link new ads to this Instagram account."
The API side, for completeness
In the Marketing API the identity is set on the creative: historically instagram_actor_id, renamed to instagram_user_id (announced January 2025, with Marketing API migration running until 21 January 2026). Omit it and the creative runs on the Page-backed identity, which is exactly the fallback described above.
Adlio validated this against the live API: a creative with only page_id is accepted, which is why Instagram is a recommended step in Adlio's setup, not a blocking one. When an Instagram account is configured for the ad account, Adlio sends it on every creative; when not, your batch still launches, on the Page identity, paused as always.
For the batch you are launching today
- Dropdown empty and you need the real account: run the four causes above, in order; it is almost always cause 1 or 2.
- Dropdown empty and the batch matters more than profile taps: launch on the Page identity and connect Instagram properly this week.
- Either way, identity is check 1 on the pre-launch QA checklist: open one ad from the paused batch and confirm which name and photo it will run under, on both platforms.
Multi-account footnote: the Instagram identity belongs to the same per-account record as the pixel and DSA fields, see managing multiple ad accounts. A client A identity on a client B ad is the expensive version of this problem.
Adlio stores the Page and Instagram identity per ad account and fills them on every ad of a batch; the launch flow itself is on bulk upload Facebook ads from a folder.
Frequently asked questions
Can I run Instagram ads without an Instagram account?+
Yes. Meta's help page "Run ads on Instagram with your Facebook Page" documents it: connect a Facebook Page in the Identity section and "the Page that you've connected has automatically been selected to be the voice of your ads on Instagram". Behind the scenes this is a Page-backed Instagram identity: it "gets the name and profile picture from the Page, and can be used to run ads", but cannot post, comment or like organically.
Why does my Instagram account not appear in the identity dropdown?+
The usual causes, in order: the Instagram account is not connected to the Facebook Page you selected; it sits in a different business portfolio (Meta: "Each Instagram account can only be added to one business portfolio"); or you lack the asset permission (Meta: "Only people with access to this Instagram account's ad accounts can use it to advertise"). Fix the Page link first, then the portfolio assignment, then your own access.
Does Adlio require an Instagram account?+
No. Adlio recommends connecting one (comments and profile taps land on your real account) but launches with only a Facebook Page: we validated against the live API that Meta accepts a creative with just the page_id, and Instagram placements then run on the Page-backed identity.
Adlio team
Built by media buyers who launch Meta ads in volume. Questions or corrections: support@adlio.ai.
Topic cluster
Launch hygiene and QA
Naming, UTMs, identity, DSA and the paused review that makes a bulk batch safe to set live.
- Meta ads naming convention: a template you can copy, and how to apply it to every ad
- UTM parameters for Meta ads: set them once per account, apply them to every ad
- The pixel and conversion event per ad account: set once, verify on every launch
- Instagram account not showing in Ads Manager: the causes, and when you do not actually need it
- Adding ads to an existing ad set: what it does to the learning phase, budget and delivery
- Facebook ad review when you publish in bulk: timing, re-review triggers, and the paused-ads advantage
- Rolling back a bulk launch: pause many ads at once without resetting learning
- Managing multiple Facebook ad accounts: how to keep client A's settings out of client B's ads
- Meta ads in the EU: the DSA beneficiary and payer fields, and how to stop them blocking your launches