Home / Blog / Meta CAPI Gateway vs Elevar: Which Should Send Shopify Purchase Events?
Shopify · Tracking Troubleshooting
Meta CAPI Gateway vs Elevar: Which Should Send Shopify Purchase Events?
Meta CAPI Gateway and Elevar can both send server-side events to Meta. That is exactly why running both without a plan can create duplicate Purchase events, mixed diagnostics, and inflated reporting. The question is not “which one can send CAPI?” It is which system should own Shopify Purchase.
Keyword target
- Primary: Meta CAPI Gateway vs Elevar Shopify
- Secondary: Meta Conversions API Gateway vs Elevar, Elevar vs Meta CAPI Gateway Shopify, Shopify Meta CAPI Gateway duplicate events, should I use Meta CAPI Gateway with Elevar, disable Meta CAPI Gateway Elevar
Key takeaways
- Do not let two independent CAPI systems own the same Shopify Purchase event.
- Elevar recommends disabling Meta CAPI Gateway when Elevar server-side tracking is enabled.
- Gateway can be useful in some non-Elevar setups, but it does not replace source-of-truth validation.
- The decision should be made by event ownership, deduplication, and payload quality.
Why this comparison matters
A Shopify store can send Meta events through the Facebook & Instagram app, Meta CAPI Gateway, Elevar, Stape, GTM server-side, or other apps. If two systems send Purchase independently, Meta may see multiple server and browser origins for the same order. Even if each tool “works,” reporting can still be wrong.
Decision table
Use one owner per event. Feed/catalog functions are separate from conversion ownership.
| Setup | Best use | Main risk |
|---|---|---|
| Elevar owns Meta Purchase | Stores already using Elevar as data layer/server-side source | Native Meta/Gateway left active and duplicates Purchase |
| Meta CAPI Gateway owns Purchase | Simpler non-Elevar setup needing a Meta-managed path | Less Shopify-specific control than a dedicated ecommerce data layer |
| Facebook & Instagram app owns Purchase | Basic Shopify setup with low maintenance needs | Limited control and possible overlap with other tools |
| GTM/Stape owns Purchase | Technical team wants server-side GTM control | Higher maintenance and manual deduplication risk |
| Multiple owners active | Usually accidental | Inflated purchases and optimization problems |
What to inspect before switching
Before disabling anything, document the current source of every Meta Purchase event. Check browser Pixel, server CAPI, event_id, event_name, order ID, value, currency, and event origin. Then make one system the owner and retest.
Related TrackingAudit guides
Diagnostic workflow
- Open Meta Events Manager and inspect Purchase event origins.
- List every tool that can send Meta Purchase: native app, Gateway, Elevar, GTM, Stape, Trackify, theme code.
- For one test order, record browser and server event IDs.
- Check whether Gateway and Elevar both send server Purchase.
- Check whether the native Shopify Meta app still sends Pixel or CAPI events.
- Choose the Purchase source of truth.
- If Elevar owns Purchase, disable conflicting Gateway/native purchase paths according to documentation.
- Retest one Shopify order and confirm one deduplicated Purchase.
- Monitor Events Manager diagnostics after processing.
What not to do
- Do not run Meta CAPI Gateway and Elevar for the same Purchase event without a dedupe design.
- Do not disable product catalog or shop features blindly; separate feed functions from conversion tracking.
- Do not use Ads Manager totals alone to decide whether deduplication works.
- Do not migrate during peak spend without before/after validation.
TrackingAudit validation checklist
- All Meta event sources listed
- Gateway status checked
- Elevar Meta destination checked
- Native Meta app checked
- event_id compared
- Purchase owner selected
- Duplicate server source disabled
- Test order validated
- Events Manager diagnostics reviewed
- Rollback plan documented
Need the tracking checked before scaling?
TrackingAudit can compare Shopify orders against the active event stack and show which system is missing, duplicating, or misattributing purchases.
Get your free audit →About the author
Frequently asked questions
Can I use Meta CAPI Gateway and Elevar together?
Not for the same Purchase event unless you have a deliberate deduplication design. Elevar recommends disabling Gateway when Elevar server-side tracking sends Meta events.
Is Meta CAPI Gateway bad?
No. The problem is duplicate ownership. Gateway can fit some setups, but it should not unknowingly overlap with Elevar.
Should the Facebook & Instagram app stay installed?
It depends on feed, shop, and pixel ownership needs. Do not let it send duplicate Purchase events if Elevar owns Purchase.
How do I know which system sends Purchase?
Use Meta Events Manager event origins, test events, event_id, and one Shopify test order.