FBTrack ‑ Facebook像素代码与API , 289 条评论

整体评分
4.8
每个评分等级的数量
  • 90% 的评分是 5 星
    261
  • 1% 的评分是 4 星
    3
  • 2% 的评分是 3 星
    6
  • 1% 的评分是 2 星
    3
  • 6% 的评分是 1 星
    16
2023年8月10日

The pixel parts on the payment page are not working. I made all the necessary additions, but it still did not work. It is very important to follow the payment.

Gusta Sneaker
土耳其
15天 人在使用应用
2022年2月8日

it as decent idkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk

Cali Coast Vibes
美国
6个月 人在使用应用
编辑时间：2020年6月12日

The app worked the best for a few days, suddenly on one pixel it started recording multiple purchases(it was only on few adsets who were using the pixel, other adsets of that same pixel were recording correctly.), since the support was of not much help I removed the pixel which caused duplication of data on only few adsets.

Now when I switched to my second pixel, it worked fine for the first day & now its recording 2 purchase events on one single purchase only on few adsets & the purchase conversion value is equivalent to 1 purchase only.

I liked this app very much because of easy interface, but it messed up my whole analytics, even when I didnt made any changes to ads, or my website

Dualumi
印度
大约2个月 人在使用应用
Optiapps已回复 2020年6月17日

The issues you are reporting are related to your configurations on Facebook side for the adsets that had an issue. As a side note, If you choose "Unique purchases" for the reporting column you will have the correct number of purchases for the adsets mentioned. You can use the Facebook pixel helper to see what pixels fire when a purchase is made. If the pixel helper shows that the pixels that fire are as you had expect, the job of Fbtrack ends here. Any irregularities you might notice after that in your Facebook reporting are related to your configurations on Facebook side.

1
1