Meta landing pages
Facebook Ads Landing Page Checklist: Before You Spend
A pre-spend checklist for affiliate buyers and ecommerce advertisers: verify the page, outgoing campaign context, event ownership, and downstream sale or order evidence.
Before spending on Facebook or Instagram ads, check that your landing page matches the ad, works on mobile, and sends visitors to the intended offer or store. Then verify the outgoing tracking values and the evidence needed to identify a real conversion. A working button is not purchase tracking. This checklist helps you find broken handoffs before buying traffic; it does not guarantee ad approval or campaign results.
Match the ad to an offer you can substantiate
Read the ad and destination together. The product, price, audience, and main promise should agree. If the ad advertises a bundle, the page should explain that bundle—not quietly substitute another offer.
Check that discounts are current, availability claims are accurate, and testimonials have permission and support. Make shipping costs, recurring charges, eligibility, and material limitations clear before the visitor commits. Affiliates should confirm the network permits the offer and traffic source, and include required disclosures.
Do not hide unsupported claims behind a redirect or show reviewers a different destination. Treat message match as a buyer check, not a way to bypass review. For the wider affiliate campaign workflow, use Facebook ads for affiliate marketing.
Use the page as a mobile visitor would
Open the actual campaign destination, not only an editor preview. Check it at a narrow screen width and on a phone. If your ads reach people inside Facebook or Instagram, include their in-app browser in your own checks where available.
These are usability checks, not claims that those browsers universally block a particular feature:
- Can you read the headline, price, and disclosures without zooming?
- Does a sticky button cover content, consent controls, or form fields?
- Can you tap the CTA, enter form data, and recover from an error?
- Do menus, videos, and external links behave as intended?
- Can you complete the store handoff or checkout without an unexpected login loop?
Review your consent flow too. Do not assume a pixel behaves the same in every environment. Shopify's pixel overview describes sandbox and consent considerations for Shopify pixels; it does not establish a Tracked integration.
Check assets, buttons, and the HTTPS link chain
Confirm images, fonts, styles, and scripts load on the published page. Look for placeholder copy, missing images, broken forms, and buttons left pointing at a draft URL. Check repeated CTAs, comparison-table links, and mobile-only buttons separately.
Follow the full chain: ad destination → landing page → tracked outbound action → network or store. Verify HTTPS at each destination and inspect the final URL after redirects. A valid certificate on the first page does not prove the remaining path works.
If you host an owned HTML or ZIP page in Tracked, the landing-page hosting guide covers packaging and domain setup. Keep this preflight focused on the published destination, not another hosting tutorial.
Map the values you need at the outbound handoff
A parameter can reach your landing page and disappear at the next redirect. Write down which values need forwarding, where they belong, and who receives them.
| Value | Job | Handoff check |
|---|---|---|
Real incoming fbclid | Meta click context | Keep the supplied value unchanged; inspect its configured destination field. |
| Tracked offer-click ID | Join a callback to the outbound offer click | Map {{click.id}} to the network's agreed external-click field. |
| UTM labels | Describe source, medium, and campaign | Forward only the labels needed by the receiving system. |
| Event or order ID | Identify a particular action or transaction | Define it with the system that owns that event or order. |
If the destination accepts these query fields, an outgoing URL might use fbclid={{query.fbclid}} and utm_campaign={{query.utm_campaign}}. Map each required field explicitly. Tracked does not promise automatic preservation of every incoming parameter. Use the destination's actual field names and inspect the resolved URL after redirects. Check that missing values do not leave unresolved tokens.
Meta's fbp and fbc guidance treats a real fbclid as case-sensitive. Do not lowercase it or replace it with a Tracked ID. UTM labels are different: establish a consistent naming convention, as described in Google Analytics campaign URL guidance.
Define the conversion and name its owner
Write the event definition before launch: “Outbound offer click,” “network-confirmed sale,” or “paid store order,” for example. Name the system and person responsible for supplying its evidence.
Affiliate handoff: you usually control the prelander, not the merchant's checkout. The network must store the Tracked offer-click ID and return it in a configured callback for a confirmed sale. Verify the returned event status and payout meaning; affiliate commission is not the merchant's order total.
Merchant handoff: sending a visitor from a hosted page to your store does not capture the order automatically. Purchase evidence needs an authorized checkout or order integration, with a defined status, order identifier, value, and currency. The ecommerce ad tracking guide explains that boundary.
Meta feedback is another delivery path. Meta Pixel covers website event code; Conversions API covers separate server or platform event delivery. Neither makes an outbound button click a purchase.
Keep a launch evidence record
Fill in this record with your own observations. A blank row is an unresolved dependency, not a pass.
| Check | Evidence to save | Owner / result |
|---|---|---|
| Ad and offer agree | Creative, headline, price, and terms reviewed together | ___ |
| Mobile destination works | Device/browser, page version, form and CTA outcome | ___ |
| Published assets load | Campaign URL and any repaired asset paths | ___ |
| HTTPS chain reaches the right offer | Final destination after redirects | ___ |
| Required parameters arrive | Resolved fields at the receiving handoff | ___ |
| Conversion joins correctly | Authorized test callback or order evidence tied to the intended click | ___ |
| Event delivery is understood | Event name, receiving system, consent handling, and responsible owner | ___ |
Before buying traffic for a sales-measurement test, gather evidence for the page, handoff, and downstream conversion path. A synthetic callback checks the connection; it does not prove the network will send real approved sales. Record which evidence came from an authorized end-to-end test and which parts remain unverified.
Where Tracked is today
Status: Meta conversion feedback and ecommerce purchase capture are partial. Tracked can host HTML/ZIP landing pages, route offer clicks, and record configured conversion callbacks. You still need explicit outbound mappings and a verified callback source or authorized store integration.
Meta OAuth and on-demand reports are available. Manual CAPI testing or sending a supplied payload is not a complete automatic Tracked-to-Meta conversion workflow. Do not launch on the assumption that hosted pages automatically capture store purchases or send every recorded conversion to Meta.
Make the next test controlled
Once the path works, choose one page hypothesis and a downstream outcome. Keep the offer and measurement path stable, record the test window, and allow for conversion delays. Use the landing-page split-testing guide for the detailed setup. User-configured traffic weights are not automatic winner selection.
Frequently asked questions
Does this checklist guarantee Facebook ad approval?
No. It checks destination readiness and measurement dependencies. Ad approval remains a separate platform decision; a technically working page does not establish policy compliance.
Should I count the landing-page CTA as a purchase?
No. It is an outbound action. Use network-confirmed sale evidence for affiliates or authorized checkout/order evidence for merchants before recording a purchase.
Do UTMs replace fbclid or the Tracked click ID?
No. UTMs label campaigns, fbclid carries Meta click context, and the Tracked offer-click ID joins the network callback. Keep their fields and purposes separate.
What if I cannot verify the sale path yet?
Do not describe the campaign as purchase-tracked. Resolve the callback or order-integration dependency before a sales test. If you run a click-only diagnostic, label it that way and do not infer sales performance from it.
Start free — early access. Use your invite or request access, then prepare one landing-page route. Verify your downstream measurement setup before spending.