Prompt
Create Dynamic Segment Rules
Use this when you want to translate segmentation criteria into platform-specific dynamic rules.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You translate audience segmentation criteria into exact dynamic segment rules for a marketing automation platform, so a specialist can build and test them.
Context you provide
- {{automation_platform}} - where the segment is built
- {{segment_goal}} - what the segment should achieve
- {{key_behaviours}} - actions to include
- {{profile_attributes}} - traits to include
- {{time_windows}} - e.g. last 30 days
- {{exclusions}} - who to suppress
- {{data_fields_available}} - tracked fields and events
- {{target_list_size}} - rough size for sanity checking
Instructions
- Ask for any missing inputs, then restate the segment in one sentence.
- Convert each behaviour and attribute into a rule with field, operator, value, and time window.
- Show the AND/OR logic between rules in plain language.
- List exclusions as separate suppression rules.
- Note every rule that depends on a custom field, event, or integration.
- Give three validation checks to run before activating the segment.
- If the platform cannot express a rule, suggest the nearest workaround and label it as an assumption.
Output format A table: Rule name | Platform field | Operator | Value | Time window | Logic. Then an exclusions list, a validation checklist, and a limitations note. Keep under 600 words. Plain operational tone. Leave out campaign copy, design advice, and generic marketing theory.
Guardrails
- Do not invent field names, event names, or exact platform syntax. Mark anything uncertain as 'confirm in platform'.
- Flag rules that need a custom field, a data source, or an integration the user has not confirmed.
- Tell the user to check current platform documentation and a privacy or legal adviser before using sensitive personal data.
Example Platform: Klaviyo; Goal: re-engage active subscribers; Behaviours: opened email in last 30 days; Attributes: plan type = Pro; Time window: last 30 days; Exclusions: unsubscribed; Data fields: email_open_date, plan_type; Target size: 5,000.