Skip to main content

How to stop Meta from widening your retargeting audience

Meta's Automatic adjustments can switch on Advantage+ audience in your retargeting campaign. Turn off that one adjustment in Ads Manager.

Written by Paul

Your Adwisely retargeting campaign shows ads to people who visited your store. If Automatic adjustments is on in your Meta ad account, Meta can switch on Advantage+ audience in that campaign. Your ads then also reach people who never visited your store. Meta checks this every day, so it switches it back on even after it's turned off in the campaign. To stop it, turn off this one adjustment in your ad account.

Before you start

You need an admin or advertiser role on the ad account to change Automatic adjustments. If that isn't you, forward these steps to whoever manages your Meta ad account.

Turn off Advantage+ audience in Automatic adjustments

1. Open Meta Ads Manager and choose the ad account your Adwisely campaigns run in. Or click Open Ads Manager on the Adwisely banner: it opens the Manage automatic adjustments window for the right ad account, so you can go straight to step 3.

2. In the menu on the left, select Account overview. Then, next to Opportunity score, select Manage automatic adjustments.

3. Under Audience, click the arrow on the right to open it. Untick the box next to Advantage+ audience so the box is empty, like below. A tick means Meta keeps switching it on.

4. Select Apply changes.

5. Back in the Adwisely app, click Done on the banner.

What happens next

Turning the adjustment off stops Meta from changing your campaigns from now on, but it doesn't undo what Meta already changed. That's what Done is for: Adwisely switches Advantage+ audience off in your retargeting campaign, and your retargeting ads go back to people who visited your store.

The banner came back?

Then Advantage+ audience is still ticked in Automatic adjustments, usually because it was changed in a different ad account. Check the steps above, or message us from the app and we'll take a look.

Did this answer your question?