Skip to content

Document tags conditions for Single-Email Campaign audiences - #137

Draft
wstrinz wants to merge 2 commits into
apidocs-l3-schedule-409from
apidocs-l4-audience-tags
Draft

wstrinz wants to merge 2 commits into
apidocs-l3-schedule-409from
apidocs-l4-audience-tags

Conversation

@wstrinz

@wstrinz wstrinz commented Oct 22, 2026 •

Copy link
Copy Markdown

Part of: https://dripcom.atlassian.net/browse/GG-1928

Documents changes here:

Background

  • Set the audience now accepts tags conditions alongside segments.
  • The docs still say segments is the only condition type, and Fetch the audience uses a tag rule as its example of an audience that cannot be returned as a filter.

Modification

  • Set the audience: describes tags conditions, with a table of the eight operators and the value each takes, and adds a tag exclusion to the three examples. The existing segment_id notes move up to sit with the segments description.
  • Fetch the audience: updates both examples, so the unsupported one now uses a rule that is still unsupported, and notes when unsupported_types is left out.

Result

  • Audiences that use tags can be built and read back from the docs alone.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant