Skip to main content
Server-side tracking sends shopping events from Eaglecart’s servers straight to the ad platform, alongside the pixel in the shopper’s browser. It helps platforms record events that browsers block.

Browser and server-side tracking

Keep the browser pixel on. It gives platforms details that only the browser has, such as on-site activity, and the two work together.

Supported platforms

Google Analytics, Google Tag Manager and Google Ads run in the browser only.

Before you start

Server-side tracking needs your own domain connected to your store. See Connect your existing domain.

Turn it on

  1. Create an access token in the platform’s events manager.
  2. In Eaglecart, go to Settings > Trackings and choose the region.
  3. On the pixel, open the menu (the three dots) and choose the setup option:
    • Set up CAPI for Meta.
    • Set up Events API for TikTok.
    • Set up Conversions API for Pinterest, Snapchat and ChatGPT Ads.
  4. In the window that opens, paste the access token. For Pinterest, also enter your Ad account ID.
  5. Switch on Turn on the Conversions API.
  6. Save.

Duplicate events

Every event gets one ID, created once and used by both the browser pixel and the server. The platform sees the matching pair and counts the event once. This is called deduplication. In Meta’s Test Events, matched pairs show as Deduplicated. It’s the same value in every case. Don’t also send the same events from another tool, such as a separate server-side setup or Google Tag Manager, because those won’t share the ID.

Test without affecting results

Use the platform’s test event code, test switch or validation mode while you check your setup, then turn it off. Test events left on can mix with your real campaign data.

Keep tokens safe

  • Treat an access token like a password. Don’t share it in screenshots or messages.
  • After you save a token, Eaglecart doesn’t show it again. To change it, paste a new one.
  • If you replace or delete a token, server-side events stop until a valid token is saved. The browser pixel keeps working.
Each platform’s server-side connection works differently, and how much data the platform accepts depends on your account. Check events are arriving in the platform after setup, instead of assuming every event is recorded.

Common questions

Purchases are counted twice. The same purchase is coming from two setups, for example this integration and a tag in Google Tag Manager. Remove one. Server-side events aren’t arriving. Check your custom domain is connected, the token is valid and hasn’t expired, and the connection is active in the right region.

Keep reading