Facebook Pixel Event Showing as Custom Event: Why and How to Fix It

Last checked against Meta's documentation. By Muhammed Abdul Kalam. Data loss

Quick fix

Facebook pixel event showing as custom event usually means the event name is spelled or capitalised wrongly. Meta's event names are case sensitive, so a lowercase viewcontent creates a custom event with that name instead of the standard ViewContent. Correct the spelling in the code and check it sits in the right place on the page.

  • Find the event in Events Manager and compare its name with the standard event list.
  • Correct the spelling and capital letters in the code.
  • Check the event code sits after the base code on the page.
  • Confirm the event in the test events tool.

Can't fix it yourself? Send me the details

What this error means

Meta has a fixed list of standard events with exact names. If your code uses a name that doesn't match exactly, Meta can't treat it as the standard event and records it as a custom event instead. Ads can't optimise for it as a standard event until the name is correct.

Why it happens

1Wrong capitalisation or spelling

Names are case sensitive, so any difference creates a custom event.

How to tell if this is you: Events Manager lists the event in lowercase or with a typo.

2Event code in the wrong place

The event snippet must come after the pixel base code.

How to tell if this is you: The event fires before the base code loads, or not at all.

3Base code missing on the page

Every page needs the base code, with only the event snippets differing.

How to tell if this is you: The page has an event snippet but no base code.

4A tag manager hides the code

With a tag manager the code is not on the page, so check inside the manager.

How to tell if this is you: The page source shows no pixel code.

How to fix it

Correct the event name

For: Wrong capitalisation or spelling

  1. Copy the standard event name exactly from the specifications list.
  2. Make sure the event is spelled correctly in the code.

Fix the placement

For: Event code in the wrong place, Base code missing on the page

  1. Verify the base code is accurate on every page.
  2. Put the event code in the right place after the base code.

Check inside the tag manager

For: A tag manager hides the code

  1. Troubleshoot within the manager, because the code is not on the page.

Test the result

For: Wrong capitalisation or spelling, Event code in the wrong place

  1. Verify the event in the test events tool.
  2. Check the Diagnostics tab for setup problems.

How long it takes

Meta doesn't publish a timeline for this.

How to stop it happening again

  • Copy event code from Meta rather than typing it.
  • Test every new event in the test events tool before launching ads.
  • Check the Diagnostics tab regularly.

From my desk

The cause is usually a typo in the event name, most often a lowercase letter, or code pasted by hand instead of copied from Events Manager. I check the event list in Events Manager first, because a stray custom event with a standard name is the giveaway, then fix the spelling in the code or tag.

Muhammed Abdul Kalam

When to get help

  • You've worked through the checks and the numbers or status still aren't right.
  • The setup involves a tag manager, Shopify app or developer you cannot reach and nobody can explain it.
  • Results are suffering during a launch or sale and every day costs real money.

Stuck on this? Send me the details.Tell me what the platform shows and what you've tried so far.

Send me the details

FAQs

Are Meta Pixel event names case sensitive?

Yes. Standard event names are case sensitive.

What happens if I type viewcontent instead of ViewContent?

Meta creates a custom event called viewcontent instead of recording the standard event.

Where does the event code go?

After the pixel base code, on pages that carry the base code.

How do I know the pixel is working?

The page view event reaches Meta and the pixel status becomes Active.

How do I test an event?

Use the test events tool, and the Diagnostics tab in Events Manager.

Sources