Advertisers can use the Facebook pixel to capture intent information about how people are using their website. A single Facebook pixel is added to all pages of a website, and is then used to create website custom audiences. Advanced matching fields which are enabled for automatic advanced matching.
Represents whether automatic advanced matching is enabled for the pixel for identity matching purposes. First party cookie status to indicate whether first party cookies can be set for this pixel. ID of the business that owns this pixel or null if the pixel has not been claimed by any business yet. Advanced matching fields for which automatic advanced matching should be enabled. Enable automatic advanced matching for the pixel for identity matching purposes. Docs Tools Support. Marketing API.
Graph API Version v HTTP Headers include IP addresses, information about the web browser, page location, document, referrer and person using the website. Button Click Data — Includes any buttons clicked by site visitors, the labels of those buttons and any pages visited as a result of the button clicks. Optional Values — Developers and marketers can optionally choose to send additional information about the visit through Custom Data events.
Example custom data events are conversion value, page type and more. Form Field Names — Includes website field names like email , address , quantity , etc. We don't capture field values unless you include them as part of Advanced Matching or optional values. There are two ways to access these insights. First is through a table view. Select List Settings within Ads Manager and include these post-install results as part of your campaign columns.
You can view these insights in the main table view across install cohort dates based on the date range chosen. You can also chart these metrics by clicking the graph icon on your side panel after you choose an ad campaign. This view offers the ability to chart revenue, yield, and ARPU and compare it to your average performance across each metric. The x-axis is the time window, and the y-axis is the the metric you choose to chart.
Average Revenue per User ARPU is defined by the revenue gained from an install day cohort divided by the total users from that cohort. You can view 1-day, 3-day, 7-day, day, and day ARPU. To access all the raw data, you also have the option to export the post-install results by clicking the export button within the chart view section. The raw data will be exported by install cohort date.
0コメント