Quick answer
You connect Meta Pixel to your WanderOS site from app.wander.com → Website → Integrations. Find the Meta Pixel field, click Connect, paste your numeric Meta Pixel ID, and click Connect again. WanderOS automatically injects the pixel on every page, so no developer is required. This applies to all WanderOS hosts and property managers. The pixel is live immediately. The Meta Pixel Helper Chrome extension confirms it within seconds, while audiences and standard reports in Meta Events Manager take a few hours to start populating and a few days to become useful.
Before you start
Have the following ready before you begin.
A Meta business account with a Pixel created in Meta Events Manager. If you do not have one, create it before connecting.
Your Meta Pixel ID, which is a numeric string from Meta Events Manager.
How do I find my Meta Pixel ID?
You find your Pixel ID inside Meta Events Manager.
Open Meta Events Manager at
business.facebook.com/events_manager.In the left sidebar under Data Sources, select your Pixel.
The Pixel ID appears directly below the Pixel name. It is a long numeric string, for example
123456789012345.
Tip: If your business has multiple Pixels, pick the one you want to use for your direct-booking site. Mixing Pixels makes retargeting audiences unreliable.
How do I connect Meta Pixel to WanderOS?
You connect the Pixel in three steps from the WanderOS Integrations page.
Log in to
app.wander.com.In the left sidebar, click Website → Integrations.
Find the Meta Pixel field. Click Connect, paste your numeric Pixel ID, and click Connect again.
The pixel script is injected across every page of your site immediately on save. No code or developer work is required.
How do I confirm the Pixel is firing?
You confirm the Pixel is firing using the free Meta Pixel Helper Chrome extension, available in the Chrome Web Store.
Install the Meta Pixel Helper extension in Google Chrome.
Open your live WanderOS site in a new browser tab.
Click the Meta Pixel Helper icon in your browser toolbar.
You should see your Pixel ID listed with a green checkmark and at least one PageView event.
You can also verify in Meta Events Manager under Test Events, but the helper extension is faster.
Note: The Pixel Helper and the Test Events tab confirm the Pixel is firing in real time. Custom Audiences and standard Events Manager reports take a few hours to start populating, and several days of traffic before they are large enough to use for ads.
How do I update or disconnect Meta Pixel later?
You can return to Website → Integrations at any time to update your Pixel ID or disconnect the Meta Pixel from your site. Changes take effect immediately.
Important: Disconnecting the Pixel in WanderOS only stops it from firing on your site. It does not delete historical event data, audiences, or reports inside Meta Events Manager. Existing audiences stop receiving new events from the WanderOS site.
Best practices
Apply these once your Pixel is live.
Connect early. Retargeting audiences in Meta Ads Manager grow based on cumulative visitor data. The earlier the Pixel runs, the larger your audiences when you start running ads.
Use one Pixel per site. Splitting traffic across multiple Pixels fragments your audiences and reduces ad performance.
Verify after every domain change. If you connect, change, or remove a custom domain, re-check the Meta Pixel Helper to confirm the Pixel still fires on the new URL.
Store your Pixel ID in a safe place. Keep it in your operations doc so you can reconnect quickly if you ever rebuild or migrate your site.
Troubleshooting
If something does not behave as expected, check the most common causes below.
The Pixel ID is rejected on save: Confirm the ID is the numeric string from Meta Events Manager and contains no spaces, letters, or extra characters.
Pixel Helper says the Pixel is not detected: Open your site in an incognito window with ad blockers disabled and reload. Most ad blockers and privacy extensions block the Meta Pixel by default.
Pixel Helper shows the Pixel but Events Manager reports are empty: Allow a few hours for events to roll up into Events Manager standard reports, and several days of real traffic before audiences are large enough to use.
I see duplicate PageView events: You likely have the Pixel connected through both WanderOS and a previous CMS, or have it injected somewhere else such as a custom HTML section. Remove the duplicate source.