Advertising feedback
Meta Ads traffic quality and Pixel control
Use traffic evidence to investigate Meta Ads visits and manage Meta Pixel loading on selected website paths.
On this page
What Button controls for Meta
Button can use visitor classification to decide when the configured Meta Pixel loads on selected paths. Smart Bidding Training loads the configured Pixel for trusted and unknown visits and withholds it from untrusted visits, subject to your rules and plan.
The control acts on your website’s browser Pixel. It does not cancel ad clicks, change Meta audiences or exclusions, or establish that the withheld visits were fraudulent. It does not, by itself, filter events sent through a separate Conversions API integration.
Establish a baseline
Start with Analytics only. Compare Meta-associated visits by campaign, source, landing page and available journey evidence. Retain the counts, period and collection limitations behind your decision.
An inferred checkout or thank-you page is not an independently verified sale. Review how your store records outcomes before treating URL activity as conversion quality.
Configure the Pixel
Do not assume an ecommerce app’s server events stop when its browser Pixel stops. Inventory those integrations separately.
- Open Configuration for the verified site and enter the Meta Pixel ID under Tracking scripts.
- Select Smart Bidding Training for the paths you intend to manage. Use path-specific IDs if that section reports to a different account.
- Find every existing Pixel installer: theme code, GTM, ecommerce apps and other plugins. Coordinate suppression of the original base-code loader on managed paths with Button-managed loading.
- Review the protection setting and save the configuration. Check publication history and verify the actual page behavior.
Keep event calls compatible
Page code must tolerate the Pixel being absent on visits where it is withheld. Review existing calls rather than pasting an additional Pixel base-code snippet into the page. A guard avoids calling an undefined function; it does not validate the event setup.
// Example guard around an existing event call.
if (window.fbq) {
window.fbq('track', 'ViewContent');
}Keep in mind: Keep your real event parameters and event deduplication design. Do not add a second Purchase event or loader while following this guide.
Verify the integration
- Inspect Network requests on each managed path and check Meta’s event diagnostics for the expected browser events.
- Confirm the Pixel is not also loaded independently by GTM, a theme or an app.
- Validate relevant consent states and classifications. A bot used for testing may correctly receive no Pixel.
- Monitor event coverage and legitimate visitor journeys after the change. Restore the previous setup if the integration behaves unexpectedly.