Actions57
- Annotation Actions
- Calculated Metric Actions
- Component Meta Data Actions
- Add Tags
- Delete Multiple Tags
- Delete One Tag
- Delete Shared Component
- Get Shared Component
- Get Tag
- List Shared Components by the User
- List Shared Components to the User
- List Tag Names
- List Tags
- Save Tags
- Search Shared Components
- Search Tags for Multiple Components
- Search Tags for One Component
- Share Component with Multiple User
- Share Component with One User
- Date Range Actions
- Dimension Actions
- Metric Actions
- Project Actions
- Report Actions
- Segment Actions
- Usage Log Actions
- User Actions
Overview
The node integrates with the Adobe Analytics API to perform various operations related to analytics data management. Specifically, for the Segment resource and the Validate Segment operation, it allows users to validate segment definitions before creating or updating them in Adobe Analytics. This validation ensures that the segment's JSON definition is correct and complies with Adobe's requirements.
This node is beneficial when automating workflows that involve managing Adobe Analytics segments, such as validating new or updated segment definitions programmatically to prevent errors during deployment.
Practical example:
A marketing analyst creates a new customer segment definition in JSON format and wants to ensure it is valid before applying it in Adobe Analytics. Using this node, they can automate the validation step within an n8n workflow, catching any issues early.
Properties
| Name | Meaning |
|---|---|
| Global Company ID | The unique identifier of the Adobe Analytics company (or global company) under which the segment exists. Required for all operations except user discovery. |
| Query Parameters | A collection of optional parameters to filter or modify the request. For segment validation, these are generally not required but available for other segment-related operations. |
| Request Body | The JSON object representing the segment definition to be validated. This should contain the segment's structure according to Adobe Analytics API specifications. |
Details on relevant properties for Validate Segment operation:
- Global Company ID: Identifies the company context for the API call.
- Request Body: Contains the segment definition JSON to be validated.
- Query Parameters: Not typically used for validation but available for other segment operations.
Output
The output is a JSON array where each item corresponds to the response from the Adobe Analytics API for the validation request. The response typically includes:
- Validation success status.
- Any error messages or warnings about the segment definition.
- Additional metadata returned by the API regarding the segment's validity.
If the API returns no content, the node outputs a status code indicating "204 No Content".
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for Adobe Analytics with appropriate permissions.
- Needs valid Adobe Analytics API credentials including client ID, client secret, and scope.
- The node makes HTTP requests to Adobe's OAuth token endpoint to obtain an access token and then calls the Adobe Analytics API endpoints.
- Network connectivity to
https://ims-na1.adobelogin.comandhttps://analytics.adobe.iois necessary.
Troubleshooting
- Missing Credentials Error: If the node throws an error about missing credentials, ensure that the Adobe Analytics API credentials are properly configured in n8n.
- Failed to Retrieve Access Token: Indicates issues with client ID, client secret, or scope. Verify these values and their permissions.
- Required Parameter Missing: For segment validation, if the segment definition JSON (
requestBody) is empty or malformed, the API will reject the request. Ensure the JSON is correctly formatted. - API Errors: The node surfaces API errors with messages prefixed by "Error calling Adobe Analytics API". Check the message for details such as invalid JSON, unauthorized access, or rate limits.
- Network Issues: Connectivity problems to Adobe endpoints will cause failures. Confirm network access and proxy settings if applicable.