Server-side analytics (Meta CAPI)

Improve conversion tracking by enabling the Meta Conversions API — survives ad blockers and gives you a server-side mirror of every pixel event.

The Meta Conversions API (CAPI) is a server-side mirror of your browser pixel. Instead of relying entirely on the visitor's browser to fire a pixel event, Spotagig also sends the same conversion data directly from its servers to Meta — meaning the event reaches Meta even when an ad blocker, iOS privacy restriction or browser extension would have blocked the pixel.

  • Visitor converts
  • Browser pixel fires
  • Server also fires
  • Meta deduplicates

Meta deduplicates the browser hit and the server hit automatically using a shared event ID, so you never double-count — you just get better coverage.

Before you start Server-side analytics requires a Meta Pixel ID already saved in your analytics settings — the CAPI token is paired with it. If you haven't added your Pixel ID yet, see setting up analytics tracking first.

Getting a CAPI access token

The CAPI access token is a credential that authorizes Spotagig's server to send events to your Meta pixel on your behalf. You generate it in Meta's Events Manager.

  1. Open Events Manager Go to Meta Events Manager and select your pixel.
  2. Go to Settings Click the Settings tab for your pixel.
  3. Generate a token Scroll down to Conversions API and click Generate access token. Copy the token — it starts with EAA… and is quite long.
System user tokens last longer Tokens generated directly on a pixel expire periodically. For a longer-lived token, create a system user in Meta Business Manager, assign it Manage access to the pixel, and generate the token from the system user instead.

Adding the token to your profile

  1. Open Analytics settings Go to your profile's Settings page and expand the Analytics Tracking accordion.
  2. Find the Server-side section Below the pixel and GA4 fields you'll see a Server-side Conversions API section.
  3. Paste your token Click into Meta CAPI Access Token and paste the token you copied from Events Manager. The field is masked — your token is never displayed in plaintext and is stored encrypted.
  4. Save Click Save Analytics Settings. Server-side event delivery starts immediately for your tenant site.
Updating or removing the token To update the token, simply paste a new value and save — the old one is replaced. To remove it, contact our team; the field intentionally does not allow blanking (to prevent accidental deletion). Removing the token stops server-side delivery but leaves your browser pixel unaffected.

Testing with Meta Test Events

Before going live, you can route server-side events to Meta's Test Events tool so you can verify they arrive without affecting your real reporting.

  1. Get your test event code In Events Manager, go to Test Events. Your test code is shown at the top — it looks like TEST12345.
  2. Add it to your settings In the same Server-side Conversions API section, paste the code into Meta Test Event Code and save.
  3. Send a test event Use the Send a Test Event panel (just below the save button) to fire a Purchase, InitiateCheckout or other event. Tick Server-side (CAPI) and click Send Test Event. The event should appear in Meta Events Manager within about 30 seconds.
  4. Remove the code when done Clear the Meta Test Event Code field and save. Leaving a test code in place routes all real conversion events to the test dataset instead of live reporting, so always remove it before going live.

How deduplication works

Every conversion event on your tenant site fires twice: once from the visitor's browser (the Meta Pixel) and once from Spotagig's server (CAPI). Both hits carry the same event ID, which Meta uses to recognize them as the same occurrence and count it only once. You can verify this in Events Manager under Compare with browser events.

Tip The Client-side (Pixel) checkbox in the test panel fires fbq() from your browser, so you can verify the browser pixel is loaded separately from the server-side test.