LinkedIn Ads
LinkedIn Ads exposes one statistics report and three metadata snapshots. The statistics report carries daily figures for every ad: impressions, clicks, cost, leads, conversions, engagement, video, and carousel metrics. The metadata reports return the current attributes of ads, campaigns, and the connected ad account.
Renta exports any of the four to your data warehouse. A pre-built template loads the statistics and metadata tables together.
Authentication
Renta uses OAuth to authenticate with LinkedIn. You will be redirected to LinkedIn to grant Renta limited access to your LinkedIn Ads account.
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 your LinkedIn account settings at any time.
Connect LinkedIn Ads source
Follow these steps to add LinkedIn Ads as a source in Renta using OAuth authentication.
- Navigate to the Connections > Catalog section in the left sidebar.
- Open the Advertising category and click the LinkedIn Ads card.

Click Log in to your LinkedIn Ads account. You will be redirected to LinkedIn to sign in and confirm the permissions Renta requests. If the browser already holds an authorized LinkedIn session, the confirmation resolves right away and you return to Renta.

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. The connected account carries the name of your LinkedIn profile.
Click Save to finish.
If your LinkedIn 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.

The new source appears in the Sources list with the Active status. You can now use it in pipelines.

Create a pipeline
Once the source is connected, create a pipeline to sync your LinkedIn Ads data into your destination.
Create a LinkedIn Ads pipeline
Link your LinkedIn Ads source to a destination and configure the pipeline.
In the left sidebar, click New pipeline. On the Source step, select LinkedIn Ads under Already connected and click Next step.

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

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

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

Pipeline configuration
On the final step, choose which LinkedIn Ads data to export and how Renta loads it.
Integration type
Choose how to configure the pipeline: assemble the report yourself or start from a template.

| Integration type | Description |
|---|---|
| Custom report | You choose the report type, the fields, and the load settings yourself. The sections below describe this path. |
| Pre-built templates | A predefined set of pipelines with a fixed field selection. You pick only the ad account and the template. |
Renta offers one template, LinkedIn Ads Performance report. It creates three pipelines at once: a daily Ad statistics report with date, Creative ID, and 19 cost, conversion, and engagement metrics, plus Campaign metadata report and Ad metadata report snapshots.
The statistics pipeline is created with the overwrite period set to Last 7 days. The destination tables get the la_ prefix.
Report configuration
Pick the ad account and the report type. The report type defines the set of fields available in the Parameters picker.

-
Ad accounts The dropdown lists every ad account available to the authorized LinkedIn profile. The Viewer role on the account is enough for exporting statistics. A pipeline exports data for one account. To load several accounts, create a pipeline for each.
-
Report Types Select the type of report to export.
Report type Description Ad statistics report Daily performance statistics for each ad: impressions, clicks, cost, conversions, leads, engagement, video, carousel, and document metrics. Ad metadata report Current attributes of each ad: name, campaign and account identifiers, review status, serving status, creation and modification dates. Campaign metadata report Current attributes of each campaign: name, status, objective, format, cost type, budget, schedule, and feature flags. Account metadata report Current attributes of the connected ad account: name, identifier, type, status, and currency.
The Ad statistics report is always grouped by ad and day. To get campaign or account totals, aggregate the exported rows in the warehouse and join the metadata reports by the campaign and account identifiers.
Parameters
Select the fields to include in the destination table. Your dataset schema is defined by the parameters you choose here.

Every row in the picker shows the field name with the destination column name below it: actionClicks becomes the action_clicks column.
Check the fields to export, use the search to find a field by name, and review the choice on the Selected tab. The Selected Parameters list below the picker lets you remove a field.
The Ad statistics report carries cost in two fields: cost_in_local_currency (the currency of the ad account) and cost_in_usd.
Identifiers such as Creative ID and Campaign ID are exported as plain numbers, so the statistics table joins the metadata tables directly.
Include the date parameter in the Ad statistics report. With it, the destination table is partitioned by the date column and Renta loads data incrementally. It also enables the Overwrite Period setting, which appears below the date range. Without it, Renta reloads the whole date range on every run.
The LinkedIn reporting API returns at most 20 fields per request, so the Ad statistics report can include at most 19 metric fields besides date and Creative ID. Select All picks all 71 fields, so pipeline creation fails with the error: Too many fields requested. Maximum possible fields to request: 20. Renta validates the selection with a test request when you create the pipeline, so you see the error immediately rather than on the first run.
Table name
Name the pipeline and the destination table.

- Integration name.
The name of the pipeline. It is used exclusively in the Renta interface. - Table name.
The destination table name. You can keep the auto-generated name or enter your own.
Date range
Set the historical period to load. By default, Date start is the first day of the current month and Date end is Today.

- Date start.
The first date of the extraction period. - Date end.
The last date of the extraction period. You can pick a fixed date or a relative option such as Today.
Overwrite period
The overwrite period defines how many recent days Renta reloads on every run. The setting appears once the date parameter is selected.

On each run, Renta re-fetches the data starting from the date of the last successful run minus the overwrite period. The affected days are deleted from the destination table and inserted again, while older data stays untouched.
The options range from Without overwrite data to Overwrite all data. The default is Last 3 days.
LinkedIn attributes conversions to clicks and views retroactively, within attribution windows of up to 30 days, so conversion figures for recent days keep changing after the fact. Set the overwrite period to at least Last 7 days, or Last 30 days to cover the longest attribution window.
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.
The new pipeline appears in the Pipelines section under the ETL tab, where you can track its runs, progress, and the destination table name.

Limitations
The LinkedIn reporting API sets boundaries that apply to every pipeline built on this source.
| Limitation | Description |
|---|---|
| Fields per report | The API returns at most 20 fields per request. In practice the Ad statistics report fits date, Creative ID, and up to 19 metric fields. |
| Daily statistics depth | LinkedIn retains day-level statistics for roughly the last six months. An earlier Date start returns nothing for the part of the range that falls outside that window. |
| Statistics grain | The Ad statistics report is always grouped by ad with daily granularity. Campaign and account totals are aggregated in the warehouse. |
| No history in metadata reports | Ad metadata report, Campaign metadata report, and Account metadata report return the current state of the objects, without change history. |
Sync strategy
The synchronization strategy depends on the report type and on whether the report includes the date parameter.
| Strategy | Supported report types | Description |
|---|---|---|
| Incremental | Ad statistics report (with the date parameter selected) | Each row carries its date, and the destination table is partitioned by the date column. On every run Renta requests the window from the last successful run minus the overwrite period: the affected daily partitions are deleted and inserted again, and older partitions stay untouched. |
| Full reload | Ad statistics report (without the date parameter) | The table has no date column to partition by, so Renta requests the statistics for the whole configured date range and replaces the dataset on every run. |
| Full reload | Ad metadata report, Campaign metadata report, Account metadata report | These reports return the current state of ads, campaigns, and the account and have no date field, so Renta reloads the entire dataset on every run. |
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.