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
Posts → Get Post Analytics
AI-generatedOverview
The "Get Post Analytics" operation in the Posts resource of this LinkedIn Enhanced node fetches detailed analytics data for a specific LinkedIn post. It allows users to retrieve various performance metrics over a defined date range, helping marketers and social media managers understand how their content is performing on LinkedIn.
This node is beneficial in scenarios such as:
- Measuring engagement and reach of individual posts.
- Tracking key performance indicators (KPIs) like impressions, clicks, likes, comments, shares, and more.
- Analyzing post effectiveness over time to optimize content strategy.
- Reporting and dashboarding LinkedIn post performance within automated workflows.
For example, a user can specify a LinkedIn post ID along with a start and end date, then select metrics like impressions, clicks, and likes to get a comprehensive view of that post's impact during the selected period.
Properties
| Name | Meaning |
|---|---|
| Post ID | The unique identifier of the LinkedIn post for which analytics are requested. |
| Start Date | The beginning date/time from which to collect analytics data. |
| End Date | The ending date/time up to which analytics data should be collected. |
| Metrics | The list of analytics metrics to include in the 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 (pagination control). Defaults to 20, max 100. |
| Start Index | The index of the first result to return (pagination offset). Defaults to 0. |
Output
The output JSON contains the analytics data for the specified post, structured according to the requested metrics and date range. Each item corresponds to the analytics snapshot or aggregated data points for the post.
The exact structure depends on the LinkedIn API response but typically includes fields representing counts or rates for each selected metric (e.g., impressions count, click count, engagement rate).
No binary data output is involved in this operation.
Dependencies
- Requires an active subscription and valid API key credential for the external N8N Tools API service.
- Requires OAuth2 credentials configured for LinkedIn API access.
- The node internally validates the API key via a POST request to the N8N Tools API before executing operations.
- The LinkedIn Marketing API v2 is used under the hood to fetch post analytics.
Troubleshooting
- Invalid Subscription or API Key: If the node throws an error about invalid subscription or API key, verify that your API key credential is correct and active.
- Permission Errors: Ensure the LinkedIn OAuth2 credentials have sufficient permissions to access post analytics.
- Date Range Issues: Providing an invalid or future date range may cause errors or empty results; ensure start and end dates are valid and logical.
- Metric Selection: Requesting unsupported or misspelled metrics will likely cause errors; use only the provided metric options.
- Pagination Parameters: Using out-of-range values for
maxResultsorstartIndexmay lead to unexpected results or errors; keep within allowed limits.