Actions23
- Data Explorer API Actions
- Public API Actions
- Change User Access
- Clear AB Tasty Script
- Get Framework Checksum
- Get Modification
- Get Test
- Get Third Party Tools Link
- Get User
- Get Variation
- Give User Access
- List Events
- List Modifications
- List Tests
- List Tests Statistics
- List Third Party Tool Links
- List Users
- List Variations
- Pause Test
- Play Test
- Revoke User Access
- Update AB Tasty Script
- Universal Data Connector API Actions
Overview
This node integrates with the AB Tasty Public API to programmatically access and manage data related to experiments, campaigns, and account configurations. Specifically, the "List Tests Statistics" operation retrieves statistical data about tests associated with a given account.
Use cases include:
- Fetching aggregated performance metrics of A/B tests for reporting or analysis.
- Automating monitoring of test results within workflows.
- Integrating AB Tasty test statistics into dashboards or other systems.
For example, a marketing analyst could use this node to automatically pull test statistics daily and feed them into a BI tool for trend analysis.
Properties
| Name | Meaning |
|---|---|
| Account ID | The numeric identifier of the AB Tasty account whose test statistics you want to list. |
Output
The node outputs an array of JSON objects representing the statistics of tests for the specified account. The exact structure depends on the AB Tasty API response but typically includes aggregated metrics such as impressions, conversions, and other key performance indicators for each test.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential (Client ID and Client Secret) for authenticating with the AB Tasty API.
- The node obtains an OAuth2 access token using these credentials before making API requests.
- Network access to
https://api.abtasty.comis required.
Troubleshooting
- Missing Credentials: If the Client ID or Client Secret is not provided, the node will throw an error indicating missing credentials.
- Missing Account ID: This operation requires the Account ID property; omitting it will cause an error.
- Failed Token Retrieval: If the OAuth token cannot be obtained, the node will fail with an authentication error.
- API Errors: Any errors returned by the AB Tasty API are wrapped and reported with details. Check that the Account ID is correct and that the API credentials have sufficient permissions.
- Empty Response: If no statistics are available, the node may return a "204 No Content" status indication.