🔍 What Is Happening?

When Search Atlas generates a budget recommendation for your Meta Ads campaign, it pulls performance data directly from the Meta Pixel. This means only the conversion events that have been reported back to Meta are factored into the calculation. If your business records conversions outside of Meta — such as phone orders, in-person machinery sales, or any transaction you intentionally keep offline — those events are invisible to the guidance engine.

The result is a recommended budget that can appear significantly lower than what your real-world ROAS would justify. This is a known limitation of the current system.

⚙️ Why the Guardrail Exists

The budget guidance guardrail is designed to protect advertisers from overspending when there is insufficient conversion signal in Meta to validate a higher budget. Because the system can only read what Meta reports, it treats low Pixel conversion volume as a risk indicator — even when your actual business performance is strong. This is not a judgment on your ROAS; it is a data-visibility constraint.

Common scenarios where this mismatch occurs:

• High-ticket or industrial products (e.g., heavy machinery) sold offline or over the phone
• B2B businesses where deals close through a sales team, not a web form
• Businesses that deliberately limit Meta Pixel data for privacy or competitive reasons
• Multi-channel businesses where most revenue happens in physical locations

🚀 What You Can Do

The ability to account for offline conversions in budget recommendations is not currently available in the platform. This is a recognized product gap. While our team is aware of this limitation, the following workarounds may help in the meantime:

1. Consider adding a Meta Custom Conversion as a proxy signal. If you are able to pass even a partial signal back to Meta — such as a lead form submission, a quote request, or a phone call tracked via a third-party call tracking tool — setting up a Custom Conversion in Meta Events Manager can improve the quality of future budget recommendations. This is optional and only worthwhile if it aligns with your privacy and reporting strategy.
2. Document your offline ROAS separately. Keep a record of your true blended ROAS outside of Search Atlas so you can evaluate campaign performance against your real business outcomes, not just the Pixel-reported figures.
3. Request this feature. If accounting for offline conversions in budget guidance is important to your workflow, please have the following ready when contacting support: your project or account name, the specific campaign(s) affected, the approximate volume and type of offline conversions you record, and a description of how this limitation is impacting your budget decisions. This context helps our team prioritize and document the request.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.