What the Meta Pixel does on RealScout
When a Pixel is added to your RealScout portal, the Pixel can record website events when a client loads your portal pages (for example, a Search Link landing page or if you've installed your search widget on your website and a user clicks through).
This is primarily used to track visits and actions on your RealScout pages, build audiences, and optimize ads inside your Meta/Facebook Events Manager.
What it typically tracks (examples)
Meta Pixel events can include:
PageView when a RealScout page loads.
The page URL and referrer URL used for reporting and rule-based conversions in Events Manager.
Basic browser/device signals used by Meta for measurement.
What the Pixel does NOT do
Does not access a visitor’s phone contents (photos, texts, contacts, apps).
Does not “scrape” the page or read it. Listing views and listing photos are not readable by Meta; this is just reporting visitor click activity.
The Pixel records events and URLs. Any additional details would only be sent if a site explicitly passes them as event parameters.
How to set it up in RealScout (Start in Meta/Facebook first)
In Meta Events Manager, create or select a Pixel.
Copy the Pixel ID.
In RealScout, add that Pixel ID to your RealScout portal integration settings.
How to test and verify it is working
Method 1: Meta Events Manager “Test Events”
Use Events Manager to confirm Meta is receiving events from your portal in real time.
Method 2: Meta Pixel Helper (recommended by Meta/Facebook)
Meta Pixel Helper is Meta’s official Chrome extension to confirm a Pixel is present and which events are firing.
Steps:
Install Meta Pixel Helper (Chrome).
Open your RealScout portal page (for example your Search Link landing page).
Click the extension to view:
Pixel ID detected
Events firing (often
PageView, which is indicating a page was viewed by your visitor)Any auto-detected events (example:
SubscribedButtonClick, which is a click on the site.On RealScout this does not mean your viewer subscribed with you/saved a listing; just that they clicked somewhere on your RealScout page.
Warnings or errors
Common issues to help troubleshoot
No events detected
Pixel ID not added correctly in RealScout.
Ad blockers or browser privacy settings blocking the script.
Testing in an in-app browser vs a standard browser can change results.
Only Page View shows
That can be expected. RealScout’s integration is designed to support Pixel placement on the portal.
additional event strategy (custom events, advanced setup) is typically configured on the Meta side.
Auto-detected events appear
Meta may automatically detect certain interactions and label them as automatic events, such as clicks
FAQs
Does RealScout send server-side events via Conversions API?
No, RealScout’s integration option is for adding a Pixel ID to your RealScout portal, which is a browser Pixel implementation.
Can I track traffic sources with UTMs in RealScout?
At this time, RealScout does not support UTMs for links shared outside of RealScout.
For campaign attribution and optimization, when you make a Facebook/Meta ad, this is done through their ad manager tools.
Where do I see the results?
In Meta:
Events Manager for event activity and diagnostics
Ads Manager for campaign reporting