Tracking pixels

Attach a Meta Pixel and Google Analytics 4 ID to track conversions on your event pages.

Attach your own Meta Pixel and Google Analytics 4 (GA4) measurement ID to your host so conversions on your event pages flow into your own ad and analytics accounts. Use this to measure ad campaigns in Meta Ads Manager, Google Ads, or any tool that reads from GA4.

Tracking pixels are part of Eventship Pro.

What gets tracked

Three funnel events fire from your event pages to whichever pixel(s) you've configured:

StepMeta Pixel eventGA4 event
Someone views your event pagePageViewpage_view (auto)
Someone completes a free RSVP or hub subscribeCompleteRegistrationsign_up
Someone completes a paid checkoutPurchasepurchase

Each event includes the event ID and event title so you can build conversions by event. For paid checkouts we also send the order value, currency, and transaction ID, so Meta and Google can calculate ROAS for your ad campaigns.

Where to find the IDs

Meta Pixel ID — In Meta Events Manager, open the Data Sources panel and pick your pixel. The 15–16 digit number at the top is your Pixel ID. If you don't have one yet, create a new pixel from that same screen.

Make sure eventship.com is allowed under your pixel's Traffic Permissions. Without it, Meta drops events from our domain.

Google Measurement ID — In Google Analytics, open Admin → Data Streams, pick your web stream, and copy the Measurement ID (it looks like G-XXXXXXXXXX). This is a GA4 ID, not a Universal Analytics tracking ID and not a Google Tag Manager container ID.

Connect your pixels

  1. Go to your host dashboard → Settings
  2. Scroll to the Tracking pixels card
  3. Paste your Meta Pixel ID and/or your Google Measurement ID
  4. Each field auto-saves a moment after you stop typing. A green check confirms the save.

You can fill in one, the other, or both. To remove a pixel, clear the field — Eventship saves the empty value and stops firing events to it.

Scope

Pixels are configured at the host level and apply to every event on that host. There's no per-event override. If you run multiple hosts, each one connects its own pixels separately — they can point to the same ad account or to different ones.

Verify it's working

Meta — Install the Meta Pixel Helper Chrome extension. Open one of your event pages — the helper should show your Pixel ID firing PageView. Complete a test registration to confirm CompleteRegistration (free) or Purchase (paid).

Google — In Google Analytics, open the Realtime report and load one of your event pages. You should appear as an active user. Trigger a registration and you'll see the sign_up or purchase event in the realtime event stream within 30 seconds or so.

If neither shows up, double-check that the ID matches exactly, that the field saved (green check), and — for Meta — that eventship.com is in the pixel's allowed-domains list.

Privacy and consent

Eventship doesn't show a cookie banner before firing your pixel. If you operate in the EU, UK, or other jurisdictions that require explicit consent before loading third-party tracking, you're responsible for ensuring you have a lawful basis to process visitor data through your own pixel — same as you would on any landing page you control. Both Meta and Google have their own consent-mode tooling you can configure on the ad-account side.

We never send personally identifying information (email, name, phone) to Meta or Google. Only the event ID, event title, and — for paid checkouts — the purchase amount, currency, and transaction ID.

Troubleshooting

The Tracking pixels card is greyed out. The card is Pro-only. Upgrade under Account → Plan. Existing values aren't lost when Pro lapses, but new edits are blocked until Pro is active again.

My Pixel ID is rejected with a format error. Meta Pixel IDs are pure digits — no dashes, spaces, or pix_ prefix. Copy the number directly from Events Manager.

My Measurement ID is rejected. Make sure you're copying the GA4 Measurement ID (G-XXXXXXXXXX), not the older Universal Analytics tracking ID (UA-XXXXXXX-X) or a Google Tag Manager container ID (GTM-XXXXXXX). Universal Analytics was sunset by Google in 2024.

Meta Pixel Helper says "Pixel ID disabled" or "Domain not in allow-list". Open the pixel's settings in Meta Events Manager and add eventship.com to Traffic Permissions. Without that, Meta silently drops events from our domain even though the pixel fires.

`PageView` shows up but `CompleteRegistration` / `Purchase` doesn't. The funnel events only fire on a successful registration or paid checkout. Pending approval, declined cards, or abandoned checkouts don't count. Run a real test registration end-to-end (you can refund yourself afterwards for paid events) to confirm.

I see double `PageView` events on Eventship's platform pixel. You shouldn't — host events are scoped via trackSingle so they only fire to your pixel. If you're seeing duplicates in Eventship's own analytics, that's a bug; please email support.

Google Tag Manager. Eventship doesn't support GTM container IDs directly. If you need GTM, point GTM at the GA4 stream that's already wired up via your Measurement ID, or contact support to discuss your use case.

Other ad platforms (TikTok, LinkedIn, X/Twitter, Snap). Not currently supported. If you need one of these, email [email protected] — demand drives the roadmap.

Questions?

Email [email protected]. We can help you confirm events are flowing through and set up custom conversions in Meta or GA4.

Was this article helpful?

Let us know if this article answered your question.