Facebook Ads Performance report
Renta pipeline templates allow you to create a set of related pipelines for Facebook Ads in a single action. Instead of manual configuration for each aspect, you can select a template, choose your accounts and schedule, and the system will create all necessary pipelines automatically.
Overview
Using pre-built templates streamlines the process of establishing a comprehensive data collection system for your marketing analysis.
The Facebook Ads Performance report template is designed to provide a comprehensive dataset for marketing analytics and optimization. It automatically creates 4 separate pipelines that work together:
| Pipeline | Description |
|---|---|
Ad statisticsfb_ads_statistics_* | Performance metrics like clicks, impressions, and spend. |
Ad campaign metadatafb_ads_campaign_metadata_* | Structural data for campaigns including objectives. |
Adset metadatafb_ads_dataset_metadata_* | Details for ad sets such as budgets and targeting. |
Ad metadatafb_ads_metadata_* | Specifics for ads including statuses and preview links. |
Data schema
Each component within the template provides a specific subset of data required for a holistic view of your advertising performance.
Each pipeline within the template exports a predefined set of fields. Below are the details for each table.
Ad statistics
This table contains the core performance metrics and dimensions.
| Field | Description |
|---|---|
| account_currency | The currency used by the ad account. |
| account_id | The unique ID of the ad account. |
| account_name | The display name of the ad account. |
| ad_id | The unique ID of the individual ad. |
| ad_name | The display name of the ad. |
| adset_id | The ID of the parent ad set. |
| adset_name | The name of the parent ad set. |
| campaign_id | The ID of the parent campaign. |
| campaign_name | The name of the parent campaign. |
| clicks | All clicks on the ad (all interactions, including link clicks). |
| impressions | The number of times your ads were displayed on screen. |
| spend | Total amount spent on the ads during the reported period. |
| reach | The number of unique users who saw your ads at least once. |
| frequency | The average number of times each unique user saw your ad. |
| inline_link_clicks | Clicks on links that direct users away from Facebook-owned properties. |
| date | The specific date for the reported metrics. |
| date_start | The start date of the report period. |
| utm_medium | UTM medium parameter for traffic categorization. |
| utm_source | UTM source parameter identifying the traffic origin. |
| utm_campaign | UTM campaign name for tracking individual efforts. |
| utm_content | UTM content parameter for distinguishing different ad Creatives. |
| utm_term | UTM term parameter typically used for keywords. |
| lead | Total leads generated and attributed to the ad. |
| onsite_conversion.lead_grouped | Number of leads generated directly through Facebook lead forms. |
Default settings.
When creating a pipeline through a template, Renta automatically applies optimized settings to ensure your data matches the Meta Ads Manager interface. These settings handle attribution and data consistency.
| Setting | Value | Description |
|---|---|---|
| action_report_time | impression | Determines whether to attribute actions to the time of impression or the time of conversion. |
| attribution_settings | account_attribution | Uses the attribution window defined at the ad account level for report consistency. |
| overwrite_period | 7 days | Automatically re-syncs the last 7 days of data to account for conversion lag. |
Ad campaign metadata
Contains high-level settings for your campaigns.
| Field | Description |
|---|---|
| account_id | The ID of the ad account. |
| id | The unique ID of the campaign. |
| name | The display name of the campaign. |
| buying_type | The ad buying method (such as Auction, Reserved). |
| objective | The primary objective of the campaign (such as Traffic, Awareness). |
Adset metadata
Contains detailed configurations for your ad groups.
| Field | Description |
|---|---|
| account_id | The ID of the ad account. |
| campaign_id | The ID of the parent campaign. |
| id | The unique ID of the ad set. |
| name | The display name of the ad set. |
| adlabels | Custom labels associated with the ad set. |
| bid_amount | The bid cap or amount you are willing to pay per result. |
| billing_event | The event that triggers a charge (such as Impressions). |
| budget_remaining | The remaining amount in the current budget. |
| daily_budget | Average daily budget for the ad set. |
| lifetime_budget | Total budget for the entire duration of the ad set. |
| configured_status | The status set by the user (Active, Paused). |
| effective_status | The actual current status of the ad set. |
| status | The processing status of the ad set. |
| created_time | The date and time when the ad set was created. |
| updated_time | The date and time of the last update. |
| start_time | The scheduled start time for the ad set. |
| end_time | The scheduled end time for the ad set. |
| optimization_goal | The specific event Meta optimizes for (such as Reach). |
| pacing_type | Defines the delivery pace (Standard, Accelerated). |
| frequency_cap | Limits how often users see the ad (Reach & Frequency). |
Ad metadata
Contains specific details and statuses for individual ads.
| Field | Description |
|---|---|
| id | The unique ID of the ad. |
| account_id | The ID of the ad account. |
| adset_id | The ID of the parent ad set. |
| campaign_id | The ID of the parent campaign. |
| name | The display name of the ad. |
| configured_status | The status configured in the dashboard. |
| effective_status | The actual delivery status of the ad. |
| status | The processing status of the ad. |
| created_time | The timestamp of ad creation. |
| updated_time | The timestamp of the last update. |
| preview_shareable_link | A shareable URL for ad preview. |
| conversion_domain | The domain where conversions are tracked. |
| ad_review_feedback | Feedback and reasons from Meta review process. |
Data relationships
Understanding the primary keys and relationships between tables is crucial for accurate data modeling in your BI tools.
The tables are designed to be joined together using common ID fields:
- Statistics to ads.
Join fb_ads_statistics with fb_ads_metadata using ad_id = id. - Ads to adsets.
Join fb_ads_metadata with fb_ads_dataset_metadata using adset_id = id. - Adsets to campaigns.
Join fb_ads_dataset_metadata with fb_ads_campaign_metadata using campaign_id = id. - Global account ID.
All tables can be filtered or joined by account_id.
Table name format
Standardized table naming conventions help you easily identify and manage your advertising datasets.
Tables are created with a unique timestamp to avoid naming conflicts:
- fb_ads_statistics_{unix_timestamp}
- fb_ads_campaign_metadata_{unix_timestamp}
- fb_ads_dataset_metadata_{unix_timestamp}
- fb_ads_metadata_{unix_timestamp}
Creating with template
Follow these steps in the Renta interface to set up data collection using the template:
- Select Pre-built templates as the integration type.
- Choose the Ad accounts you want to extract data from.
- Select the Facebook Ads Performance report from the templates dropdown.
The system will create 4 separate pipelines automatically.
Pipelines vs manual integration
Choosing between a template and a custom report depends on whether you need a quick start or a highly specialized data set.
| Feature | Template | Manual integration |
|---|---|---|
| Setup speed | One action for multiple tables | Separate setup for each table |
| Field selection | Predefined set of fields | Full custom selection |
| Scheduling | Shared schedule for all pipelines | Configured separately for each |
| Use case | Standard marketing reports | Custom data requirements |
Ready to get started?
Build your data pipeline today or get a personalized demo. Start free!
Need help?
Get expert support to ensure your project succeeds. We're here to help!
Feature requests?
Help shape our product! Share your ideas for new features and integrations.