If your Meta pixel currently runs through Google Tag Manager (GTM), you can switch to HomeRunner’s native Meta Pixel integration. The switch involves two changes, and both should happen within the same hour to keep the overlap window short.
What the native integration tracks. The native integration fires Purchase with value and currency, plus ViewContent and InitiateCheckout, automatically.
Why timing matters. If a GTM Purchase tag stays active after HomeRunner starts firing Purchase natively, every booking is reported twice in Meta Events Manager.
Step 1: Send your pixel ID to HomeRunner. Confirm the pixel ID your ad account reports on in Meta Events Manager and send it to HomeRunner. HomeRunner sets it in the native integration and removes the header snippet in the same pass.
Step 2: Pause the Meta tags in GTM. Pause every Meta tag that fires on that pixel, not just the base-code tag. This includes the Custom HTML tag that loads the pixel (PageView), the Purchase tag, and any Lead tag.
- Open each Meta tag in GTM.
- Use the pause control in the tag editor.
- Submit and Publish the container.
If coordinating the timing is difficult. You can grant HomeRunner Publish access to your GTM container so both changes happen in one pass, with no window to manage.
Checking the result. After the cutover, Meta Events Manager should show one PageView per page load, and your next completed booking appears as a Purchase event with the booking amount attached.