How to configure Meta Pixel + Google Analytics 4
LimãoPay has serverside Conversions API ready — no JS in the browser, no ad blockers. 1. Go to Settings → Integrations 2. Meta Pixel: paste Pixel ID + Access To…
Quick answer
LimãoPay has server-side Conversions API ready — no JS in the browser, no ad blockers.
- Go to Settings → Integrations
- Meta Pixel: paste Pixel ID + Access Token (generated in business.facebook.com)
- GA4: paste Measurement ID + API Secret (generated in analytics.google.com → Admin → Data Streams → Measurement Protocol)
- Save → events fire from the server automatically
Events that fire
| Event | When |
|---|---|
PageView | Visitor lands on the page |
ViewContent | Visitor sees the product |
InitiateCheckout | Clicks "Buy" |
AddPaymentInfo | Fills payment data |
Purchase | Payment confirmed |
Why server-side is better
- Not blocked by iOS 14.5+ ATT, Brave, ad blockers
- More reliable than client-side pixel (up to 30% of conversions vanish in JS pixel)
- Accurate attribution — Facebook/Google know which ad converted
Where to find your credentials
Meta
- Pixel ID: business.facebook.com → Events → Settings → Pixel ID
- Access Token: business.facebook.com → System Users → "Generate Token" with
ads_managementpermission
GA4
- Measurement ID: analytics.google.com → Admin → Data Streams → your site → starts with
G- - API Secret: same screen, scroll to "Measurement Protocol API Secrets" → Create
Common errors
- "Events don't show in Meta" → Wait 5-10min (normal delay). If still nothing, validate the Access Token.
- "GA4 Auth error" → API Secret is wrong or expired. Regenerate.
- "Duplicate purchase in funnel" → Seller also configured the old JS pixel. Remove the JS, keep only server-side.
Expected result
Within 24h, you see events arriving in both platforms. You can run campaigns optimized for Purchase directly, no data loss.