When do I need to re-authorize?

Only when your Facebook authorization changes — for example, after you change your Facebook account password or revoke a permission. Open the source and click **Re-authorize**. The connection refreshes in place, so every pipeline built on that source keeps running.

What access does Renta request?

Renta requests read access to the Facebook Pages you manage and the leads submitted through their lead forms. You approve this during the Facebook authorization step and can revoke it at any time. Your credentials are encrypted in transit and at rest and never stored in Renta's application database.

How are custom form questions stored?

Every answer from the lead form is kept in the **field_data** array as a name and value pair. Email, phone, and full name are also promoted to their own **email**, **phone**, and **name** columns when the form collects them. Any other custom question stays inside **field_data**.

Can I sync one lead form or all of them?

Both. In **Lead forms**, choose **All lead forms** to export leads from every form on the selected page, or pick a single form to export only its leads. Use one pipeline per scope.

What is the difference between Personal pages and Business Manager pages?

It reflects how the page is managed. Choose **Personal pages** if the page is run from an individual Facebook account, or **Business Manager pages** if it is owned by a Facebook Business Manager. For Business Manager pages you also pick the Business Manager account that owns the page.

Facebook Lead Ads

Capture the leads people submit through your Facebook lead-gen forms and load them directly into your data warehouse with Renta. Centralize form responses, contact details, and the ad, ad set, and campaign behind each lead for faster follow-up, lead scoring, and attribution — without writing a single line of code.

Authentication

Renta uses OAuth to authenticate with Facebook. This ensures secure access without sharing your password directly. You will be redirected to Facebook to grant Renta limited access to your Pages and their lead forms.

Your credentials are encrypted in transit and at rest, and never stored in Renta's application database. You stay in control and can revoke access from Facebook at any time.

Connect Facebook Lead Ads source

Follow these steps to add Facebook Lead Ads as a source in Renta using OAuth authentication.

Go to the SourcesStep 1

Navigate to the Connections > Sources section in the left sidebar.
Click + Add source in the top-right corner.

Renta Sources list with the Add source button

Select Facebook Lead AdsStep 2

Open the Advertising category and click the Facebook Lead Ads card to open the connection form.

Facebook Lead Ads card in the Advertising category of the Renta catalog

Authorize connectionStep 3

Click Log in to your Facebook Lead Ads account. You will be redirected to Facebook to grant Renta access to your Pages and their lead forms. After you approve access, you are redirected back to Renta.

Authorize Facebook Lead Ads connection page in Renta

Name the connection and saveStep 4

Finish the setup:

Source name.
Specify a name for this data source. This is used exclusively in the Renta interface.
Access granted.
Verify that the account is connected successfully.

Click Save to finish. Your new source will now appear in the sources list.

If your Facebook authorization later changes — for example, after a password change — click Re-authorize on this source. The connection refreshes in place and every pipeline built on it keeps running.

Set up your Facebook Lead Ads connection with source name and access granted

Create a pipeline

Once the source is connected, create a pipeline to sync your leads into your destination.

Create a Facebook Lead Ads pipeline

Link your Facebook Lead Ads source to a destination and configure the pipeline.

Start a new pipelineStep 1

In the left sidebar, click New pipeline.

Select Facebook Lead Ads as the sourceStep 2

On the Source step, select Facebook Lead Ads under Already connected and click Next step.

Select a source step with Facebook Lead Ads under Already connected

Select your Facebook Lead Ads connectionStep 3

Choose the Facebook Lead Ads connection you created earlier and click Next step.

Select a destinationStep 4

On the Destination step, select your destination (for example, Google BigQuery) and click Next step.

Select a destination step with Google BigQuery

Select the destination connectionStep 5

Choose the destination connection you want to load data into and click Next step.

Select your Google BigQuery connection step

Pipeline configuration

On the final step, choose which leads to export and how Renta loads them.

Lead source

Point the pipeline at the page and forms you want to sync.

Facebook Lead Ads page type, Business Manager, and lead form selection

Facebook Page types Choose how the page is managed.

Page type Description
Personal pages Pages run from an individual Facebook account.
Business Manager pages Pages owned by a Facebook Business Manager.
Business Manager accounts For Business Manager pages, select the Business Manager account that owns the page.
Business Manager pages Select the page you want to pull leads from.
Lead forms Choose All lead forms to export leads from every form on the page, or select a single form to export only its leads.

Page type	Description
Personal pages	Pages run from an individual Facebook account.
Business Manager pages	Pages owned by a Facebook Business Manager.

Parameters

Select the lead fields to include in your destination table. Your dataset schema is defined by the parameters you choose here.

Field	Description
Lead ID	Unique identifier for each lead.
Form ID	Identifier of the lead form that produced the lead.
Created Time	Timestamp when the lead was submitted.
Created Date	Submission date, derived from Created Time and used for partitioning.
Platform	Platform where the lead was collected, such as Facebook or Instagram.
Campaign ID	Identifier of the campaign behind the lead.
Campaign Name	Name of the campaign.
Adset ID	Identifier of the ad set behind the lead.
Adset Name	Name of the ad set.
Ad ID	Identifier of the ad behind the lead.
Ad Name	Name of the ad.
Email	Email address, promoted from the form answers when present.
Phone	Phone number, promoted from the form answers when present.
Name	Full name, promoted from the form answers when present.
Field Data	All form answers as an array of name and value pairs.

Output table and date range

Set how the data lands in your destination and how far back to pull.

Facebook Lead Ads integration name, table name, date range, and overwrite period

Integration name.
A display name for this integration. Edit it to match your preferences.
Table name.
The destination table name. Renta suggests a default such as facebook_lead_ads_{id}, and you can enter your own.
Date range.
Specify the historical period to pull. Renta filters leads by their submission time, so the sync covers leads created within the selected window. Leave the end date as Today to keep collecting new leads.
Overwrite period.
Choose the lookback window that is reloaded on every run. Renta deletes and re-inserts leads in that window so late edits are captured. The default is Last 1 day.

Schedule

Choose how often the pipeline runs.

Schedule type	Description
Manual	The pipeline runs only when triggered manually through the interface or via API.
Daily	The pipeline runs once a day at the specified update time.
Interval	The pipeline runs at specified time intervals.
Cron Expression	The pipeline runs on a schedule defined by a cron expression.

For Daily schedules, set the Update time — the exact time each run starts — then click Create pipeline.

Renta also supports API triggers and integration with external orchestrators such as Apache Airflow, Dagster, and Prefect. See the full scheduling documentation for details.

Sync strategy

Renta keeps your leads table up to date with an incremental load and a configurable lookback window.

On each run, Renta appends leads submitted since the previous sync, filtering by submission time, and reloads the Overwrite period window (by default the last day) so late edits are captured. Tables are partitioned by created_date, so only the affected days are rewritten.

To rebuild the whole table from scratch, re-run the pipeline with a full refresh — you do not need to change the Overwrite period.

Frequently asked questions

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.