Skip to main content
A series per traveler-type segment (Solo/Couple/Family/Group) of demand for a destination. —destination is required. (traveler_type is not a filter here — it is the dimension.)

Usage

jinko travel-demand audience-trend [options]

Options

FlagRequiredDescriptionDefault
--origin <level:code>Noorigin filter, e.g. Country:US or City:NYC (or ‘global’ for all origins)
--destination <level:code>Nodestination, e.g. Country:JP (required)
--departure-date-from <YYYY-MM-DD>Nostart of departure window (use with —departure-date-to; omit both for no departure-date filter — buckets count searches for all departure dates, recommended)
--departure-date-to <YYYY-MM-DD>Noend of departure window (use with —departure-date-from; omit both for no departure-date filter)
--trip-type <type>NoOne-Way|Round-Trip
--trip-duration-min <n>Nominimum trip length in nights (round-trips only, >= 0)
--trip-duration-max <n>Nomaximum trip length in nights (>= —trip-duration-min)
--search-window-min <n>Nominimum advance-purchase window in days before departure (>= 0)
--search-window-max <n>Nomaximum advance-purchase window in days (>= —search-window-min)
--trend-window <n>Nonumber of buckets the series spans, in the granularity unit (day 2-60 | week 2-52 | month 2-12, default 12)
--granularity <bucket>Noseries bucket size: week (default) | day | month"week"
--limit <n>Nomax number of series (top-N), 1-50 (default 10)