> For the complete documentation index, see [llms.txt](https://support.sayprimer.com/primer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.sayprimer.com/primer/primer-support-legacy/troubleshooting-connections/meta-troubleshooting/junk-leads-because-of-advantage+-audience-setting.md). # Junk Leads Because of Advantage+ Audience Setting Meta now defaults to their Advantage+ Audience feature, which automatically expands targeting beyond your selected audience. We don’t recommend using this with Primer audiences, as it can dilute targeting precision. Follow the steps below to turn this setting off: {% embed url="" %} #### Steps to Turn Off Advantage+ Audience in Your Ad Set **Step 1: Locate the Advantage+ Audience Setting** * Open Facebook Ads Manager. * Select the campaign or ad set where you want to disable Advantage+ * Scroll down to the Audience section. * If you see the **Advantage+on** icon, it means Advantage+ Audience is currently active. **Step 2: Disable Advantage+ Audience** * Click the **Remove Saved Audience** button to eliminate the Advantage+ Audience feature from your ad set. * Locate the option labeled **Further limit the reach of your ads** and select **Switch setup** to proceed. **Step 3: Configure Your Custom Audience** * Navigate to the Audience settings panel. * Select Custom Audiences and add back the audience segments you want to target. **Step 4: Publish Your Changes** * After making the adjustments, click **Publish** to save your changes. Your Advantage+ Audience should now be disabled, and your manual targeting will be applied instead. Contact our [Support team](mailto:support@sayprimer.com) for additional help! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://support.sayprimer.com/primer/primer-support-legacy/troubleshooting-connections/meta-troubleshooting/junk-leads-because-of-advantage+-audience-setting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.