Actions65
- Posts Actions
- Company Pages Actions
- Get Company Page
- Get Company Pages
- Update Company Page
- Get Company Page Followers
- Get Company Page Analytics
- Get Company Page Posts
- Create Company Page Post
- Get Company Page Insights
- Get Company Page Engagement
- Get Company Page Demographics
- Get Company Page Content
- Get Company Page Events
- Create Company Page Event
- Get Company Page Jobs
- Get Company Page Lifecycle
- Advertising Actions
- Get Ad Accounts
- Get Ad Account
- Get Campaigns
- Get Campaign
- Create Campaign
- Update Campaign
- Delete Campaign
- Get Ad Sets
- Get Ad Set
- Create Ad Set
- Update Ad Set
- Delete Ad Set
- Get Ads
- Get Ad
- Create Ad
- Update Ad
- Delete Ad
- Get Audiences
- Get Audience
- Create Audience
- Update Audience
- Delete Audience
- Get Lead Gen Forms
- Get Lead Gen Form
- Create Lead Gen Form
- Update Lead Gen Form
- Delete Lead Gen Form
- Get Ad Analytics
- Get Campaign Analytics
- Get Ad Set Analytics
- Search Actions
Advertising → Get Ad Set Analytics
AI-generatedOverview
The "Get Ad Set Analytics" operation in the Advertising resource of this LinkedIn Enhanced node fetches detailed analytics data for a specific LinkedIn ad set within a company account. It allows users to retrieve performance metrics such as impressions, clicks, spend, conversions, and other engagement statistics over a specified date range.
This node is beneficial for marketers and advertisers who want to monitor and analyze the effectiveness of their LinkedIn advertising campaigns at the ad set level. For example, a user can track how an ad set performed last month in terms of reach and cost per click, enabling data-driven decisions to optimize future campaigns.
Properties
| Name | Meaning |
|---|---|
| Company ID | The LinkedIn Company ID associated with the ad set. |
| Ad Set ID | The identifier of the specific ad set to retrieve analytics for. |
| Start Date | The start date for the analytics data (inclusive). |
| End Date | The end date for the analytics data (inclusive). |
| Metrics | The list of metrics to include in the analytics response. Options include: |
| - Impressions, Clicks, Likes, Comments, Shares, Engagement, Reach, Followers, Views, CTR, CPC, CPM, Spend, Conversions, Leads | |
| Max Results | Maximum number of results to return (default 20, min 1, max 100). |
| Start Index | Index of the first result to return (default 0, min 0). |
Note: The "Ad Set ID" property is implied from the code parameter adSetId used in this operation but was not explicitly listed in the provided properties JSON. It is required to specify which ad set's analytics to fetch.
Output
The output is a JSON object containing the requested analytics data for the specified ad set. This includes the selected metrics aggregated over the given date range. The structure typically contains metric names as keys with their corresponding values, such as counts or monetary amounts.
No binary data output is indicated for this operation.
Example output snippet (conceptual):
{
"impressions": 12345,
"clicks": 678,
"spend": 150.75,
"conversions": 12
}
Dependencies
- Requires a valid API key credential for the external N8N Tools API service.
- Requires OAuth2 credentials for LinkedIn API access.
- The node internally uses helper classes to interact with LinkedIn Marketing API v2 endpoints.
- Proper configuration of these credentials and permissions is necessary to successfully fetch ad set analytics.
Troubleshooting
- Invalid subscription or API key error: If the node throws an error about invalid subscription or API key, verify that the API key credential is correctly configured and active.
- Missing or incorrect Company ID or Ad Set ID: Ensure that the correct LinkedIn Company ID and Ad Set ID are provided; otherwise, the API call will fail.
- Date range issues: The start date must be before or equal to the end date; invalid date ranges may cause errors or empty results.
- Metric selection: Selecting unsupported or misspelled metrics may lead to incomplete or failed responses.
- API rate limits: LinkedIn API enforces rate limits; excessive requests may result in throttling errors.