I am unable to enable the Meta Conversion API on my Shopify site. I am using Meta’s official app, “Facebook & Instagram”, and I have set data sharing to maximum. The pixel is connected, and I am receiving client-side events, but I am not receiving server-side events, so I cannot enable the Conversion API.
I contacted Meta support, and according to them, the pixel is correctly configured, and I should ask Shopify support. I also reached out to Shopify support, but they say the settings are fine and that I should contact Meta support.
I have connected other websites using the same app without any issues, and I don’t know what else to do to enable the Conversion API.
Thanks to anyone who can give me any ideas, even just suggestions!
Did you find a solution to this issue? I am seeing the same where on a store where the pixel is set up through the official Facebook & Instagram app with the data sharing set to maximum. However, I don’t see any Conversions API events coming through in Meta Events Manager.
This issue started for us last september where just the server events for purchase have been missing from one moment to the other. I switched to the omega app to connect pixel and capi and that worked, eventhough with lower tracking scores in event manager. Just wanted to see what´s going on with the native integration now and it seems even worse, because now i do not see ANY server data for ANY event… The picture shows the switch from omega to the native app…
Configure the meta Pixel and Conversion API(CAPI) through Google tag manager GTM for the best tracking accuracy and the highest event match quality score up to 9.3.
Shopify native apps can configure conversion API but these apps don’t use first party domain/sudbdomain for server side tracking/CAPI that’s why HTTP request gets blocked sometimes in case of some browsers and extensions.
I had a meeting with Facebook representative last week about pixel and conversion API setup. I was suggested to use 2 different pixel with the website. One should be configured through GOogle Tag Manager GTM both browser and server side tracking and another one with facebook and Instagram apps.
Our own app, WeltPixel Conversion Tracking, is in the same category as Omega, so discount me the same way on all of this. Two problems are tangled together in this thread and only the first one has been getting answered.
One correction before anything else, since it has been said twice and people will find this thread later. Conversions API traffic never touches the shopper’s browser. It goes from Shopify’s servers to Meta’s. A content blocker or a browser extension cannot interfere with it, and a first party subdomain buys you nothing there either, because there is no client side request to disguise. First party domains matter a great deal for the browser pixel and its cookies. They do nothing for native CAPI. So moving to GTM will not fix the blocker problem, because the server side never had it.
On running two pixels, one through GTM and one through the app: that will send the same purchase twice unless the two sides agree on one event id, and two independently built setups rarely do. Meta dedupes on that id, not on the value or the timestamp.
Erdnussbuddha, yours reads differently from the OP’s. Nimaia’s never started. Yours worked and then stopped, and then stayed dead through an app switch, which points at the connection rather than the settings. I would disconnect the sales channel entirely and reconnect it rather than touching data sharing again. That is a guess from outside the account, but the token behind that connection can expire without anything in either interface saying so, and toggling settings on a dead connection changes nothing.
