Skip to main content
Meta’s Conversions API (CAPI) lets you share purchases, leads, and other conversion events from your server directly to Meta. Sherpo’s integration forwards checkout events so your ad campaigns stay accurate even when browser tracking is limited.

​
What the integration does

  • Sends purchase events (value, currency, product info) to Meta whenever a Sherpo checkout succeeds.
  • Includes hashed customer data (email, IP, user agent) to improve match quality.
  • Respects Meta’s deduplication rules so you can safely send both browser Pixel and server CAPI events.
  • Works across all Sherpo products-courses, files, memberships, coffee tips, calendar bookings, etc.

​
Prerequisites

  • A Meta Business Manager account.
  • A Pixel with Conversions API access.
  • A Meta access token & Pixel ID with the right permissions.

​
Connect Meta Conversions API

  1. In Meta Events Manager, navigate to your Pixel -> Settings -> Conversions API -> Generate access token (or use an existing system user token).
  2. Copy the Pixel ID and Access token.
  3. In Sherpo, go to Organization -> Integrations.
  4. Select Meta Conversions and click Configure.
  5. Paste the Pixel ID and Access token, then save.
Sherpo stores the credentials for your current site (space). If you manage multiple spaces, repeat the process for each one.

​
Verify events

  • Back in Meta Events Manager, open Test events and copy the Test Event Code.
  • In Sherpo’s Meta Conversions configuration, add the test code temporarily.
  • Trigger a test purchase (e.g., a low-dollar live order). Within a few minutes, you should see the event in Meta with source=Conversions API.
  • Remove the test code after confirming.

​
Managing privacy & data

  • Sherpo hashes customer data (SHA256) before sending.
  • If a buyer opts out of tracking on your site, Sherpo honors the preference by skipping non-essential events.
  • Keep your own privacy policy updated to mention server-side tracking where required.

​
Troubleshooting

  • No events showing: Confirm the token hasn’t expired and that you saved the Pixel ID correctly.
  • Duplicate events: Meta automatically deduplicates matching browser + server events when event_id aligns. Use the same Pixel for both if you run a front-end Pixel.
  • Event mismatch: Compare currency + value in Meta to Sherpo’s Sales -> Transactions data. If they differ, ensure you selected the right Pixel or currency in Meta.

​
Best practices

  • Rotate tokens periodically and store them securely (Meta recommends system user tokens that you can revoke if needed).
  • Use Meta’s Aggregated Event Measurement to prioritize Sherpo conversions if you run multiple domains.
  • Pair CAPI with Sherpo’s coupons/redirects so you can measure campaign performance end-to-end.
With Meta Conversions connected, Sherpo keeps your Facebook and Instagram ads optimized-even when browser cookies fail-by streaming reliable server-side conversion data directly to Meta.