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 Campaign Analytics
AI-generatedOverview
The "Get Campaign Analytics" operation within the Advertising resource of this LinkedIn Enhanced node fetches detailed analytics data for a specific LinkedIn advertising campaign. It allows users to retrieve various performance metrics over a defined date range, helping marketers and advertisers analyze the effectiveness of their campaigns.
This node is beneficial in scenarios such as:
- Monitoring key performance indicators (KPIs) like impressions, clicks, spend, and conversions for LinkedIn ad campaigns.
- Generating reports on campaign performance to optimize marketing strategies.
- Integrating LinkedIn campaign analytics into broader marketing dashboards or workflows.
For example, a user can specify a company ID, campaign ID, a start and end date, and select metrics like impressions, clicks, and spend to get a comprehensive view of how a campaign performed during that period.
Properties
| Name | Meaning |
|---|---|
| Company ID | The LinkedIn Company ID associated with the advertising account. |
| Campaign ID | The unique identifier of the LinkedIn advertising campaign to retrieve analytics for. |
| Start Date | The start date for the analytics data range (inclusive). |
| End Date | The end date for the analytics data range (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 | The index of the first result to return (default 0). |
Output
The output JSON contains the analytics data for the specified campaign, including the requested metrics aggregated over the given date range. The structure typically includes metric names as keys with their corresponding values, such as counts or monetary amounts.
Example output snippet (conceptual):
{
"impressions": 12345,
"clicks": 678,
"spend": 150.75,
"conversions": 12
}
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 for LinkedIn API access.
- The node internally uses helper classes to interact with LinkedIn Marketing API v2 endpoints.
- Proper configuration of these credentials in n8n is necessary for successful execution.
Troubleshooting
- Invalid Subscription or API Key: If the node throws errors related to invalid subscription or API key, verify that the API key credential is correctly configured and active.
- Permission Errors: Ensure the LinkedIn OAuth2 credentials have sufficient permissions to access advertising data.
- Date Range Issues: Providing an invalid or future date range may cause empty or error responses; ensure dates are valid and logical.
- Metric Selection: Requesting unsupported or misspelled metrics will likely cause errors; use only the provided metric options.
- Rate Limits: LinkedIn API rate limits may cause temporary failures; consider implementing retry logic or reducing request frequency.