Tealium Learning Center

Thank you for sharing your solution, this was very helpful! ... View more

Hi Marielle! We recently compiled the following article on Facebook CAPI Best Practices for configuration. Those tips should help, but keep in mind that CAPI is meant to be a fallback in the case that the client-side pixel is not received. To achieve this result, you'll want to ensure that your event feed conditions match those of your client-side tag and how the event is being triggered. For example, if you have a load rule on your Facebook tag to allow for consent and you trigger a "ViewContent" event when "tealium_event" equals "product_view", then your Facebook event feed will need to cover the consent piece AND the event trigger (tealium_event = product_view). This will ensure that both the client-side and server-side events are triggering in parallel and are not dependent on each other (ex: an event ID being present).  If you are seeing the event trigger but the event ID is not present, then please refer to the article linked above on how to configure the client-side tags to allow for the event ID to generate in time for the Tealium Collect tag to send it in the final data payload.  ... View more