Building Audiences from Conditions (Audience Filter)

Overview

Audience Filter builds audiences from user behaviour conditions instead of requiring a manually uploaded CSV. The system pulls the member list straight from data it has already recorded.

Supported condition sources:

Source	Example condition
Campaign	Opened or clicked a particular campaign
Rich Menu	Tapped a particular menu button
Auto Response	Sent a message matching a particular keyword
Form Builder	Answered a particular question with a particular value
Multi-source	Any combination of the above

The module's key strength is its preview step, which shows the member count and a sample of matching members before anything is created — reducing the risk of building the wrong audience and only discovering it after messages have gone out.

Business Flow

Preparing the options

1. cms-web loads the selectable options for each source into dropdowns via the list-dropdown-campaign, list-dropdown-richmenu, list-dropdown-auto-response and list-dropdown-form-builder endpoints.
2. If the user filters by form, GET /api/audiences-filter/form-questions/:formId returns that form's questions so a specific question and expected value can be chosen.
3. GET /api/audiences-filter/form-response shows a preview of the raw answers, confirming the shape of the data.

Preview, then create

4. Form-based filter — call POST /api/audiences-filter/preview-form-filter to inspect the result, then POST /api/audiences-filter/create-form-filter to create it for real.
5. Multi-source filter — the same pattern using preview-multi-source-filter followed by create-multi-source-filter.
6. General filter — POST /api/audiences-filter/create-filter with a CreateAudiencesFilterDto payload.
7. Every creation path checks the maxSegments quota from the customer's plan first.
8. Once created, the result becomes a regular audience managed by the Audience Management module, including member CSV generation and optional auto-refresh.

Internal path

9. POST /api/audiences-filter/internal/refresh is called by other services, not by users. It is protected by InternalApiKeyGuard via the X-Internal-Key header and accepts a body containing audienceId, lineOaId, organizationId, lineOaHash and triggerType. Workers and webhooks use it to trigger a recomputation of a filter-derived audience's members.

Key Files & Functions

The code lives in internal/modules/audiencefilter/, split across controller.go, service.go and dto.go.

Method	Route	Handler	Policy
POST	/api/audiences-filter/create-filter	ct.createFilter	create audiences
GET	/api/audiences-filter/list-dropdown-campaign	ct.getListDropdownCampaign	read audiences
GET	/api/audiences-filter/list-dropdown-richmenu	ct.getListDropdownRichmenu	read audiences
GET	/api/audiences-filter/list-dropdown-auto-response	ct.getListDropdownAutoResponse	read audiences
GET	/api/audiences-filter/list-dropdown-form-builder	ct.getListDropdownFormBuilder	read audiences
GET	/api/audiences-filter/form-questions/:formId	ct.getFormQuestions	read audiences
GET	/api/audiences-filter/form-response	ct.formResponsePreview	read audiences
POST	/api/audiences-filter/preview-form-filter	ct.previewFormSegment	read audiences
POST	/api/audiences-filter/create-form-filter	ct.createFormFilterAudience	read audiences
POST	/api/audiences-filter/preview-multi-source-filter	ct.previewMultiSourceFilter	read audiences
POST	/api/audiences-filter/create-multi-source-filter	ct.createMultiSourceFilter	create audiences
POST	/api/audiences-filter/internal/refresh	ct.internalRefresh	internalApiKeyGuard()

Connections to Other Services

• Permissions — user-facing routes sit on the authed group, which enforces JWT globally, and carry PolicyModuleAudiences as metadata. The internal route uses InternalApiKey (from the INTERNAL_API_KEY environment variable) instead of a JWT.
• Tables — audience, campaign, rich_menu, auto_response, form_builder, form_submission, line_user and tracking_line_users.
• Cross-module — calls formbuilder.Service.GetFormById through a local formByIDProvider interface to avoid an import cycle, and depends on Plan Limits and Storage.
• Storage — writes the resulting member list as a CSV file to object storage.
• Related modules — Audience Management, Form Builder, Campaign Management and Rich Menu.