logo
    Back to all articles
    For Organisers

    Does TicketsMinistry support Meta Conversions API and server-side tracking?

    3 min read·4 steps

    Yes. Alongside the standard browser pixel (Meta Pixel, TikTok Pixel, GA4), TicketsMinistry fires a matching server-side Purchase event through each platform's Conversions API / Events API for every completed booking. Running both together is the setup ad platforms recommend: the server-side event still reaches Meta, TikTok, or Google even if the browser event is blocked.

    1

    Why server-side tracking matters

    Browser-only pixels lose a meaningful share of purchase events to ad blockers, Safari's Intelligent Tracking Prevention, and iOS 14.5+ App Tracking Transparency opt-outs. A server-side event is sent directly from TicketsMinistry's backend to the ad platform, bypassing the browser entirely, so none of these blocks affect it.

    2

    Browser and server events are deduplicated automatically

    Every booking gets a single order ID. That same ID is sent as Meta's eventID, TikTok's event_id, and GA4's transaction_id on both the browser Purchase event and the backend's server-side event. Meta, TikTok, and Google Ads use this shared ID to recognise the two events as one purchase, so your reported conversions aren't inflated by double-counting.

    3

    Which platforms are covered

    Server-side Purchase events are sent for Meta (as "Purchase"), TikTok (as "CompletePayment"), and Google Analytics 4 (as "purchase"), matching the event names each platform's Conversions or Events API expects.

    4

    What you need to do

    Nothing beyond adding your Pixel ID (see How to add a Tracking Pixel or Tag to your event page). Server-side dispatch and deduplication are handled automatically for every event with a pixel configured, there's no separate Conversions API setup or access token for you to manage.

    Tip

    If your ad platform's reported purchases look lower than your actual sales, check that your Pixel ID is correctly saved in Event Settings first. That's the most common cause, not a deduplication issue.

    Note

    For the browser-side pixel setup this pairs with, see How to add a Tracking Pixel or Tag to your event page.

    Still need help?

    Our team typically responds within 2 hours on WhatsApp during business hours (Mon–Sat, 9am–7pm).