Connect Meta Ads
Connect Meta Ads to bring your Facebook and Instagram ad data into Commander. The connection also lets Commander deploy ads to your account. Find it at Settings > Integrations, on the Meta Ads card.
Problem and intended user
The media buyer (the person who runs your paid ads) needs Commander to read the right Meta ad account and to publish ads under the right Facebook Page, Instagram identity and pixel. A wrong or missing choice can send ad data from the wrong account, make a deployed ad fail, or leave conversions untracked.
Current workflow
Without Commander, the media buyer copies results from Meta Ads Manager into a spreadsheet to compare with store data. To launch an ad, they upload the creative there and pick the Page, Instagram account and pixel again for each campaign.
Prerequisites
- Meta ad account: one that you can access.
- Facebook Page: you need admin or advertiser access to it.
- Meta Pixel: Commander needs it for conversion tracking and Target ROAS bidding. You can connect without one and add it later.
- Browser: allow pop-ups for Commander. The Facebook login opens in a pop-up window.
- Ad budget: to create a campaign in Commander, you need an ad budget. See Set your ad budget below.
How Commander works
Commander reads ad data from the Meta ad account you choose, and uses your Page, Instagram identity and pixel when it deploys ads. Fixed rules do this work. AI does not take part.
You approve access yourself, in the Facebook pop-up or by creating a token in Meta. Each setup choice needs your Confirm (or Create Instagram identity), or you skip it. Each choice feeds one feature:
| Setting | What Commander uses it for |
|---|---|
| Ad account | The account that Commander reads ad data from. See Ad performance. |
| Facebook Page | The identity of your ad creatives when you deploy. |
| Instagram identity | Required on every ad that runs on Instagram placements (Feed, Stories and Reels). |
| Meta Pixel | Conversion tracking and Target ROAS bidding. |
Commander uses the connection in these places: Ad performance, Review and deploy ads, Campaigns, Launch monitor and Audiences.
Commander updates your Meta ads on its own while Meta is connected. Settings > Store Status shows the sync. See Store Status. To sync sooner, use Sync Now or Full Sync on Performance > Ad performance.
Choose the permission groups
Before you sign in or paste a token, the dialog asks What is this connection for? It shows three groups, all ticked. Each group turns on one part of Commander and asks Meta for the permissions that part needs.
| Group | What it turns on | Permissions it asks for |
|---|---|---|
| Audience sync | Sync your audiences to Custom Audiences. | Permission to manage ads. |
| Ad creation and deployment | Publish ads, and use conversion tracking and brand assets. | Permission to manage ads, Pages and your business. |
| Analysis | Sync ad performance. | Permission to read ads and stats. |
Ad creation and deployment includes Analysis. When you tick it, Analysis stays ticked and locked, with the note Included with ad creation and deployment. Commander needs ad performance to run ad rules, the launch monitor and budget rebalance.
Keep at least one group ticked. With none ticked, the dialog says Choose at least one permission group to connect and the title-bar button stays off.
Commander turns on only the groups whose permissions Meta granted. On Meta's consent screen you can untick permissions under Edit access. If you do, Commander connects the groups that still have all their permissions. If Meta granted no group's permissions, the dialog shows "Commander didn’t receive the permissions any feature needs. Connect again and keep at least one group’s permissions".
A group you leave out stays off. A feature that needs it tells you the connection doesn’t include it. Without Ad creation and deployment, Commander skips the Facebook Page, Instagram identity and pixel steps, and the dialog does not show those rows. Without Audience sync, Commander does not sync audiences to Meta.
A connection that you made before the groups existed has all three.
When you open a connected Meta Ads card, the Permissions row lists the groups the connection has, with a Change permissions button. Reconnecting keeps the groups the connection already has.
Change permissions
To change the groups of a connected account, open the Meta Ads card and click Change permissions. The dialog shows the three groups, with the ones the connection has ticked.
Until you change a tick, the dialog says No changes yet. After a change, If you save lists what it does. For each group you untick, a line says what stops, such as how many audiences stop updating on Meta or how many active ad rules stop running. Ads already live keep running with their current budgets. A group you tick shows as Added:, and nothing changes until you accept on Meta.
- Remove a group. Untick it, then click Save permissions in the title bar. Commander stops using that permission for this shop. No Meta sign-in is needed. Ad creation and deployment includes Analysis: unticking Ad creation and deployment leaves Analysis ticked, and you can untick it next.
- Add a group. Tick it. The title-bar button reads Continue to Meta. Click it, grant the new permission on Meta's consent screen and confirm the ad account. Nothing is added until you finish that sign-in. On the Enter Token tab, paste a token with the new permissions and click Save token instead. Your audiences stay as they are.
- Keep at least one group. To remove them all, click Disconnect.
- Change your mind. Cancel takes you back to the connection with nothing changed.
In Demo Mode, the dialog says Permission changes aren’t saved in demo mode.
INFO
Unticking a group does not remove the permission from your Meta account. Meta keeps listing the permissions you granted earlier, because it stores them on your Meta login, and that login may also connect your other shops to Commander. To remove them there, open your Meta business integrations settings and remove Commander. This removes the permissions for every shop connected with that login, and it disconnects all of them.
Choose how to connect
| Tab | Best for | Trade-off |
|---|---|---|
| Connect via OAuth | Most stores. You sign in with Facebook. | The token lasts 60 days. Commander renews it before it expires. The card shows the Valid until date. |
| Enter Token | Stores that want a connection that never expires. | You create a System User Token in Meta first. |
Connect with Facebook login
- Go to Settings > Integrations and click the Meta Ads card.
- Stay on the Connect via OAuth tab.
- Under What is this connection for?, keep the groups you want ticked.
- Click Connect Meta Ads.
- Sign in and approve access in the pop-up window.
When the pop-up closes, Commander moves you to the setup steps below. If Facebook still asks you to sign in, the dialog tells you to finish signing in with Facebook in the window that opened. Commander continues when you're done.
Connect with a System User Token
- Open the Meta Ads card and select the Enter Token tab.
- In Meta Business Settings, open Users > System Users. Create a System User with the Admin role, or select an existing one.
- Click Add Assets. Add your ad account with Full Control.
- Under Apps, select your app. Click Add People and give the System User the Admin role.
- Back in System Users, click Generate New Token. Enable the permissions of the groups you ticked in Commander. See the list under these steps.
- Set the token expiration to Never. Click Generate Token and copy the token.
- Paste the token into System User Token in Commander.
- Click Save and validate.
The token tab uses the same What is this connection for? groups. Tick the groups before you click Save and validate. The token needs the permissions of each group you tick:
| Group | Permissions the token needs |
|---|---|
| Audience sync | ads_management |
| Analysis | ads_read |
| Ad creation and deployment | ads_management, pages_show_list, pages_read_engagement, pages_manage_ads and business_management, plus ads_read for Analysis |
Commander turns on only the groups whose permissions the token has. If the token has no group's permissions, the dialog shows the message above, and you generate a new token.
To limit Commander to one ad account, connect with a system user token that has access to that ad account only. In step 3, add only that ad account to the System User. Tick only the groups you need.
Pick what Commander uses
WARNING
If you skip a step, the card shows No ad account selected, No page connected or No pixel connected. Meta requires an Instagram identity on ads that run on Instagram, so ad deployment fails until you resolve a skipped Instagram step.
After you connect, Commander asks for up to four choices, one after the other. Each step has Skip for now. The steps that ask you to select something also have Confirm. A connection without Ad creation and deployment has only the ad account step.
- Select Ad Account. The list shows only the ad accounts that the Facebook login you just signed in with can reach. It never shows the accounts of a login someone else made earlier. Select the account and click Confirm. Nothing changes until you click Confirm: that replaces the stored Meta sign-in and the ad account in one step. Click Skip for now (Cancel reconnect when you are repairing a broken connection) or close the dialog to keep the connection as it was. The new sign-in or token is dropped. A pasted System User Token counts as a sign-in: it is checked on Save and validate, but it replaces the stored one only when you click Confirm. It also expires if you leave the step open.
- Select Facebook Page. Select the Page to publish ads from and click Confirm.
- Instagram identity required. This step appears only when your Page has no linked Instagram Business Account and no Page-Backed Instagram Account. Click Create Instagram identity. Meta creates a Page-Backed Instagram Account from your Page. It does not need an Instagram sign-up and does not show as a public profile. To use a real account instead, link it to your Page in Meta Business Suite, then reopen the dialog.
- Select Meta Pixel. Select the pixel and click Confirm.
If the pixel list is empty, the step shows No Meta Pixels found for this ad account. Create a pixel in Meta Events Manager. Choose Connect Data Sources, then Web. Name the pixel and enter your website address. Come back and click Refresh.
Set your ad budget
- Open the Meta Ads card after you connect.
- Select Set up ad budget.
- Enter the Monthly Budget. The form shows the daily amount under it.
- Choose a Bid Strategy: Lowest Cost, Cost Cap, Target ROAS or Maximize Value.
- Enter Target CPA when you choose Cost Cap, or Target ROAS (×) when you choose Target ROAS.
- Click Save.
An empty or zero amount shows Monthly budget must be greater than 0. Target ROAS shows a warning when no Meta Pixel is linked.
After you save, the panel reads Ad Budget and shows Monthly, Daily, Strategy and Campaigns. Click Edit to change it. For the rest, see Campaigns.
WARNING
Rebalance acts at once and asks for no confirmation. It splits the daily budget equally across your campaigns and updates the daily budget of campaigns already deployed on Meta. It stays off while you have only one campaign, or none.
Check or change your connection
Open the Meta Ads card at any time. On the Instagram row, Change opens Instagram identity. Click Refresh from Meta there to pick up a newly linked Instagram account.
Click Check connectivity to test the connection. If it is expired or in error, check again, or click Disconnect and connect again.
Disconnect acts at once and asks for no confirmation. It deletes the Meta sign-in that Commander stored, and the ad account, Page, Instagram identity and pixel you chose. After you connect again, choose them again. It does not delete or pause ads you already published. Ads that already run in Meta keep running. Commander stops reading and managing them until you connect again.
Disconnect does not remove the Commander app from your Meta account. To remove the app there, use Meta Business Settings.
Commander encrypts your credentials before it stores them.
Reconnect when Meta stops the connection
Meta can end a connection that looks valid, for example after a password change or a security check. Commander then cannot read your ads, and the ad sync stops. Commander shows this in two places:
- Performance > Ad performance shows the card Meta Ads needs to be reconnected. It says: "The ad sync stopped. Reconnect to import the missing days." If Google Ads has the same problem, the title reads Meta Ads and Google Ads need to be reconnected.
- On Settings > Integrations, the Meta Ads card shows the ERROR badge. Open the card. The dialog shows Connection error with the message "Meta no longer accepts this connection. Reconnect Meta Ads to resume the ad sync".
How you reconnect depends on how you connected.
If you connected with OAuth
WARNING
An OAuth reconnect takes effect when you click Confirm on Select Ad Account, not when you sign in. It then clears your ad account, Page, Instagram identity and pixel choices. Select them again, or the sync cannot resume. If you click Cancel reconnect, the connection stays as it was.
- Click Reconnect on the card. The accessible name is Reconnect Meta Ads. The Meta Ads dialog opens.
- Click Reconnect Meta Ads.
- Sign in and approve access in the pop-up window.
- Select your ad account in Select Ad Account and click Confirm. Choose the Page, Instagram identity and pixel again.
If you connected with a System User Token
The dialog has no Reconnect Meta Ads button. It says "Enter a new System User Token below" and shows the token form.
- Open the Meta Ads card.
- Paste a new System User Token.
- Click Save and validate. Commander checks the token and holds it aside. It does not replace the stored token yet.
- On Select Ad Account, your current ad account is selected if the token can reach it. Click Confirm to finish. Click Cancel reconnect to keep the stored token. If the account stays the same, your Page, Instagram identity and pixel choices stay.
Commander imports the missing days on the next sync. Use Sync Now on Performance > Ad performance to start it sooner. If you restore the permission in Meta without reconnecting, the next sync can clear the card by itself.
Read-only access
Support can turn off write access to Meta Ads for your store. This typically happens when the connected login can only view your account. Commander then reads your Meta Ads account but changes nothing in it. To turn write access back on, contact support.
Disconnecting and connecting Meta Ads again does not change this. Read-only stays on until support turns it off.
When write access is off, the Meta Ads card on Settings > Integrations shows a READ-ONLY badge next to the connection status. Every control that would change something in your Meta Ads account is greyed out. This includes Deploy and Retry Deploy on a generated ad, so you learn it before you fill in the deploy form. Hover over the control or focus it to read: "Write access to Meta Ads is turned off for this store. Contact support to turn it on."
If you click or tap a greyed-out control, the same message shows in a notice at the bottom of the page. In an ad's detail panel, it shows under the panel's buttons instead. The notice also shows if a page you opened before the change tries to change Meta Ads: Commander refuses the change and greys out the page's controls. The notice stays until you close it.
These actions are off for Meta Ads:
- Deploy ads, one at a time or in bulk.
- Archive ads and campaigns, and pause or resume campaigns.
- Create a campaign or an ad set in the deploy form, and remove one the form created. Create, edit, pause, resume or archive an ad set in Performance > Ad Containers.
- Send a budget change, and Rebalance a budget pool.
- Sync an audience to Meta Ads, and create a lookalike audience.
- Approve a decision that changes your Meta Ads account.
- Ticking Disabled to turn on an Auto Rule that targets only Meta Ads. A new Auto Rule that targets only Meta Ads is created turned off. When every ad platform you connected is read-only, the Auto Rules modes Require human approval for all and Auto-approve where allowed are off too.
- Select Pause, Resume or Activate on an ad.
- Select Kill on an ad in Launch Monitor. Kill pauses or archives the ad.
These actions still work:
- Reading and reporting: sync and performance pages.
- Viewing Launch Monitor.
- Creating and editing ad drafts.
- Preparing campaigns in Commander.
- Changing your budget pool settings.
- Creating rules.
- Renaming or deleting an audience. This changes only the Commander copy. The copy in Meta Ads stays as it is.
Auto Rules and automatic lifecycle actions skip Meta Ads. Commander changes nothing in your Meta Ads account.
Exact output
The dialog before you connect
It has the Connect via OAuth and Enter Token tabs and the Connect Meta Ads button.
The reconnect card
When Meta ends the connection, Performance > Ad performance shows this card.
The dialog after you connect
The dialog shows:
- The status: Connected, Connection expired, Connection error or Status unknown.
- A label for the method: OAuth or System User Token.
- The dates next to Connected, Expires and Checked. Expires shows only when the connection has an expiry date.
- The Permissions row, with the groups the connection has and a Change permissions button.
- Rows for Ad Account, Page, Instagram and Pixel (the last three only with Ad creation and deployment), each with a Change or Select button. On the Ad Account row the buttons read Change account and Select account. They open Select Ad Account, which offers the same two ways in as a first connection: Sign in with Facebook, or paste a System User Token and click Save and validate. The list that follows is for that login or token. The Instagram row offers Change only after you select a Page.
- The Set up ad budget button. After you save a budget, an Ad Budget panel with Monthly, Daily, Strategy, Campaigns, Edit and Rebalance replaces it.
On the Meta Ads card, Valid until shows the expiry date of an OAuth token and the days left. The card turns amber when the date is close.
What to do with it
| What you see | Decision or action | Owner |
|---|---|---|
| No ad account selected, No page connected or No pixel connected on the card | Open the card and finish the open step. | media buyer |
| Pixel list is empty | Create a pixel in Meta Events Manager, outside Commander. Then click Refresh. | media buyer |
| Meta Ads needs to be reconnected, or the ERROR badge on the card with the message "Meta no longer accepts this connection. Reconnect Meta Ads to resume the ad sync" in the dialog | With OAuth, click Reconnect, sign in, then select the ad account again and click Confirm. With a System User Token, enter a new token and click Save and validate. | media buyer |
| Connection expired or Connection error | Click Check connectivity. If it still fails, click Disconnect and connect again. | media buyer |
| No ad budget in the dialog | Select Set up ad budget and save a budget. | media buyer |
| An amber Valid until date on an OAuth connection | Wait. Commander renews the token before it expires. Act only when the status shows Connection expired or Connection error. | media buyer |
| You want a token that never expires | Click Disconnect, then connect with Enter Token. | media buyer |
| A READ-ONLY badge on the card, or a greyed-out control or a notice at the bottom of the page with the message "Write access to Meta Ads is turned off for this store. Contact support to turn it on." | Contact support to turn on write access. See Read-only access above. | media buyer |
Expected value and measurement
A complete connection can help you see Meta results beside your store data, and deploy ads with every identity in place.
To check it, open Settings > Integrations and confirm the Meta Ads card shows CONNECTED and no amber warning. Then open Performance > Ad performance, choose Meta, and compare You spent with Meta Ads Manager for the same dates. The status bar shows the last sync.
Check that the pixel records conversions in Meta Events Manager, outside Commander. You cannot isolate the effect of the pixel on Target ROAS bidding from other changes made at the same time.
Limitations and exceptions
- Meta only. For Google ads, see Google Ads.
- A missing group. A connection without Ad creation and deployment does not publish ads or track conversions. Without Analysis, it does not sync ad performance. Without Audience sync, it does not sync audiences. A feature that needs the missing group tells you the connection doesn’t include it. Click Change permissions to add it.
- Meta shows "No permissions available". If this happens in step 5 of the System User Token steps, repeat step 4.
- Empty ad account list. The step shows No ad accounts found for this connection.
- List errors. The Page step can read Could not load pages. Make sure your Meta account has Page access. Click Skip for now to leave the step. The pixel step can read Could not load pixels. Make sure an ad account is selected. Click Go to connection settings to leave it.
- Unhealthy connection. Status unknown means Commander has not confirmed the connection. If Commander cannot renew an OAuth token, the status can turn to Connection error and the card badge reads ERROR. The dialog then tells you to use Check connectivity, or to disconnect and reconnect. Commander shows the problem on the card and in the dialog only.
- Ended connection. When Meta ends the connection, the ad sync stops until you reconnect. Commander keeps the data it already imported. It imports the missing days on the next sync after you reconnect. Commander tells you on the sync card, on the Meta Ads card badge and in the card dialog. See Reconnect when Meta stops the connection above.
- Failed saves. An empty token field shows Please enter a System User Token. Another failed save shows a red message, such as Failed to save credentials. Try again.
- Read-only access. When support turns off write access, Commander still reads your Meta Ads data. It disables every control that changes your Meta Ads account. See Read-only access above.
- Demo Mode. Commander blocks connecting and disconnecting a real ad platform. It shows messages such as Disable demo mode to connect real integrations. Choosing an account, Page, Instagram identity or pixel is simulated and changes nothing in Meta.