![]() Since we are viewing our product on a different page, we should get another PageView event. ![]() Then, I’ll trigger the View Content event whenever we view a product. This is because I consider a click as a website engagement that I want to track. Having all these events on your website is not mandatory, but feel free to implement them if you want.Īfter the PageView event, you can see that I have a custom event for when the user clicks on the product. Let’s briefly discuss how to structure an eCommerce store to explain these new events. At this point, just ensure that the events important to you are being shown. The setups and the events we want to track are likely different. If you are following, you will see that you might not have the same events listed in your Pixel. Here, we can see five new events in the test events tab, sorted in reverse chronological order. Let’s quickly go back to our events manager to check if new events have been sent to our Pixel. Those steps should have triggered a few events already. Let’s scroll down and click on one of the products. But for now, let’s go back to our test events tab and start the purchase process to check if any other errors appear. No doubt that a majority of you who had been running ads for at least a year have seen this warning here. Even before testing our events, you can see in my Pixel diagnostics tab that I have three active issues.įor issues relating to eCommerce websites, we have the Invalid Purchase Currency Code and the Invalid Purchase Value Parameter. Note that I have tweaked my setup to ensure that I have errors to show you exactly what it looks like when you have an error and how to fix them. Since our demo website is an eCommerce shop, let’s go through the entire purchase process. Now, we need to verify if all the events we care about are showing in the events manager without an error warning. If you find that your website is sending events to the wrong Pixel ID, install the correct one and repeat the steps mentioned above. Other ways to view your Pixel ID are checking the URL and looking at your Data Sources in the events manager. You will see your Pixel ID on the right side. One way to verify this is by going to the Overview tab. Make sure that the Pixel ID you see in this extension matches the one you have in the events manager. If you find that there is no Pixel event showing when you want to test your events, it’s usually because you’re using the wrong Pixel ID. Opening this extension on my website, we can see that a PageView event was sent successfully. It can also show a detailed overview of the page’s pixels, including warnings, errors, and successes. The Facebook Pixel Helper extension is a troubleshooting tool that shows the number of Pixel events sent to your Meta account. If you’re still not getting the event, download the extension called Facebook Pixel Helper. If you are still not receiving a PageView event, I recommend using Google Chrome and trying again. ![]() If we go back to the events manager, we should get a PageView event. This should load our website on another tab. To test browser events, all we have to do is enter our website URL.Ĭopy your website URL and paste it into the space provided. If you want to learn more about server events, check out our post on how to send Meta Pixel events via the conversion API using Zapier, or our video on how to use the conversion API with Google Tag Manager. In this post, however, we’ll only go in-depth on discussing how to test browser events. Here, we can see the steps you can follow to test each type of event. If we scroll down, we can see that there are two kinds of tests we can do – Test Browser Events and Test Server Events. Select Clear Activity and confirm for a second time when the popup comes up.
0 Comments
Leave a Reply. |