Running facebook ads for ndis providers can become frustrating when a useful, factual ad is rejected before it reaches anyone. Sometimes the problem is a sentence that appears to identify the viewer’s disability. Sometimes it is the destination page, an image or a restriction affecting the business account rather than the ad itself.

The safest response is not to keep submitting slightly different versions and hope one passes. Identify what Meta has flagged, check the entire enquiry journey and resolve the underlying issue.

This guide explains how to investigate rejected ads, distinguish them from account restrictions and prepare a clear review request without using risky workarounds.

First, identify what has actually been rejected

Before changing your campaign, record the exact status and policy message shown in Meta’s advertising tools. Interface labels and review options change, so follow the prompts available in your account.

Three situations need different responses:

• An individual ad is rejected: investigate its wording, imagery, form and destination page against the cited policy.
• An advertising asset or user is restricted: check whether the issue affects a personal advertising account, ad account, Page or business portfolio.
• An approved ad is not delivering: investigate payment, scheduling, campaign settings and delivery issues rather than rewriting it as a policy fix.

Save the ad ID, screenshot the notice and note when the status changed. If someone else manages your advertising, ask them to provide the actual message rather than simply saying “Facebook blocked it”.

Why Facebook ads for NDIS providers get rejected

Advertising disability supports is not automatically prohibited. However, wording that seems ordinary on a provider website can create problems when delivered directly to an individual in their feed.

Personal attributes implied by the wording

Meta’s personal attributes policy restricts ads that assert or imply sensitive information about the viewer, including disability or health conditions. The distinction is between describing a service and suggesting that the advertiser knows something personal about the person seeing it.

• Avoid: “Do you have a psychosocial disability and need support?”
• Try: “Explore psychosocial disability support services in Newcastle.”
• Avoid: “Struggling with your autism support?”
• Try: “Learn about our approach to autism support and meet the team.”

These alternatives are not promises of approval. They illustrate a better principle: describe what your organisation offers without assigning a diagnosis, condition or personal difficulty to the viewer.

Claims that go beyond what you can substantiate

Statements such as “guaranteed funding”, “instant NDIS approval” or “the best support workers in Australia” create problems beyond platform review. They can mislead people about eligibility, outcomes or the provider’s role.

Use specific, verifiable information instead: your service area, the supports offered, the enquiry process and current availability. Only describe your organisation as a registered NDIS provider if that is accurate.

Images and video that change the message

Review text overlaid on images, captions, voiceovers and thumbnails. Neutral ad copy does not fix a video that makes unsupported promises or uses distress to pressure people into enquiring.

Use respectful, relevant visuals with appropriate permission. Where participants appear, consent should cover advertising use, not merely taking a photo. Do not disclose someone’s diagnosis or circumstances simply to make the creative more persuasive.

Check the landing page, not just the ad

Meta can assess an ad’s destination as part of its review. An ad with careful wording may still encounter problems if the linked page is misleading, broken or inconsistent with the offer.

Open the destination on a phone and check:

• The page loads: there are no broken links, redirect loops or error messages.
• The offer matches: an ad about community participation leads to relevant service information, not an unrelated vacancy page.
• The provider is identifiable: visitors can find your business name and contact details.
• Claims are consistent: registration status, availability and service areas match across the ad and website.
• The next step is clear: visitors understand whether they are requesting information, a callback or an intake discussion.
• Privacy information is accessible: people can understand how enquiry information will be handled.

Avoid implying that clicking an ad secures funded support. A person’s circumstances, funding arrangements, service suitability and provider capacity may still need to be discussed.

Keep sensitive information out of the initial lead form

A Facebook lead form can make enquiries convenient, but it should not become a clinical intake form.

Review Meta’s current lead ad requirements before choosing questions. Sensitive information, including health and disability information, is subject to platform restrictions. A privacy notice does not automatically make every question acceptable.

For an initial contact request, consider limiting fields to:

• Name.
• Preferred contact method.
• Phone number or email address.
• A suitable time to get in touch.

Move detailed suitability and intake questions into an appropriate, secure process after contact. Explain why information is needed and avoid collecting more than necessary.

Also check what your website tracking sends to Meta. Do not include diagnoses, NDIS numbers or sensitive intake answers in event names, page URLs or tracking parameters. If you are unsure, have the implementation reviewed rather than assuming a standard plugin configuration is safe.

Should you edit the ad or request a review?

Use the cited policy and the actual ad content to decide. Repeated submissions without a clear diagnosis create confusion and do not resolve the underlying issue.

Edit when you can identify the problem

If the copy directly addresses a viewer’s disability, rewrite it around the service. If the destination contains an unsupported claim, correct the page before resubmitting. If a lead form asks for restricted information, simplify it.

Keep a record of what changed. This helps your team distinguish a genuine correction from another version of the same problem.

Request a review when the rejection appears incorrect

If the ad appears to comply with the cited policy, use the review option provided in your account. Keep the explanation brief, factual and tied to the specific issue.

A review note might say: “This ad describes community participation services available in Geelong. It does not assert that the viewer has a disability or health condition. The linked page explains the service and enquiry process. Please review the rejection under the cited personal attributes policy.”

Only use that explanation if it accurately describes your ad and page. Review outcomes and timing can vary; avoid planning a time-sensitive launch around an assumed approval date.

Handle account restrictions separately

An account restriction may require action that an ad edit cannot solve. Check the notice for identity confirmation, business verification, security or other account-level requirements.

Ask an authorised administrator to check:

• Who owns the affected business assets.
• Whether the correct people have access.
• Whether there are unfamiliar users or unexpected account changes.
• Which verification or security steps Meta has requested.
• Whether a review option is available for the specific restriction.

Complete requested checks through Meta’s official tools. Do not share passwords or verification codes with anyone claiming they can “unlock” an account.

Do not create replacement accounts or disguise the destination to bypass enforcement. Resolve the restriction through the available process. If you suspect compromise, secure the account and remove unauthorised access promptly.

Build a simple pre-launch approval checklist

Reducing avoidable rejections is easier when policy checks happen before launch, not after the campaign owner receives an alert.

Give one person responsibility for checking the full journey: ad copy, creative, form, destination and tracking. Confirm service availability with your intake team, and ensure the language remains accurate and person-centred.

Keep a shared rejection log containing the ad ID, cited policy, original wording, correction and review outcome. Use it to improve future briefs, while remembering that previous approval does not guarantee future approval.

If different suppliers manage your website and advertising, make ownership of fixes explicit. Our NDIS marketing services can help bring campaign planning, website messaging and the enquiry journey together.

Need help working through rejected ads and improving your campaign process? book a free strategy call with NDIS Advertising.

Frequently asked questions

Can NDIS providers advertise on Facebook?

Yes, advertising disability support services is not automatically prohibited. Ads must comply with Meta’s applicable policies and Australian advertising obligations. Describe services accurately without implying that you know the viewer’s disability or health condition.

Why was my Facebook ad rejected for personal attributes?

The wording or creative may imply that the viewer has a disability, diagnosis or another sensitive personal attribute. Check the exact policy notice and describe your services without assigning a condition to the person seeing the ad.

Should I edit a rejected NDIS ad or appeal it?

Edit it when you can identify a policy issue, including problems on the destination page or form. If the rejection appears incorrect, request a review through the option available in your account and explain how the ad complies with the cited policy.

Can I ask for a diagnosis in a Facebook lead form?

Meta restricts the collection of sensitive information through lead ads. Avoid using the initial form to collect diagnoses, NDIS numbers or detailed support information. Check the current requirements and move necessary intake questions into an appropriate, secure process.