LinkedIn Ad Analytics
LinkedIn Ad Analytics offers you information about the performance of your LinkedIn Ads.
Features
Feature Name | Supported | Notes |
---|---|---|
Capture deletes | ||
History mode | check | |
Custom data | ||
Data blocking | check | |
Column hashing | check | |
Re-sync | check | |
API configurable | check | API configuration |
Priority-first sync | check | |
Fivetran data models | check | |
Private networking | ||
Authorization via API | check |
Setup guide
Follow our step-by-step LinkedIn Ad Analytics setup guide to connect LinkedIn Ad Analytics with your destination using Fivetran connectors.
Sync overview
Rollback sync
A rollback sync is a sync that automatically runs once a day. Rollback syncs capture the changes that happen outside the incremental sync time frame.
Fivetran does not automatically capture the rollback window size. The rollback window depends on the maximum value between the View-Through Attribution Window and Post-Click Attribution Window settings. For example, we perform a one-day rollback sync if you set the View-Through Attribution Window and Post-Click Attribution Window to DAY_1
.
The supported values you can set for the View-Through Attribution Window and Post-Click Attribution Window are:
DAY_1
DAY_7
DAY_28
DAY_30
Schema information
This schema applies to all LinkedIn Ad Analytics connectors.
To zoom, open the ERD in a new window.
Sync notes
The CREATIVE_HISTORY
table stores data from various ad formats.
- The Follower, Job, Spotlight, and Text Ad creative types have corresponding names stored in dedicated fields:
- Follower corresponds to the
follower_headline
field. - Job corresponds to the
jobs_headline
field. - Spotlight corresponds to the
spotlight_headline
field. - Text Ad corresponds to the
text_ad_headline
field.
- Follower corresponds to the
- If the reference field contains a URN (Uniform Resource Name), the corresponding names are stored differently depending on the content type.
- Shares and UGC posts: Names are stored in the
Content
table'sarticle_title
andmedia_title
fields for articles and media posts, respectively. - In-mail content: The name is stored in the
in_mail_content_history
table'sname
field.
- Shares and UGC posts: Names are stored in the