Sync data from Facebook Ads to your warehouse destination via RudderStack.
Facebook Ads is an online advertising platform that lets you create and run cross-device marketing campaigns and track their performance with easy to read reports.
This document guides you in setting up Facebook Ads as a source in RudderStack. Once configured, RudderStack automatically ingests your specified Facebook Ads data and routes it to your data warehouse.
Go to Sources > New source > Cloud Extract and select Facebook Ads from the list.
Assign a name to your source and click Continue.
Click Connect with Facebook Ads and grant RudderStack the necessary permissions to access your Facebook Ads data.
Your Facebook Ads account and the related details will then automatically appear under Choose an account.
In the Source Settings, configure the following settings:
Page: Enter the name of the Facebook page from where you want to ingest the Ads data.
Historical data: Specify the timeframe for which RudderStack should fetch the historical data during the first sync.
Attribution window: Specify the attribution window, that is, the number of days between a person viewing/clicking your ad and subsequently taking an action. Facebook measures the ad actions based on the clicks and views of your ad.
RudderStack will not sync the data older than the selected timeframe for the historical data.
The following settings specify how RudderStack sends the ingested data from Facebook Ads to the warehouse destination:
Table prefix: RudderStack uses this prefix to create a table in your data warehouse and loads all your Facebook Ads data into it.
Note that RudderStack does not add special characters like - or _ to the prefix by default. Hence, you need to specify it while setting the prefix.
Schedule Settings: RudderStack gives you three options to ingest the data from Facebook Ads:
Basic: Runs the syncs at the specified time interval.
CRON: Runs the syncs based on the user-defined CRON expression.
Manual: You are required to run the syncs manually.
For more information on the schedule types, refer to the Common Settings guide.
Selecting the data to import
Choose the Facebook Ads data that you wish to ingest via RudderStack. You can either select all data or choose specific Facebook Ads data attributes as per your requirement.
Facebook Ads is now configured as a source. RudderStack will start ingesting data from Facebook Ads as per your specified schedule and frequency.
You can further connect this source to your data warehouse by clicking on Add Destination:
Use the Use Existing Destination option if you have an already-configured data warehouse destination in RudderStack. To configure a data warehouse destination from scratch, select the Create New Destination button.
Is it possible to have multiple Cloud Extract sources writing to the same schema?
Yes, it is.
RudderStack associates a table prefix for every Cloud Extract source writing to a warehouse schema. This way, multiple Cloud Extract sources can write to the same schema with different table prefixes.
What Facebook Ads data does RudderStack import?
This table contains insights, aggregated for the whole account. Insights include total impressions, CPP, CPC, Reach, and CPM.
This table holds information about your campaigns. The columns of this table include: name, objective, account_id, andstatus.
This tables has information about your Ad Sets. The columns of this table are: bid_amount,updated_time,campaign_id,daily_budget,lifetime_budget, and pacing_type.
This table contains information about your Facebook Ads.
This table contains the creative content for your Facebook Ads account that you can use in your ads.
How can I avoid sync errors due to rate limits?
To avoid sync errors due to rate limits, set the Page Size of Requests setting to 500 from the default value of 50. This allows RudderStack to make fewer calls to the Facebook API. Note that the maximum value for this setting is 1000.
How does RudderStack count the events for Cloud Extract sources?
RudderStack counts the number of records returned by the source APIs when queried during each sync. It considers each record as an event.
How does RudderStack set the table name for the data sent via Cloud Extract sources?
RudderStack sets the table name for the resource you are syncing to the warehouse by adding rudder_ to the Table prefix you set while configuring your Cloud Extract source in the dashboard.
For example, if you set test_ as the Table prefix in the dashboard, RudderStack sets the table name as test_rudder_<resource_name>, where <resource_name> is the name of the resource you are syncing (for example, contacts, messages, etc.).
Note that RudderStack does not add the character _ to the prefix by default. Hence, you need to specify it while setting the prefix.
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
for the working of basic functionalities of the website. We also use third-party cookies that
analyze and understand how you use this website. These cookies will be stored in your browser
consent. You also have the option to opt-out of these cookies. But opting out of some of these
have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.