Are you using custom landing pages like Funnelish or Checkout Champ? Your Meta tracking pixel may be cooked.

Why do people use a custom landing page?

A lot of people build advertorials as a landing page using softwares like Funnelish or Checkout Champ. If you don’t know what advertorials is, it basically looks like an educational editorial or news article but is actually an ad. It increases conversion rate by a lot because people tend to trust third-party recommendations more. It’s like a hack.

Tracking/pixel mistakes that cost money

We have worked with close to a hundred of brands with customized landing pages. One of the popular setups I have seen is having Funnelish or Checkout Champ as landing pages and Shopify as the backend for fulfillment.

Here are a few big tracking/pixel mistakes I have seen that cost people $$$:

1. Different domain for the landing page

Why It Bleeds Cash

Meta treats yourbrand.com and shopyourbrand.com as two strangers at a party. There’s no shared cookies.

Quick Fix

Host the advertorial on a sub‑folder/sub‑domain you can domain‑verify or use CAPI to stitch sessions.

2. Redirect nukes fbc / gclid

Why It Bleeds Cash

Those clickID parameters (fbc for Facebook and gclid for Google) tie the purchase back to the ads click. Lose them and you’re invisible to the algorithm.

Quick Fix

Forward them in the URL (?fbp=…&fbc=…) or capture them in hidden inputs and forward via CAPI.

3. Double‑firing (or missing) events

Why It Bleeds Cash

Turning on “Pixel” in both Funnelish and Shopify sometimes cause duplicates conversion tracking.

Quick Fix

Decide one source per event, especially for purchase. Use consistent event_ids so Meta can dedupe.

4. Pixel‑only in a post‑cookie world

Why It Bleeds Cash

Safari/Firefox already block browser cookies. Pixel alone ≈ 30‑40 % conversion loss.

Quick Fix

Always set up CAPI or server‑side GTM; hash emails/phones, send event_source_url.

TL;DR for the attention‑challenged

• One domain.
• Keep fbp/fbc forwarded through every redirect because your ROAS depends on it.
• Fire each event once with matching event_id.
• Move server‑side ASAP.

Fix these, and your Meta pixel goes from “money pit” to “printing press.”

Need a sanity check or a done‑for‑you setup? Aimerce can help. Happy to help you check your current setup.