Facebook Pixel and CAPI Landing Page Report

The Landing Page Report with the Facebook Pixel provides critical insights into how visitors interact with a specific landing page on your website. This report aggregates data about user behavior, enabling you to evaluate the page’s performance and optimize it for better engagement, conversions, and other desired outcomes. It also connects landing page performance metrics with advertising data, facilitating improved campaign refinement.

Populating the Report with Data

The accuracy and completeness of the Landing Page Report depend on the implementation of event tracking. Below are the required steps to ensure data is correctly populated, depending on your tracking setup.

Client-Side and Server-Side Implementation

If you are using the Meta Conversion API in conjunction with both client-side and server-side event tracking, and you have implemented deduplication for all events as Meta recommends, no additional configuration is needed. The default JENTIS implementation will automatically provide sufficient data to populate the Landing Page Report.

A separate implementation of the server-side Landing Page Report Tag (“Pageview (Landing Page Report)”) is not recommended in this scenario. Please see below for more details on this.

Server-Side Only Implementation

If you rely solely on server-side event tracking without any client-side tags, an extra configuration step is necessary to ensure the Landing Page Report collects all required data.

Steps for Configuration:

Add the Special Event: In the JENTIS DCP configuration, include a dedicated event named ‘Pageview (Landing Page Report)’.
Event Deduplication: This special Pageview event will be deduplicated with the original server-side Pageview event to avoid duplication in reporting.

Important note:
If you use a hybrid event tracking approach (combining client-side and server-side tracking), please do not use the ‘Pageview (Landing Page Report)’ event. Even though all three Pageview events (client-side, server-side, and special Pageview) are sent with the same deduplication parameters, Meta may still present duplicated Pageview counts in your report. To maintain accurate reporting, rely solely on the default deduplication methods for hybrid implementations.