Scenario
Create a system-defined report for LinkedIn Ads data. LinkedIn data is stored across these tables:| Table | Level |
|---|---|
| interaction_insight_ads_tracker | Account |
| interaction_insight_ads_campaigntracker | Campaign |
| interaction_insight_ads_adsettracker | AdSet |
| ads_adtracker | Ads |
Walkthrough
Add dictionary entries
Create metrics for each level in
report_data_dictionary:| metric | source_table | source_column | level |
|---|---|---|---|
| impressions | interaction_insight_ads_tracker | impressions | Account |
| clicks | interaction_insight_ads_tracker | clicks | Account |
| spend | interaction_insight_ads_tracker | cost | Account |
| clicks | interaction_insight_ads_campaigntracker | clicks | Campaign |
| spend | ads_adtracker | cost | Ads |
Create entries at every level even though the system report only uses Account level. Campaign, AdSet, and Ads level entries are used for custom reports and drill-down views.
Map metrics to source
Insert all dictionary IDs into Now the LinkedIn source only exposes LinkedIn metrics.
report_custom_fields:Verify
The report should now appear automatically in the UI. The reporting engine will:
- Read metrics from
report_data_dictionaryfor IDs 101, 102, 103 - Filter by source (LinkedIn Ads)
- Apply the template configuration (display order, labels)
- Build SQL queries against
interaction_insight_ads_tracker - Render the report
.png?fit=max&auto=format&n=Frm2GFbmok4D-yJA&q=85&s=93c3ebd47542af65d1cd06d8563a7f6e)