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 platform's Universal Data Connector API to list visitor segments associated with a specific visitor ID within an account. It is useful for retrieving real-time audience segment data that can be used for personalization, targeted marketing, or experimentation based on visitor behavior and attributes.
A practical example use case is when you want to fetch all segments a particular visitor belongs to in order to tailor content or offers dynamically on your website or app.
Properties
| Name | Meaning |
|---|---|
| Account ID | The numeric identifier of the AB Tasty account from which to retrieve visitor segments. |
| Visitor ID | The unique string identifier of the visitor whose segments you want to list. |
Output
The node outputs a JSON array where each item corresponds to the response from the AB Tasty API listing visitor segments for the specified visitor. The structure depends on the API response but typically includes details about each segment the visitor belongs to.
If the API returns no content, the output will indicate a "204 No Content" status.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential (Client ID and Client Secret) for AB Tasty API authentication.
- The node performs OAuth2 client credentials flow to obtain an access token before making API requests.
- Network access to
https://api-data-connector.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 Required Parameters: The node requires both Account ID and Visitor ID for this operation. Omitting either will cause an error.
- Failed Token Retrieval: If the OAuth token cannot be obtained, the node will fail with an appropriate error message.
- API Errors: Any errors returned by the AB Tasty API will be wrapped and reported as node API errors with details.
- Empty Response: A "204 No Content" response means no segments were found for the visitor; verify the visitor ID and account ID are correct.