I have a correction!
Last week I told you about a possible bug. Some custom events don’t appear among metrics you can add as columns in Ads Manager. From what I could tell, there was no rhyme or reason why this was. As it turns out, there was a reason.
Luckily, Meta employees follow my videos, and I was properly corrected. Conversion events tracked by the pixel, app SDK, or API that are outside of standard events. These tend to be created to fit the publisher's needs when a pre-defined standard event will not. More will only appear among metrics to add as columns if you’ve previously optimized for that event. I tested this with an event that didn’t previously appear, and it worked.
Here’s what you need to do if a custom event doesn’t appear…
1. Create an engagement The campaign is the foundation of your Facebook ad. This is where you'll set an advertising objective, which defines what you want your ad to achieve. More and select the Website conversion location in your An ad set is a Facebook ads grouping where settings like targeting, scheduling, optimization, and placement are determined. More.
2. Select your pixel and your custom event as the conversion event.
3. If you don’t want to run a campaign now, set a start date in the future and publish the campaign.
The custom event should then immediately appear when adding columns. You can then delete the campaign since it never ran. Or you could simply run the campaign if you want, but you don’t have to.