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
This node integrates with the Adobe Analytics API to manage and update segments within an Adobe Analytics account. Specifically, the "Update Segment" operation allows users to modify existing segment definitions by sending updated data to the Adobe Analytics service.
Use cases include:
- Refining audience segments for more precise analysis.
- Updating segment criteria dynamically based on new business rules or data insights.
- Automating segment management as part of a larger analytics workflow.
For example, a marketing analyst could use this node to programmatically update a segment that targets users from a specific region or behavior pattern without manually editing it in the Adobe Analytics interface.
Properties
| Name | Meaning |
|---|---|
| Global Company ID | The unique identifier for the Adobe Analytics company (or global company) under which the segment exists. Required to scope the API request correctly. |
| Segment ID | The identifier of the segment to update. This is required to specify which segment will be modified. |
| Query Parameters | Optional parameters to refine or filter the request. Includes many options such as approved, classifiable, componentId, endDate, limit, locale, name, pagination, sortDirection (ASC/DESC), startDate, and many others to customize the request context. |
| Request Body | A JSON object representing the updated segment definition and properties. This contains the actual data to update the segment with, such as new rules, name changes, or other segment attributes. |
Output
The node outputs the response from the Adobe Analytics API after attempting to update the segment. The output is a JSON array where each element corresponds to the API response for each input item processed.
- If the update is successful, the output typically includes the updated segment details or confirmation data.
- If the response is empty or a string, it attempts to parse it as JSON; otherwise, it returns the raw text or a status code message like "204 No Content".
- No binary data output is produced by this node.
Dependencies
- Requires an Adobe Analytics API credential configured in n8n, including:
- Client ID
- Client Secret
- Scope
- The node obtains an OAuth access token via Adobe's IMS token endpoint before making API calls.
- Network access to Adobe Analytics API endpoints (
https://analytics.adobe.io/api/) and Adobe IMS token endpoint (https://ims-na1.adobelogin.com/ims/token/v3) is necessary.
Troubleshooting
- Missing Credentials: The node throws an error if the Adobe Analytics API credentials are not set or incomplete.
- Missing Required IDs: For updating a segment, the Segment ID must be provided; otherwise, an error is thrown.
- Access Token Retrieval Failure: If the OAuth token cannot be obtained, the node will fail with an appropriate error.
- API Errors: Any errors returned by the Adobe Analytics API are wrapped and reported with messages indicating the failure reason.
- Invalid JSON in Request Body: The request body must be valid JSON; malformed JSON will cause the request to fail.
- Network Issues: Connectivity problems to Adobe endpoints will result in request failures.
To resolve these issues:
- Ensure all required credentials and IDs are correctly configured.
- Validate the JSON structure of the request body.
- Check network connectivity and firewall settings.
- Review API permissions associated with the credentials.