Meta Ads Integration (CAPI)

    Send server-side purchase events back to Meta to optimize your Facebook & Instagram ad campaigns — bypassing iOS 14+ and ad-blocker limitations.

    What it does

    When a customer clicks one of your Facebook or Instagram ads, the URL contains an fbclid parameter. MenuLogic automatically captures this click ID and, when the customer completes a purchase, sends a server-side Purchase event back to Meta via the Conversions API (CAPI). This tells Meta's algorithm exactly which ad clicks led to real revenue, improving targeting and lowering your cost per acquisition.

    How it works

    1. Click capture

      When a visitor lands on your menu from a Meta ad, MenuLogic extracts the fbclid from the URL and stores it alongside the browsing session.

    2. Customer orders

      The customer browses the menu, adds items to cart, and completes checkout as normal.

    3. Payment confirmed

      After Stripe confirms the payment, a server-side function fires automatically.

    4. Purchase event sent to Meta

      The function sends a Purchase event to Meta's Conversions API with the order value, currency, and the original click ID — all from the server, not the browser.

    Setup

    1. Navigate to Restaurant Setup → Integrations in the admin sidebar.
    2. Find the Meta Ads Integration card.
    3. Enter your Meta Pixel ID — a 15-digit number found in your Meta Events Manager under Data Sources.
    4. Enter your Conversions API Access Token — generate this in Events Manager → Settings → Conversions API → Generate Access Token.
    5. Toggle the integration on.
    Screenshot: Meta Ads Integration settings showing Pixel ID, Access Token, and enable toggle

    Data sent to Meta

    FieldDetails
    Event namePurchase
    Value & currencyOrder total in CAD
    fbc (click ID)The original fbclid from the ad click, formatted as fb.1.timestamp.fbclid
    Hashed emailSHA-256 hash of the customer's email for advanced matching
    Hashed phoneSHA-256 hash of the customer's phone number for advanced matching

    Privacy & security

    • All customer data (email, phone) is SHA-256 hashed before being sent to Meta — raw PII never leaves the server.
    • Events are sent server-side only, bypassing browser-based tracking limitations (iOS 14+, ad blockers).
    • Your Conversions API access token is stored securely and only accessed by server-side functions — it is never exposed to the browser.
    • The integration can be disabled at any time via the toggle in Integrations settings.
    Tip: For best results, use Meta CAPI alongside the Meta Pixel (browser-side). CAPI fills in the gaps that ad blockers create, while the Pixel handles standard page-view and add-to-cart events. Together they give Meta the most complete picture of your ad performance.