Dstillery Audience

Overview

The Dstillery Audience node provides audience recommendations based on a marketing brief. It leverages an external API to analyze the input marketing brief and returns relevant audience segments that match the campaign goals, product description, or tone provided. This node is useful for marketers and advertisers who want to identify target audiences dynamically by describing their campaign in natural language.

A practical example: A user inputs a marketing brief describing a new eco-friendly product launch with a focus on sustainability and young adults. The node returns a list of audience segments interested in environmental issues and related topics, helping tailor ad targeting strategies.

Properties

• Marketing Brief: This is the core input where you describe your campaign or product in free text.
• Interest Types: Allows specifying which categories of interests to consider when generating recommendations. Defaults to "110,112,250" but can be customized.

Output

The node outputs JSON data with the following structure:

{
  "audiences": ["Audience Name 1", "Audience Name 2", "..."],
  "brief": "The original marketing brief text",
  "interestTypes": "Comma-separated interest type IDs used"
}

• audiences: An array of audience segment names recommended based on the marketing brief.
• brief: Echoes back the marketing brief input for reference.
• interestTypes: Echoes back the interest types used in the query.

No binary data output is produced by this operation.

Dependencies

• Requires access to the Dstillery Audience API endpoint (https://audience-explorer-api.dstillery.com by default).
• Optionally uses an API key credential for authorization; if provided, it is sent as a Bearer token in the HTTP header.
• No other external dependencies are required.

Troubleshooting

• Common Issues:

  • Missing or invalid API key may result in authorization errors.
  • Incorrect formatting of the Interest Types string (e.g., non-numeric or malformed comma separation) could cause API request failures.
  • Empty or too vague marketing briefs might return empty or irrelevant audience lists.

• Error Messages:

  • If the API call fails, the node throws an error with the message returned from the API or a generic network/request error.
  • When continueOnFail is enabled, errors are captured and returned in the output JSON under the error field instead of stopping execution.

• Resolution Tips:

  • Ensure the API key credential is correctly configured and valid.
  • Validate the marketing brief content to be descriptive enough for meaningful recommendations.
  • Confirm the interest type IDs are correct and supported by the API.

Links and References

• Dstillery Audience API Documentation (Assumed public API docs URL for reference)
• n8n Documentation on HTTP Request Node (for understanding underlying HTTP calls)

This summary covers the "Audience" resource with the "Get Recommendation" operation only, as requested.