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 run various operations related to analytics data management. Specifically, for the Report resource and the Run Report operation, it allows users to execute detailed reports based on customizable query parameters and request bodies. This is useful for extracting analytical insights such as traffic metrics, user behavior, and event tracking from Adobe Analytics.
Typical use cases include:
- Running custom reports filtered by date ranges, dimensions, or segments.
- Fetching real-time or historical report data for dashboards or automated workflows.
- Applying complex filters and pagination to retrieve specific slices of analytics data.
For example, a marketing analyst could use this node to automatically generate daily reports on page views segmented by device type, or a product manager might extract conversion metrics filtered by campaign tags.
Properties
| Name | Meaning |
|---|---|
| Global Company ID | The unique identifier for the company in Adobe Analytics context; required to specify which company's data to access. |
| Query Parameters | A collection of optional filters and settings to customize the report query. Options include: - Approved (boolean): Include only approved calculated metrics. - Classifiable (boolean): Include classifiable dimensions. - Component ID(s) (string): Filter by component IDs. - Component Type (string): Specify component type. - Curated RSID (string): Include curated item status. - Dimension (string): Dimension to run the report against (e.g., "variables/page"). - End Date (string): End date for the report period. - Event/Event Type (string): Filter logs by event description or type. - Expansion (string): Add extra metadata. - Favorite (boolean): Include favorite calculated metrics. - Filter by Date Range/IDs/Modified After/Published Segments (string): Various filtering options. - Include Type (string): Include additional annotations ("all" or "shared"). - IP/Login/User ID (string/number): Filter logs by user or IP. - Limit (number): Max number of results. - Locale (string): Locale setting. - Lookup None Values (boolean): Include none values. - Migrating (boolean): Include migration functions. - Name (string): Filter segments by name. - New Definition (boolean): Use new JSON definition. - Owner ID (string): Filter projects by owner. - Page (number): Pagination page number. - Pagination (boolean): Enable pagination. - Reportable (boolean): Include only valid report dimensions. - RSID (string): Report suite ID. - Search And/Or/Not/Phrase/Clause (string): Search terms. - Segment Filter (string): Filter segments. - Segmentable (boolean): Include only segment-valid dimensions. - Sort Direction (ASC/DESC): Sorting order. - Sort Property (string): Property to sort by. - Start Date (string): Start date for report period. - Tag Names (string): Filter segments by tags. - To Be Used In RSID (string): Target report suite. - Use Cache (boolean): Use caching for faster requests. |
| Request Body | JSON object representing the full request body for the report API call. Allows sending complex report definitions beyond simple query parameters. |
Output
The node outputs the JSON response returned by the Adobe Analytics API for the executed report. This typically includes:
- Report data structured according to the requested dimensions and metrics.
- Metadata about the report such as totals, pagination info, and any applied filters.
- If the response is empty or no content is returned, a status code message like
"204 No Content"is output.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for Adobe Analytics with client ID, client secret, and scope configured.
- The node performs OAuth2 client credentials flow to obtain an access token before making API calls.
- Network access to
https://ims-na1.adobelogin.comfor authentication andhttps://analytics.adobe.io/apifor API requests is necessary.
Troubleshooting
- Missing Credentials Error: If the API credentials are not set or invalid, the node will throw an error indicating missing credentials. Ensure that the Adobe Analytics API credentials are properly configured in n8n.
- Access Token Retrieval Failure: Failure to get an access token from Adobe's IMS endpoint will cause the node to error out. Check client ID, secret, and network connectivity.
- Required Parameter Missing: For some operations, required IDs (like Global Company ID) must be provided. Omitting these will result in errors specifying which parameter is missing.
- API Errors: Any HTTP or API errors from Adobe Analytics are caught and rethrown with descriptive messages. Review the error message and stack trace for details.
- Invalid JSON in Request Body: The request body must be valid JSON. Malformed JSON will cause parsing errors.
- Rate Limits or Quotas: If Adobe Analytics API rate limits are exceeded, requests may fail. Implement retry logic or reduce request frequency if needed.