Ecommerce Ad Tracking: Connect Landing Pages to Real Purchases

Ecommerce ad tracking connects an ad click to a confirmed merchant order—not just a landing-page visit or checkout button. Follow the path from ad to page, store, checkout, and purchase. Carry an explicit click reference into an authorized merchant system, then return verified order evidence. Tracked can host the page and receive configured conversion callbacks; it does not automatically capture your store's orders.

This guide is for Facebook, Instagram, and other paid advertisers who control the store or have authorized merchant access. Affiliates receiving commissions need a different evidence chain: see Facebook ads for affiliate marketing.

Trace the purchase across each handoff

A useful path is: ad → hosted presale or product page → store/checkout → confirmed order → conversion report → ad-platform feedback.

Each arrow needs an owner. The page owner controls the outbound link. The merchant controls checkout and order records. The event sender controls what reaches the tracker or Meta. Hosting the first page does not give that page access to the final order.

If you use a separate presale page, configure its outbound link to forward the required reference explicitly. In Tracked, that means configuring the appropriate routing and outbound macros—not assuming every incoming parameter follows the visitor.

The merchant's authorized implementation must receive and store the click reference, associate it with the eventual order, and return verified conversion evidence. Redirects, apps, checkout changes, consent settings, or a later visit can interrupt the chain. There is no universal promise that a reference survives checkout.

UTMs label the campaign; they are not an order join by themselves. Google's campaign URL guidance explains those labels. Our click IDs versus UTM parameters guide explains the separate attribution job.

Keep clicks, carts, checkouts, and orders separate

A busy funnel can hide a missing purchase signal. Record each stage under its own name so a page interaction cannot masquerade as revenue.

The following table is an illustrative evidence checklist, not customer results or a built-in Tracked ecommerce setup.

Stage	Evidence to keep	What it does not prove
Ad or landing-page visit	Source labels, time, and available click reference	The visitor reached checkout
Page-to-store click	Destination and forwarded reference	An item entered the cart
Add to cart	Authorized store event and item context	Checkout started or payment succeeded
Checkout started	Authorized checkout event	A confirmed order exists
Confirmed purchase	Merchant order ID, confirmation time, value, currency, and stored click reference	Meta attributed the sale to an ad
Tracker callback	Correct click association and recorded conversion fields	Browser/server events were deduplicated by Meta
Meta feedback	Delivery and processing diagnostics	Ads Manager credited that campaign

Choose what counts as a purchase before sending events. A pending payment, failed payment, or checkout visit should not become a confirmed paid order. If your business uses another confirmation rule, document it and apply it consistently.

Use stable identifiers and defined order value

Keep the merchant order ID stable across retries. Also assign a stable conversion event ID for each distinct event. An order identifier tells you which purchase occurred; an event identifier tells receiving systems whether the same event arrived again.

For browser and server copies of the same Meta purchase, Meta’s recommended deduplication approach uses the same event name and shared identifier: browser eventID, server event_id. Meta's deduplication guidance describes this pairing. Separate orders must not reuse that identifier.

Define value and currency at the merchant boundary. Decide whether value is before or after discounts and includes tax or shipping. Send the actual currency rather than treating every number as dollars. An affiliate payout is commission revenue, not the merchant's order total.

Keep a reconciliation record for refunds and cancellations. Your initial purchase event and retained sales revenue can differ later. Agree how corrections reach each report; do not assume a callback automatically reverses a purchase everywhere.

Give checkout events one clear owner

For Shopify stores, Shopify's Meta Pixel guidance describes setup through Facebook & Instagram by Meta and its data-sharing settings. Check for an old theme-installed Pixel before adding the channel setup to avoid duplicate tracking.

Shopify's pixel overview explains app and custom pixels, their sandbox, and customer-event access. Those pixels use permitted customer events, not arbitrary checkout DOM scraping. Privacy permissions govern loading and access; a server connection is not a consent bypass.

Meta's Conversions API provides server, platform, and CRM event delivery. That describes Meta's interface, not proof that your tracker has connected your merchant backend. Decide which authorized system owns purchase delivery and how it coordinates with the browser event.

Compare reports before changing the ad

A merchant order ledger, tracker report, and Ads Manager answer different questions. They can disagree without a broken checkout.

Before pausing a campaign, align:

• Time: date range, time zone, order time versus click time, and attribution window.
• Counting: unique orders, repeated events, and the exact purchase definition.
• Value: currency, gross versus retained sales, refunds, and cancellations.
• Coverage: which orders have a valid stored click reference and which remain unattributed.
• Spend: the source, reporting period, and freshness of the cost data.

Do not force every merchant order onto a paid click to make totals agree. Keep missing evidence visible. Revenue divided by spend gives ROAS, not profit after product costs, fulfillment, returns, and overhead. The campaign profit review guide covers comparable windows and cost definitions.

Meta API acceptance is not proof of Ads attribution. Meta's setup verification guidance separates received, deduplicated, processed, and matched events. Inspect those checkpoints before treating feedback as a campaign result.

Where Tracked is today

Status: Partial for ecommerce purchase tracking. Tracked supports HTML/ZIP landing-page import and hosting, configured routing and macros, offer-click records, and inbound conversion callbacks when properly configured.

Connecting those clicks to merchant orders requires an authorized merchant/backend implementation that stores the reference and returns verified evidence. This is not a built-in ecommerce setup. No native Shopify connector, automatic order or webhook ingestion, checkout Pixel installation, or complete ecommerce attribution workflow has been established.

Meta account connection and on-demand reporting are available, not automatic campaign discovery or scheduled sync. Manual sending of supplied CAPI events exists; automatic wiring from merchant orders or Tracked conversions to Meta has not been established. A received callback does not imply automatic Meta delivery.

Use the integration and postback guide to separate these connections. For event-delivery details, see the Meta CAPI guide; its affiliate examples do not grant checkout access.

Frequently asked questions

Can I track Shopify purchases by hosting a page in Tracked?

Not automatically. Hosting covers the landing page. Purchase tracking needs authorized Shopify or merchant-side evidence and a working reference handoff. Shopify's Meta channel setup is separate from connecting an order to a Tracked click.

Should an add-to-cart event count as a conversion?

It can be a named funnel conversion, but not a purchase. Keep cart, checkout, and confirmed-order events separate. Otherwise, a campaign with many carts can look like one with paid sales.

Why does Meta show fewer purchases than my store?

Check attribution windows, consent, matching, duplicates, and event processing. The store counts orders; Meta credits eligible events under its reporting rules. A successful API response alone does not explain the difference.

What should I check before sending paid traffic?

Confirm the destination, explicit reference forwarding, authorized order evidence, duplicate handling, and reporting definitions. Use the Facebook ads landing-page checklist for the page preflight. Resolve the merchant handoff before treating outbound clicks as purchase measurement.

Start with the page, then connect the order evidence

Use Tracked for the hosted landing-page and campaign-click side of your workflow. Plan the authorized merchant connection separately before relying on purchase reports.

Start free — early access. Use your invite or request access to start with the hosted-page side. Connect merchant order evidence separately; purchase capture is not automatic.