Dstillery Audience icon

Dstillery Audience

Get audience recommendations from Dstillery

Actions2

Overview

This node interacts with the Dstillery Audience API to retrieve audience-related data. Specifically, for the "Audience" resource and the "Get Taxonomy" operation, it fetches the full taxonomy path associated with a given audience name. This is useful when you want to understand or categorize an audience segment based on its taxonomy hierarchy as defined by Dstillery.

A practical example: If you have an audience name obtained from a previous recommendation step, you can use this node to get detailed taxonomy information about that audience, which can help in targeting or reporting.

Properties

Name Meaning
Audience Name The exact audience name (string) for which to retrieve the full taxonomy path. This must match the audience name returned by a prior "Get Recommendation" operation.

Output

The node outputs a JSON object containing:

  • audienceName: The input audience name.
  • taxonomy: A string representing the full taxonomy path of the audience.
  • fullpath: Same as taxonomy, the full taxonomy path text.

Example output JSON:

{
  "audienceName": "Example Audience",
  "taxonomy": "Some > Taxonomy > Path",
  "fullpath": "Some > Taxonomy > Path"
}

No binary data is output by this operation.

Dependencies

  • Requires access to the Dstillery Audience API.
  • Optionally uses credentials containing an API key and URLs for the API endpoints.
  • The node attempts to use configured credentials but can fallback to default URLs if credentials are not provided.
  • No additional environment variables are explicitly required beyond the API credentials.

Troubleshooting

  • Common issues:

    • Providing an incorrect or misspelled audience name will likely result in empty or missing taxonomy data.
    • Missing or invalid API credentials may cause authentication failures.
    • Network connectivity issues to the Dstillery API endpoints can cause request failures.

  • Error messages:

    • Errors thrown by the node typically include HTTP request failures or JSON-RPC errors from the API.
    • If the node fails and "Continue On Fail" is disabled, execution stops with an error message.
    • To resolve, verify the audience name correctness, ensure valid API credentials are set up, and check network connectivity.

Links and References

Discussion