Overview
This node integrates with the TailURL API to retrieve analytics data for shortened URLs. It allows users to fetch detailed statistics about URL usage over specified time periods and at different granularities, such as hourly or daily data. This is useful for marketing teams, webmasters, or anyone who needs insights into how their shortened links are performing.
Common scenarios:
- Tracking click trends on a specific shortened URL over the last 30 days.
- Analyzing weekly or monthly user engagement with a link.
- Monitoring long-term performance of URLs with "All Time" analytics.
- Integrating URL analytics into automated reports or dashboards.
Example:
A marketing analyst wants to see how many clicks a campaign URL received in the past week, broken down by day. They configure this node with the URL ID, set the period to "7 Days," and granularity to "Day" to get the timeline data.
Properties
| Name | Meaning |
|---|---|
| URL ID | The unique identifier of the shortened URL to retrieve analytics for. |
| Period | The time range for which to fetch analytics data. Options: 1 Day, 7 Days, 30 Days, 90 Days, 1 Year, All Time. |
| Granularity | The level of detail for timeline analytics. Options: Hour, Day, Week, Month. |
Output
The node outputs JSON data containing the analytics information returned by the TailURL API for the specified URL. This typically includes metrics such as total clicks, timeline data points segmented by the chosen granularity, and possibly other engagement statistics.
The output structure is:
{
"success": true,
"data": {
// Analytics details like total clicks, timeline arrays, etc.
}
}
If the API call fails, the node throws an error with the failure message unless configured to continue on failure, in which case it outputs an error object per item.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the TailURL API.
- Network access to
https://tailurl.com/api/urls/{urlId}/analytics. - Proper configuration of the TailURL API credentials within n8n.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Providing an incorrect or non-existent URL ID will result in errors from the API.
- Using unsupported period or granularity values (though UI options prevent this).
- Network connectivity problems to the TailURL API endpoint.
Error messages:
"Failed to get analytics: <error message>"indicates the API returned an error; check URL ID validity and API key permissions.- Authentication errors usually mean the API key is invalid or expired.
- If the node returns an error object in output, verify the input parameters and credentials.
Resolution tips:
- Verify the API key is correctly set up and has necessary permissions.
- Confirm the URL ID exists and belongs to your account/team.
- Check network connectivity and firewall settings.
- Use the "Continue On Fail" option to handle errors gracefully in workflows.