Closed frankzengjj closed 11 months ago
Hi,
This tag used a new version of API because we keep all up to date. Our partner agent is correct. We do not see any issues on other accounts that use this tag.
If you use Stape sGTM hosting, you can configure writing logs in production https://stape.io/blog/troubleshooting-server-side-tagging-using-server-gtm-logs
This will help a lot with debugging production requests/responses. Basically, you will be able to see how FB responds to each request. Also you can try to regenerate API token this sometimes helps. As an option, try the same with any new FB pixel. We had a few times issues with old pixels. And in this case, you need to write to FB support.
When I set a test code in the tag, the event manager can actually display that a server event is received. However, when I publish the container without test code, the event manager stop showing any server events. I verified that in preview mode the graph api returned 200.
Moreover, if I used another tag from facebook incubator, I am able to view server side event counts are increasing. Looking at their source code, I noticed that they used a lower api version (the one published in server side gtm gallery is v12.0) and different partner agent (gtmss-1.0.0-0.0.5). So I was wondering if I didn't use this tag properly or it has anything to do with api version or partner agent?