Actions87
- Users Actions
- Shopping & Catalogs Actions
- Advertising & Campaigns Actions
- Advanced Analytics Actions
- Engagement Features Actions
- Business Tools Actions
- Search & Discovery Actions
- Pins Actions
- Boards Actions
Overview
The "Get Pin Analytics" operation in this Pinterest Enhanced node retrieves detailed analytics data for a specific Pinterest pin over a defined date range. This operation is useful for marketers, content creators, and social media managers who want to analyze the performance of individual pins in terms of impressions, clicks, saves, and other engagement metrics.
Typical use cases include:
- Measuring the effectiveness of a pin in driving traffic or engagement.
- Comparing different pins' performance to optimize content strategy.
- Tracking how a pin performs across different device types or ad accounts.
- Gaining insights into user interactions with a pin over time.
For example, a marketer could use this node to fetch impression and save counts for a promotional pin during a campaign period to evaluate its reach and user interest.
Properties
| Name | Meaning |
|---|---|
| Pin ID | The unique identifier of the pin for which analytics are requested. |
| Start Date | The start date (ISO 8601 format) for the analytics data range. |
| End Date | The end date (ISO 8601 format) for the analytics data range. |
| Metric Types | The types of metrics to include in the analytics response. Options include: Impression, Clickthrough, Click, Save, Hide, Comment, Like, Reaction, Engagement. Default includes Impression, Click, and Save. |
| App Types | The types of applications/devices to include in the analytics. Options are All, Mobile, Desktop, Tablet. Default is All. |
| Split Field | The field by which to split the analytics data. Options are No Split, App Type, Owned Content, Pin Format. Default is No Split. |
| Ad Account ID | Optional advertising account ID to filter analytics related to a specific ad account. |
| Include Private Metrics | Boolean flag to include private metrics in the response; requires elevated access permissions. |
| Custom Fields | Comma-separated list of additional custom fields to include in the analytics response. |
Output
The output JSON contains the analytics data for the specified pin according to the selected parameters. It typically includes metric values such as impressions, clicks, saves, and other engagement statistics aggregated over the specified date range. If a split field is used, the data will be segmented accordingly (e.g., by app type).
The structure generally follows the API's analytics response format, providing detailed insights per metric and optionally broken down by the chosen split field.
This node does not output binary data.
Dependencies
- Requires an active subscription and valid API key credential for the external "N8N Tools API" service that acts as a proxy or enhancer for Pinterest API v5.
- Requires Pinterest OAuth2 authentication credentials configured in n8n to access Pinterest data.
- The node internally uses multiple API wrapper classes for Pinterest features but specifically calls the Pinterest API wrapper for pin analytics.
- Proper permissions and elevated access may be required to retrieve private metrics.
Troubleshooting
- Invalid Subscription or API Key: If the node throws an error about invalid subscription or API key, verify that the API key credential is correctly set up and active.
- Permission Denied for Private Metrics: Attempting to include private metrics without proper access will result in errors. Ensure your Pinterest account has the necessary elevated permissions.
- Date Range Errors: Providing invalid or improperly formatted dates for start or end date can cause failures. Use ISO 8601 format and ensure the end date is after the start date.
- Pin Not Found: If the provided Pin ID is incorrect or the pin no longer exists, the API will return an error. Double-check the Pin ID.
- API Rate Limits: Frequent requests might hit rate limits imposed by Pinterest or the proxy API. Implement retry logic or reduce request frequency if needed.