Advanced Page Settings: Pixel, Parameters, and Back Redirect
Set up the Pixel, pass UTMs to your checkout, add an exit back redirect, page protection, and share data before you publish.
Where the settings that decide if your page tracks actually live
Before you hit publish, there's an advanced settings panel most people skip. Mistake. That's where you install the Facebook Pixel, set up UTM passing to the checkout, turn on the back redirect, and define the image that shows when someone shares the link. Skip this part and the page goes live with no tracking, no exit retention, and none of the data Meta uses to optimize. The sale happens but the pixel sees nothing.
I'll walk through what matters in each field, in the order that makes sense for someone who runs real traffic.
Pixel and external code: the base of tracking
The first field is the Facebook Pixel. Paste the ID there and the page starts firing the standard events (PageView, ViewContent, and the rest depending on the flow). Without it, you're advertising blind: Meta gets no conversion signal, the algorithm doesn't learn, and your CPA inflates because optimization is working with incomplete data.
The same panel accepts other external code. Third-party scripts, extra tracking tags, whatever you use in your measurement stack. It all fits in the head or at the end of the body, depending on what the code needs.
One thing that trips a lot of people up: the pixel on the page is only half of it. If your checkout is on another domain, the purchase event fires there, not here. That's why the parameter passing coming up next matters so much.
How to pass UTM, src, and sck to the checkout automatically
Here's the field that fixes the attribution hole. You turn on automatic parameter passing and the page grabs the UTMs, src, and sck from the URL, then hands it all to the checkout link on click.
Here's how it works: the lead lands via the URL with ?utm_source=fb&utm_campaign=xyz&src=adset1. The page stores those values and, when they click the buy button, they travel along to the checkout. Result: the sale that closes down the line carries the right source. You know which campaign, which ad set, and which creative brought the money.
Without this passing, every sale drops into your checkout report as "direct" or "no source." Then you don't know what to scale or what to kill. Your ROAS per creative becomes a guess.
Anyone running volume knows: broken tracking is wasted budget. You pay for the click but can't tie the click to the sale.
Back redirect: recover people trying to leave
The back redirect is the field that works the moment someone bails. When the user hits the browser back button to leave the page, instead of letting them go, you send them to another page.
The classic use is a rescue offer. The guy was leaving without buying? Send him to a version with a discount, an extra bonus, a cheaper downsell. It's the last shot before you lose the lead you already paid to bring in.
It's not magic and it won't convert everyone. But in paid traffic, where every lead has a cost, recovering a fraction of the people who'd leave already pays for the setup. Test the offer on your rescue page. Sometimes a lower price on the second screen turns abandonment into revenue.
Page protection and hiding from search engines
Two shielding settings sit in the same panel.
Page protection disables right-click and blocks inspect element. It's not real security (anyone who wants to copy will find another way), but it makes life harder for the casual spy trying to clone your structure in a hurry.
Hiding from search engines keeps the page off Google. You use this when the offer is paid traffic only and you don't want it indexed and found by anyone searching. Test offers, specific campaign pages, structures you don't want to expose for competitors to sweep.
Speaking of competitors sweeping: protecting the page is one layer, but heavy spying lives in the Meta Ad Library, where anyone can see your active creatives. People running lots of accounts usually handle the cloaking side with DirectAds to spread few ads per FanPage and make sweeping harder, because hiding the page doesn't help if the creative is exposed in the library.
Terms, privacy, and share data
Meta rejects ads for pages without terms and a privacy policy. It's a requirement, not decoration. The panel generates both pages automatically, in three languages: Portuguese, English, and Spanish. If you advertise abroad, it comes out ready in the audience's language.
Then comes the share and page SEO block:
- Share image: this is the image WhatsApp pulls when you send the link, and the one Facebook shows when the link appears in the feed. Meta likes this field filled in, especially if you're going to advertise there. A link with no broken preview reads as more trustworthy.
- Favicon: the little icon in the browser tab on desktop. A small detail that signals a page that's cared for.
- Title, description, and product name: fill all three. Title and description also send signals to Meta and to sharing.
Set all of this, click the green button, and publish. You get the live page link, ready to paste into your ad.
Why hosting speed decides the sale
A correct pixel, UTMs passing, and back redirect on mean nothing if the page is slow to open. A slow page loses traffic. You pay for the click, send the lead to the page, and it hangs loading. The guy won't wait. He leaves. Sale lost before he sees the offer.
In international operations the problem hits harder. If you advertise worldwide, the page has to load fast in any country, not just where the server sits nearby. Optimized hosting infrastructure solves this: fast loading regardless of geography, so you can scale abroad without bleeding conversions to latency.
The math is simple: each extra second of load drops a slice of your leads. Multiply that by your cost per lead and you see how much bad hosting costs you per day.
Takeaways
- Paste the Pixel and turn on automatic UTM, src, and sck passing before you publish, or your checkout sales come in with no source and you scale in the dark.
- Set up the back redirect with a cheaper rescue offer to recover part of the people trying to leave.
- Generate terms and privacy (in your audience's languages) and fill in share image, favicon, title, and description: Meta demands it.
- Publish on hosting optimized for global speed. A slow page burns budget before the lead sees the offer.
FAQ
Is the Pixel on the page enough to track the purchase?
No. PageView and ViewContent fire on the page, but the purchase event happens at the checkout. If the checkout is on another domain, you need parameter passing to tie the click's source to the sale that closes there.
Does the back redirect hurt user experience?
It can annoy people if the rescue offer is too aggressive. The ideal is to use it as a real second chance: a discount or bonus that makes sense for someone about to leave without buying. Test the rescue page's conversion before leaving it running.
Does hiding the page from search engines hurt paid traffic?
No. Hiding only affects organic indexing on Google. Paid traffic keeps coming in normally through the ad link, because it doesn't depend on search.
