Fix Facebook Pixel Errors - How to Fix Errors With The Facebook Pixel
Fix Facebook Pixel Errors - How to Fix Errors With The Facebook Pixel
Learn how to fix facebook pixel errors quickly and easily using this video.
If the Facebook pixel isn’t working for you, it’s probably due to one of a few common pixel errors.
I’ve timestamped each of the Facebook pixel errors that are covered in this video below. Click the timestamp to skip straight to the particular Facebook pixel issue you’re experiencing.
If you’re having issues with the Facebook pixel, this video will help you fix it.
00:00 - 01:41 - Do this first!
01:42 - 03:50 - No Pixel Found
03:51 - 04:30 - You Have Opted Out of Tracking
04:31 - 06:21 - Pixel Activated Multiple Times
06:22 - 07:50 - Pixel Took Too Long to Load
07:51 - 08:58 - We Detected an Event Code But The Pixel Has Not Activated For This Event, so no Information Was Sent to Facebook
08:59 - 10:00 - Invalid Pixel ID
10:01 - 11:53 - Cannot Find Product Catalog
11:54 - 13:39 - Missing Value Parameter
13:40 - 15:59 - Not a Standard Event
Link to Facebook’s Standard Event list: https://en-gb.facebook.com/business/h…
🔔 Subscribe for more paid traffic \u0026 digital marketing strategies:
— https://www.youtube.com/c/AndrewHubba…
👋 Say hi on social:
— Instagram: https://instagram.com/andrewnhubbard
— Facebook: https://facebook.com/andrewnhubbard
— Twitter: https://twitter.com/a_hubbard
• Fix Facebook Pixel Errors - How to Fi…
#facebookpixel #fbpixel #fbads #marketing
Content
0.45 -> - In this video, I'm going to show you
1.66 -> how to fix the most common
3.01 -> Facebook pixel errors
that you may experience.
5.9 -> Now, I've actually included
in the description below
8.76 -> different timestamps,
along with each error.
11.78 -> So if you're experiencing
a particular error,
14.46 -> and you just want to
skip straight to that,
15.87 -> have a look in the description,
16.98 -> there are all the markers
that you can just click it
19.16 -> and go to that part of the video.
21.07 -> But the first thing I'll say,
22.69 -> is at least do step number one,
25.31 -> that will help you pretty much
26.86 -> eliminate a bunch of errors straight up.
29.39 -> So the first thing I want you to do,
31.44 -> let's call this step one,
33.35 -> is go ahead and disable any ad blockers
36.56 -> that you may have in your browser.
38.18 -> Personally, I don't use ad blockers,
39.78 -> but I know a lot of people do.
40.84 -> And if you have an ad blocker
42.44 -> that will cause errors with the pixel.
45.03 -> So disable any ad blockers,
46.83 -> and the second thing is, if
you haven't done it already,
49.85 -> download the Facebook Pixel
Helper Chrome extension.
52.96 -> So there's a specific Chrome extension
55.47 -> that you can install,
56.7 -> and that actually will give
you diagnostic information
59.68 -> on the Facebook pixel
60.77 -> for any website that
you're visiting, okay?
63.43 -> So again, disable ad blockers,
66.45 -> download the Facebook Pixel
Helper if you haven't already,
68.99 -> because that's going to
give you more information
70.7 -> on why the pixel may
or may not be working.
73.65 -> Now, if you're new to this channel,
75.31 -> hi, welcome, my name is Andrew Hubbard,
77.19 -> I'm the founder of Hubbard Digital,
78.72 -> and we're a Facebook advertising agency
81.01 -> and education company.
82.3 -> And we help online businesses
grow using digital marketing.
86.2 -> Now before we jump into the first error,
87.86 -> the only thing I ask if
you're watching these videos,
89.54 -> is if you enjoy them,
please hit the like button,
91.27 -> it really does help me and
it helps the channel grow.
93.74 -> And if you wana hear more from me,
95.21 -> make sure you click subscribe
and click that little bell
97.3 -> to get notified whenever
I release a new video.
99.74 -> Okay, so the first error
we're going to cover
101.54 -> is the No Pixel Found error.
103.55 -> And basically, this is
telling you that the pixel
106.03 -> has not been found at all on the website.
108.5 -> So for some reason, the pixel
code just doesn't exist,
111.31 -> it's usually an implementation problem,
113.18 -> it means that however
you've implemented it,
114.88 -> hasn't worked properly.
116.46 -> So first of all,
117.293 -> I recommend using the
plugin PixelCaffeine.
119.12 -> So it's by a company called AdEspresso.
122.07 -> So if you use that
WordPress plugin to install,
124.1 -> that's probably the most foolproof way
125.62 -> that I've found to do it,
126.453 -> and that can be an easy way to do it
127.78 -> if you just can't get the
pixel to sharp at all,
130.1 -> and you keep seeing the
no pixel found there.
131.97 -> But if you want to troubleshoot this,
133.7 -> the first thing I recommend doing,
135.49 -> is go to your website,
136.51 -> right click anywhere on the background,
138.23 -> and click view page source.
140.17 -> And that's going to
show you the source code
142.05 -> for your website.
143.41 -> Now, don't worry, all you need
to do is press Command + F
146.16 -> if you're on a Mac or
Ctrl + F I think on a PC
150.18 -> to search the page.
151.7 -> And just search for the word pixel.
154.1 -> Or you can even search for Facebook pixel.
157.57 -> Okay, so type that in.
161.06 -> And you should find your
Facebook pixel code, okay?
165.47 -> So you should be able to
see your Facebook pixel code
167.75 -> inside that page source code.
169.67 -> Now, if you can, that's good,
172.33 -> if you can't see it at all,
173.78 -> it means the pixel isn't on the page
175.26 -> and there's obviously
something broken there
177.08 -> in the way you've implemented.
178.58 -> So if you can see it, that
means it's on the page,
182.25 -> but for some reason,
183.15 -> it's not being picked up by
the Facebook Pixel Helper tool.
186.6 -> Now, if that's the case,
188.75 -> make sure it's not commented out.
190.43 -> So if the source code is green,
193.61 -> that means that it's
commented out for some reason.
195.83 -> And that's bad, you need to fix that,
197.67 -> remove the comment tags to get rid of that
200.73 -> so that it's actually being
read by Google Chrome.
204.77 -> But if it appears,
205.83 -> then go back into wherever
you've implemented it.
208.56 -> So if you've implemented it manually,
210.72 -> inside of WordPress, go and check that,
213.17 -> if you're using a plugin, make
sure the plugin is active,
216.27 -> make sure that that plugin
217.92 -> isn't conflicting with other plugins,
220.03 -> and like I said, If you
still can't figure this out,
222.91 -> remove the implementation you've got,
224.94 -> try with PixelCaffeine,
226.31 -> and they'll probably
fix the problem for you.
228.64 -> Okay, moving on to error number two,
230.29 -> and that is, You Have
Opted Out of Tracking.
233.37 -> Now this error means that you've actually
235.08 -> inside your Facebook profile,
236.63 -> opted out of being tracked by Facebook.
239.51 -> So obviously, that's a problem,
240.75 -> because when the pixel is
trying to send information
243.87 -> back to Facebook,
244.92 -> it's recognizing that
you've actually decided
246.92 -> that you don't want to
be tracked by the pixel.
249.73 -> So the way to change this,
251.1 -> is to go into your Facebook settings,
253.66 -> and then inside those settings,
255.71 -> you can actually go to the area
257.97 -> where you enable or disable tracking,
260.57 -> and you can switch that to on.
262.8 -> So as you can see now,
264.48 -> we're just going through that process,
266.52 -> and we can turn it on here,
268.15 -> and once you do that, problem solved.
271.38 -> The third error we're going to talk about,
272.65 -> is Pixel Activated Multiple Times.
274.84 -> What this means is, the same
pixel and same pixel code
278.73 -> was actually activated
more than once on the page.
281.68 -> Now this is a problem
282.59 -> because you don't want duplicate results.
284.31 -> You don't want Facebook
double counting traffic
286.93 -> to your different web pages.
288.35 -> It's going to double count conversions
290.24 -> and all sorts of things
and cause you problems.
291.81 -> So obviously you wanna fix this.
293.66 -> Now, the most common reason I see
295.75 -> for the Facebook pixel
triggered multiple times error,
300.8 -> is usually it's when either
people use a blanket plugin,
305.35 -> like let's say,
306.183 -> AdEspresso to add the
pixels to their whole site.
308.41 -> But then for some reason,
309.53 -> they also add the pixel code individually
312.47 -> to different pages.
313.67 -> And so it's already
being added by AdEspresso
316.34 -> or a specific plugin to the whole website,
319.12 -> and then they've gone and added pixel code
322.45 -> to individual pages.
323.41 -> So it's loading on the site,
324.45 -> then it's loading on
that page a second time,
326.85 -> so check for that.
328.37 -> Also, another reason I see this happening
330.97 -> is because people will implement
332.92 -> their standard event tracking,
334.41 -> so standard events being
335.46 -> a type of conversion tracking incorrectly.
338.41 -> And what they'll do,
339.51 -> is they'll put the pixel code
340.79 -> and then they'll put the
same pixel code again,
343.21 -> but with this time with the
standard event added in,
345.99 -> and that results in a double firing.
347.77 -> So what you should be doing there,
349.55 -> is just having the pixel code,
351.66 -> and then adding just a little
snippet for the standard event
354.9 -> below that pixel code.
356 -> And that's how you
should properly implement
357.89 -> your standard events.
359.13 -> So check for both of those things.
361.71 -> Again, the way to easily see this,
363.81 -> is going into your page source,
366.08 -> and seeing if the pixel
code is duplicated twice.
369.57 -> And then if that's the case,
370.78 -> then you know that somewhere somehow,
373.25 -> it's being added a second time,
374.9 -> and you need to find that
376.33 -> and get rid of the second implementation.
378.95 -> All right, number four,
Pixel Took Too Long to Load.
382.48 -> I see this one quite frequently.
384.73 -> There's two reasons why it might happen.
386.21 -> The first reason,
387.44 -> is usually because the
pixel has been implemented
390.72 -> too far down the page.
392.7 -> So you really wanna implement the pixel
394.77 -> just before the closing
head tag in your code.
397.81 -> Most plugins will do this for you.
399.49 -> And if you're using a plugin
401.51 -> that allows you to inject the code,
403.54 -> then make sure you've
selected to add it in the head
405.92 -> and not in the body or the footer, okay?
408.9 -> So again, make sure it's in the head,
410.68 -> not the body or the footer,
411.71 -> if you're using a plugin
that allows you to do that.
413.9 -> If you've manually installed this,
415.33 -> or had a developer do it,
make sure they've done that.
417.51 -> Now, the easiest way to check this,
419.2 -> again, go into your page
source, hit Command + F,
423.02 -> and then search for /head.
426.39 -> And then that will show
you the closing head tag,
429.11 -> it's the tag with /head and
then closing pointy bracket.
434.27 -> Make sure the pixel is above that.
435.95 -> If it's not, then you
know, that's a problem,
437.92 -> and you can go and
organize to get that fixed.
440.5 -> Now, the other reason
why this might happen,
442.12 -> and this is probably the most
common reason I say this,
444.34 -> is your pages just slow, right?
447.48 -> That's a problem.
448.46 -> You don't want a slow running page,
450.1 -> if you're sending traffic
to a particular page,
453.53 -> that page has to be fast
454.92 -> in order to get the best performance
456.37 -> out of your advertising traffic.
458.07 -> So I've actually got a video on this,
460.16 -> I'll put a little link,
461.16 -> should pop up now the top of this video
462.66 -> to go and look at how
to optimize your page.
465 -> So check that one out.
466 -> But yeah, that's usually the reason,
467.28 -> if your page is slow,
you need to speed it up.
468.98 -> All right, not much more
I can say about that one
470.86 -> so let's move on to number five, which is,
472.56 -> we detected event code,
473.71 -> but the pixel hasn't
activated for this event.
476.51 -> So Facebook has not sent
any information basically.
479.83 -> Now what this means is,
481.27 -> it's found standard event code,
483.29 -> so it's trying to track a conversion,
485.01 -> but your base pixel hasn't activated,
487.25 -> so it doesn't know which
pixel it's associated with.
490.75 -> So what you need to do,
492.13 -> is make sure that your Facebook pixel,
494.61 -> the base code is above the standard event
498.55 -> or the conversion tracking
code on the page, okay?
501.97 -> So you need to go in
again to the page sources,
503.93 -> the easiest place to look at this.
505.6 -> Make sure that the
Facebook base pixel code,
507.63 -> the big chunk of pixel code
509.18 -> is above the actual standard event code,
512.77 -> whether it's purchase or
lead or complete registration
515.79 -> or whichever event code you're using.
517.17 -> So make sure it's above and not below.
519.28 -> If the base base pixel is below,
521.72 -> that's what's going to cause this error.
523.26 -> Now I have seen this happen as well
525.15 -> in situations where people
have got ad blockers turned on,
527.8 -> it will cause this error sometimes.
529.34 -> So again, make sure you've got
that ad blocker turned off,
532.06 -> because that's going to
cause you a world of pain
533.86 -> when it comes to the pixel,
535.64 -> because it just doesn't
let it work properly.
537.54 -> Which moves us on to number six.
539.3 -> So that is Invalid Pixel ID.
541.03 -> So what this means is the pixel ID
543.11 -> that you've put with your
pixel code on your website,
547.24 -> is not correct.
548.35 -> So it's probably a typo.
549.78 -> But basically, it doesn't
match the pixel code
552.32 -> inside Facebook ad manager,
553.709 -> or the pixel ID inside
the Facebook ad manager.
556.75 -> And so what you want to do,
558.63 -> have a look at the pixel code.
560.52 -> So if you look at the code,
there's a pixel ID in there,
563.62 -> it's a long string of numbers,
565.24 -> then go across into Facebook ad manager,
568.32 -> go to the events manager.
569.82 -> And then once you're
inside the events manager,
573.1 -> you need to go and find your pixel ID
575.25 -> which is right there under the pixel.
577.69 -> Find that ID and make sure
that it matches exactly
580.58 -> with what is in your pixel code.
583.06 -> Because if it's off at all,
585.21 -> if there's a space in there
that shouldn't be there,
587.09 -> if there's a number in there that's wrong,
589.07 -> it's going to give you this error.
590.18 -> So simply check that,
591.15 -> and correct it if it's wrong.
592.65 -> If you're using the pixel caffeine plugin,
595.51 -> you won't get this.
596.4 -> Like it does it automatically for you
598.07 -> so you won't have to worry about this.
600.17 -> Okay, number seven is,
Cannot Find Product Catalog.
603.6 -> So this is where the catalog ID
606.08 -> that's in your pixel code,
607.84 -> doesn't match a product catalog
610.38 -> that is associated with
this Facebook pixel.
612.72 -> So what it's doing, is it's going,
614.4 -> okay, I've got this pixel ID,
615.92 -> and it's got this catalog ID inside of it,
618.49 -> and I'm looking at all of
the catalogs associated
621.46 -> with this pixel,
622.75 -> and I'm not seeing a match, right?
624.39 -> So there's a problem there.
625.9 -> And it's likely
627.06 -> because the product catalog
ID in your pixel is incorrect,
630.29 -> or you just haven't associated
632.35 -> the catalog with that pixel yet.
633.76 -> So the first thing, is go
into the catalog manager.
637.28 -> So from Facebook Ads Manager,
you can click on the menu,
640.45 -> and go to catalog manager,
643 -> and then once you do that,
you'll see your catalogs listed,
646.28 -> make sure that the catalog ID
649.19 -> for the catalog that
you're trying to link up
652.62 -> matches exactly what's being sent over
655.27 -> in the product catalog ID
field in the pixel code, okay?
659.21 -> So make sure that's matching.
661.06 -> Again, you can view this in the
source code for the website.
664.37 -> And you also need to make
sure the product catalog
666.87 -> is associated with your pixel.
668.79 -> Now the way to do that,
670.09 -> is again go back to the catalog manager.
673.74 -> Once that's open, select your catalog.
676.39 -> So click on that.
678.64 -> And then go to Settings.
680.26 -> And that's going to open up
the settings for that catalog.
683.84 -> Now, next to event sources,
686.71 -> you can then click on connect to tracking,
689.82 -> that's going to bring up a list of pixels
691.52 -> that you've got access
to, select the pixel
693.73 -> that you want this catalog
associated with, okay?
697.08 -> So make sure you've done that,
700.2 -> and then go back and check the pixel.
701.767 -> And if you've done those two things,
703.35 -> making sure that pixel ID and
the catalog ID are correct,
706.42 -> and making sure that the catalog
707.84 -> is associated with the pixel,
709.63 -> that should fix this error for you.
712.349 -> All right, next up we got the
Missing Value Parameter error.
716.33 -> So what this means,
717.43 -> is you're using a standard event,
720.75 -> that should have a value
associated with it.
722.97 -> So for example, the purchase event,
724.94 -> you normally send a
value and a currency code
727.48 -> to say this is the purchase,
this is how much it's worth,
730.14 -> and this is the currency
that that amount is in.
733.89 -> So if you're using a standard event
735.89 -> where Facebook expects
a conversion amount,
739.14 -> and you don't have that included,
740.53 -> that's going to give you this error.
742.11 -> So if you have a look at your code,
744.31 -> and it either is using a purchase
746.97 -> or an event that normally has
a mount associated with it,
751.43 -> but it's not sending the
conversion amount value,
756.31 -> so have a look at that, if it
doesn't have that in there,
758.73 -> then that's a problem, okay?
760.65 -> So what you want to do,
is go in and include that.
764.38 -> So if you go over to the documentation,
766.94 -> you'll be able to see what
those parameters look like,
769.76 -> how to insert them,
770.593 -> and there should be a screenshot
now, you can have a look
773.59 -> and see exactly what that
code should look like.
776.34 -> So you can see there
777.58 -> where you need to insert
the dollar amount, okay?
780.55 -> And so make sure that's in there,
782.51 -> make sure you have the
currency code as well,
783.97 -> because if you don't
put the currency code,
785.73 -> it's going to give you a different error.
787.43 -> So make sure you've got that covered,
788.77 -> And then you should be fine.
791.4 -> One thing I will note here,
793.25 -> is the complete registration event
795.84 -> actually expects conversion amounts,
800.09 -> and it will give an error
inside the Facebook ad manager.
803.28 -> So if that happens, it's just a warning.
806.07 -> I mean, if you're using let's
say complete registration,
808.8 -> and people aren't paying you money,
810.76 -> when they complete a registration,
812.45 -> then it's actually not a problem.
814.02 -> So it will throw you a warning,
815.61 -> but that's fine, you can
just ignore that one.
818.12 -> And the final one we're
going to talk about,
819.87 -> is an error that's called
Not a Standard Event.
822.88 -> Now, what this means,
824.44 -> is the standard event
that you're sending over,
826.81 -> so the particular conversion event
830.75 -> and the name that you've given it,
832.27 -> doesn't match one that
is in Facebook's list
835.32 -> of standard events, right?
838.04 -> Or default standard events.
840.06 -> This is usually a typo.
841.31 -> So for example, people will type purchases
846.02 -> as their standard event
name in their code,
848.77 -> instead of purchase.
850.86 -> So they'll put es on the
end when they shouldn't.
853.74 -> And that just makes Facebook,
855.84 -> hey, this, you know, I'm getting
this standard event name,
858.31 -> but it doesn't match any in our list.
860.35 -> So you know it's throwing an error.
862.35 -> So what you need to do
is just bring up the list
864.48 -> of Facebook's standard event codes.
867.33 -> And I'll put a link to that
in the description as well.
870.18 -> So go to that page,
have a look at the list,
872.52 -> have a look at the standard events
873.95 -> that you're sending in your code
875.2 -> and the names and make sure
that it matches correctly.
878.22 -> It's probably just a typo there,
879.97 -> fix that up and you'll be
able to get rid of that error.
882.89 -> Right, so these are the most common things
884.84 -> we see with the Facebook pixel, as I said.
887.07 -> The majority of the time is,
889.21 -> it's either a problem with
an ad blocker running,
892.54 -> or it's a problem with
the actual implementation
895.01 -> of the plugin that you're using,
896.85 -> or the way that you've actually
inserted it in your website.
899.58 -> So the easiest way to fix this,
901.36 -> is either clear it
902.43 -> and use something like
PixelCaffeine plugin
904.54 -> to add the code, that's quick and easy,
907.31 -> and then obviously removing ad blockers.
909.65 -> But if you're getting
these specific errors
911.16 -> and hopefully we've covered
it here and that helps.
913.05 -> Now, if you enjoye this video,
914.39 -> please give it a thumbs
up, that means you like it.
916.98 -> If you got any questions, if
it didn't solve your problem,
918.97 -> drop it in the comments below
919.99 -> because I do check those and
I do reply to those as well.
923.57 -> And of course, if you want to get notified
926.22 -> whenever I release a new video
928.15 -> on Facebook advertising
or digital remarketing,
930.43 -> then make sure you hit subscribe,
931.85 -> click that little bell to get notified
933.48 -> whenever that happens.
934.67 -> All right, thanks again for watching.
935.75 -> I always appreciate your time
937.01 -> and I'll see you in the next video.
938.003 -> Bye.
938.836 -> In this video I'm going,
941.12 -> I'm I recording?
942.126 -> Yes I am.
945.91 -> I gotta do that again, I'm sorry.
949.23 -> The plugin called PixelCaffeine.
955.99 -> All right, the third error is oops.
Source: https://www.youtube.com/watch?v=hF0DmR09s5k