Adobe Analytics icon

Adobe Analytics

Use the Adobe Analytics API
Join our community

Actions57

Overview

This node integrates with the Adobe Analytics API to perform various operations on Adobe Analytics resources. Specifically, for the Component Meta Data resource and the Delete One Tag operation, it removes a tag identified by its Tag ID from the Adobe Analytics system, including disassociating that tag from any components it was linked to.

This operation is useful when you want to clean up or manage tags in your Adobe Analytics environment, for example, removing obsolete or incorrect tags that are no longer needed or relevant. It helps maintain accurate metadata and tagging structure within your analytics setup.

Practical example:

  • You have a tag used to categorize certain metrics or segments but it is outdated or incorrectly applied. Using this node operation, you can delete that tag and all its associations, ensuring your metadata remains clean and relevant.

Properties

Name Meaning
Global Company ID The unique identifier of the company in Adobe Analytics under which the tag exists. This is required to scope the API request correctly.
Tag ID The unique identifier of the tag to be deleted. This is mandatory for the Delete One Tag operation to specify which tag should be removed.
Query Parameters A collection of optional parameters that can modify the behavior of the request. These include filters and flags such as approved, classifiable, componentId, limit, locale, sortDirection, startDate, etc. They provide fine control over the query but are generally not required for deleting a tag.

The full list of possible query parameters includes booleans, strings, numbers, and options to filter or paginate results, but for the Delete One Tag operation, these are typically unused or optional.

Output

The output of this operation is the JSON response returned by the Adobe Analytics API after attempting to delete the specified tag. The response may vary depending on success or failure:

  • On successful deletion, the API might return an empty response or a confirmation object.
  • If the tag does not exist or cannot be deleted, an error will be thrown (see Troubleshooting).

The node returns the API response as JSON in the json output field. There is no binary data output for this operation.

Dependencies

  • Requires an API key credential for Adobe Analytics with appropriate permissions.
  • The node authenticates using OAuth client credentials flow to obtain an access token before making API calls.
  • Network access to Adobe Analytics API endpoints (https://analytics.adobe.io/api/) is required.
  • No additional external dependencies beyond the Adobe Analytics API and n8n's HTTP request helper.

Troubleshooting

  • Missing Credentials Error: If the Adobe Analytics API credentials are not set or invalid, the node will throw an error indicating missing credentials. Ensure you configure valid API credentials in n8n.
  • Tag ID Required: If the Tag ID property is empty when running the Delete One Tag operation, the node throws an error stating that the Tag ID is required. Provide a valid Tag ID.
  • Access Token Retrieval Failure: If the node fails to retrieve an access token from Adobe IMS, it will throw an error. Check your client ID, client secret, and scope settings.
  • API Errors: Any errors returned by the Adobe Analytics API (e.g., tag not found, insufficient permissions) will be surfaced as node errors with descriptive messages. Verify the tag exists and your API user has rights to delete tags.
  • HTTP Method Mismatch: The node uses the DELETE HTTP method for this operation. If the API endpoint changes or is unavailable, requests may fail.

Links and References

This summary covers the static analysis of the node’s execute logic for the "Component Meta Data" resource and "Delete One Tag" operation, focusing on input properties, output, dependencies, and common troubleshooting points.

Discussion