Best Practices for Journey Queries
Generate SQL for Journey tables: Performance, Milestones, Goals, and Touchpoints.
How to Use Prompts?
Name the Journey. Specify metric (drop-off, open rate). Provide a timeframe.
Example: What is the drop-off rate at each touchpoint for Journey X in June?
Examples for Good Prompt vs Bad Prompt
| Prompt | Good / Bad? | Reason? |
|---|---|---|
| Journey stats. | Bad | Too generic. |
| How many milestones completed in Journey Y? | Good | Clear metric. |
| Performance. | Bad | No context. |
| Show email performance in Journey Z last week. | Good | Channel + timeframe. |
| Journey data. | Bad | Needs specifics. |
| Compare SMS vs push in Journey A. | Good | Comparison |
| Goals. | Bad | Ambiguous. |
| Show goal status for Journey B. | Good | Feature + entity |
| Touchpoint details. | Bad | Which journey? |
| List entry sources for Journey C. | Good | Document-query gap—Plan can route. |