Hello,
I noticed that the built-in Meta Pixel tag doesn’t send the “PageView” event like it would when you integrate the pixel via a custom code tag. See “fbq(‘track’, ‘PageView’);” below:
<!-- Meta Pixel Code -->
<script>
!function(f,b,e,v,n,t,s)
{if(f.fbq)return;n=f.fbq=function(){n.callMethod?
n.callMethod.apply(n,arguments):n.queue.push(arguments)};
if(!f._fbq)f._fbq=n;n.push=n;n.loaded=!0;n.version='2.0';
n.queue=[];t=b.createElement(e);t.async=!0;
t.src=v;s=b.getElementsByTagName(e)[0];
s.parentNode.insertBefore(t,s)}(window, document,'script',
'https://connect.facebook.net/en_US/fbevents.js');
fbq('init', 'XXXXXXXXXXXXXXX');
fbq('track', 'PageView');
</script>
<noscript><img height="1" width="1" style="display:none"
src=https://www.facebook.com/tr?id=XXXXXXXXXXXXXXX&ev=PageView&noscript=1
/></noscript>
<!-- End Meta Pixel Code -->
Instead, the tag offers a list of standard events to send, but there’s no “PageView”.
I think that the built-in Meta Pixel tag should only serve to replicate the way the pixel works when you integrate it via its full code, and always send the “PageView” event automatically. Then, a second built-in tag dedicated to event sending (standard or custom) would be more appropriate.
Thank you!