BlendJet<\/a> (as of August 2022). Browse through a couple of pages on the site and exit the browser. Now, open up Facebook. Before you know it, you will be swarmed with remarketing ads by Blendjet, all based on your IP & User Agent. Boom.<\/p>\n\n\n\nUsing these attributes<\/h2>\n\n\n\n When working with Facebook’s CAPI, you should use as many possible data points as possible. It\u2019s that simple. I understand there are scenarios where this isn’t simple or possible, so try and prioritize these.<\/p>\n\n\n\n
Deterministic values are preferred. Whenever you can send these I recommend you do. The probabilistic values reside in the user’s browser and are usually easier to collect, but require you to store them actively. I recommend grabbing these as hidden fields on a form submission. Note that the IP address isn’t available directly in the browser (only on the server calls).<\/p>\n\n\n\n
In B2B cases, the personal information (email, phone number) is tricky to use for matching as it will likely differ from the data in the user’s Facebook profile (you don’t log into Facebook with your work email). In this case, the Click ID and Lead ID are essential.<\/p>\n\n\n\n
Facebook used to present a score in the Events Manager that ranked your Event Match Quality based on the number of attributes passed, regardless of their relevance\/accuracy. A linear scale now replaces it, but I still tend to ignore it when doing CAPI implementations for clients.<\/p>\n\n\n\n
On the significance of sending all keys<\/h2>\n\n\n\n This case as in an interesting example from a client of mine. They are offline events for down funnel actions of the users arriving from their CRM.<\/p>\n\n\n\n
Data sent to Facebook was based only on users with the FBCLID present. We also sent the user’s email address as an additional match key. The events are sent using Zapier (yellow line) and received in the Facebook Events Manager (red line) which logs all events. Events reported in the Ads Manager (blue line) are attributed to actual campaigns.<\/p>\n\n\n\n
During March 19th, the scheduled query sending the data to Facebook was changed in a way that damaged the email. Only the FBCLID was now present as a match key, and the match rate from events sent to events attributed plummeted. <\/p>\n\n\n
\n
<\/figure><\/div>","protected":false},"excerpt":{"rendered":"Working with many clients on Facebook’s Conversion API (aka CAPI), I often receive questions about how the Event Match Quality is calculated for these events. To explain this, I usually take a step back to explain how I understand Facebook’s user identification mechanisms work. The attributes used in the CAPI payload open a window into […]<\/p>\n","protected":false},"author":1,"featured_media":5236,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"_links":{"self":[{"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/posts\/5232"}],"collection":[{"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/comments?post=5232"}],"version-history":[{"count":4,"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/posts\/5232\/revisions"}],"predecessor-version":[{"id":5804,"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/posts\/5232\/revisions\/5804"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/media\/5236"}],"wp:attachment":[{"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/media?parent=5232"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/categories?post=5232"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/tags?post=5232"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}