Facebook has the data on what the lead did before it leaves a Meta platform. So when you send that user information back to Meta, it looks to see what action they did prior to leaving the platform and attributes it to the proper ad.
The option for not wanting to be tracked is only for pixels when used on a app right? Not if you are directing the traffic for a landing page or website?
Thanks for this! 1. A question on duplicate conversions: My meta pixel is tracking my lead form *submissions* already with event manager/ the standard pixel. Now, that I'm sending CAPI with user lead data, is this duplicative (eg, it thinks it's counting 2x leads when really it's one)? In this case should I disable leads from event manager and stick to using that for page views? 2. It would be great if you could build a follow up video on testing a zapier event in the meta test manager. I'd love to see how it renders in system when you are testing, to be sure it works.
You can run both but you need to make sure you're deduplicating events. A bit complicate but if you feel confident in the CAPI data you can turn off the pixel event. Having both is recommended to get the most accurate data. I'll see if I can record a video on how to test the CAPI event in Zapier.
Are you sending data that was not driven by Facebook as well? That was something I was unclear on. Like, do you just push all lead data through, even if it came from something else or how do you inform Facebook, without drumming up false positives? I have experience sending offline conversions/api conversions in Google Ads, but I used click IDs to determine what to send, here there didn't seem like there was a distinction, so I am wondering how that separation happens?
The easiest way to do it is to create separate landing pages for each channel. OR you could use Zapier to filter by source so only Facebook leads get sent through CAPI.
@@chaddlepaddle technically you could send all data through. And then let Meta determine if the event came from a Meta ad. It also depends on how sophisticated your attribution data is set up. We can get into the weeds on that topic but if you're doing some sort of scientific attribution model then it's best to send all data through.
The trigger won't be Facebook conversion. It will be whatever event that you're trying to track. So if it's a lead event you want the trigger to be a form submit. If it's a purchase it's the order event.
![Facebook / Meta Conversion API setup + Event Deduplication [Step-by-step guide]](http://i.ytimg.com/vi/ytNnSVodsA4/mqdefault.jpg)
Hi Kevin - when you send the lead event back to Facebook, how does Facebook know which specific ad the lead event was tied to?
Facebook has the data on what the lead did before it leaves a Meta platform. So when you send that user information back to Meta, it looks to see what action they did prior to leaving the platform and attributes it to the proper ad.
@@brandarrow. where do I get the lead data? Do I need to collect it myself like using landing registration form or can I use Meta's API to do that?
The option for not wanting to be tracked is only for pixels when used on a app right? Not if you are directing the traffic for a landing page or website?
When you choose the option to not be tracked, Meta can still track your actions within the app but it can't track what happens once you leave the app.
Damn that sucks good that I have the Capi then@@brandarrow.
Thanks for this! 1. A question on duplicate conversions: My meta pixel is tracking my lead form *submissions* already with event manager/ the standard pixel. Now, that I'm sending CAPI with user lead data, is this duplicative (eg, it thinks it's counting 2x leads when really it's one)? In this case should I disable leads from event manager and stick to using that for page views? 2. It would be great if you could build a follow up video on testing a zapier event in the meta test manager. I'd love to see how it renders in system when you are testing, to be sure it works.
You can run both but you need to make sure you're deduplicating events. A bit complicate but if you feel confident in the CAPI data you can turn off the pixel event. Having both is recommended to get the most accurate data. I'll see if I can record a video on how to test the CAPI event in Zapier.
Why would you have such a large head image blocking all the important details of the video?
Guess I didn't notice it recording the video - will record a new one with some updated tips. Thanks for pointing that out!
Are you sending data that was not driven by Facebook as well? That was something I was unclear on. Like, do you just push all lead data through, even if it came from something else or how do you inform Facebook, without drumming up false positives?
I have experience sending offline conversions/api conversions in Google Ads, but I used click IDs to determine what to send, here there didn't seem like there was a distinction, so I am wondering how that separation happens?
The easiest way to do it is to create separate landing pages for each channel. OR you could use Zapier to filter by source so only Facebook leads get sent through CAPI.
@@brandarrow. Okay, so confirming, you wouldn't want to open end send all data through, you are still filtering that?
@@chaddlepaddle technically you could send all data through. And then let Meta determine if the event came from a Meta ad. It also depends on how sophisticated your attribution data is set up. We can get into the weeds on that topic but if you're doing some sort of scientific attribution model then it's best to send all data through.
How do we identify the client's IP address and send click ID?
Thanks for this video. Can i create a Custom conversion to catch this event? How should that be done? Thanks
Hey, do you still offer help with meta ads? I wrote you via email, it's not possible to deliver message.
Hey! Yes. Feel free to reach me directly at kevin@brandarrow.com
Thanks for creating this video, It is very helpful, much appreciated😃
Glad it was helpful!
No trigger available when I try to select Facebook conversion app, why?
The trigger won't be Facebook conversion. It will be whatever event that you're trying to track. So if it's a lead event you want the trigger to be a form submit. If it's a purchase it's the order event.
What about mobile apps? Do I need to use this stupid conversaion api?
God bless you
Appreciate you!
useless