# Best practices

On this page we have collected "best practices" for integrations that use our API. These suggestions are based on the design of [musement.com](https://www.musement.com) and knowledge of the API's inner workings. Follow these tips to make your integration as efficient and user friendly as possible.

## Include location information

Help your customers understand where an activity takes place by displaying either its [default city](/api/catalog/activities/cities) or all its [connected destinations](/api/catalog/activities/cities#activities-with-multiple-cities).

Show any coordinates for a [meeting point](/api/catalog/activities/meeting-point) on a map so that customers can clearly see where an activity starts.

Include details about the activity's [venues](/api/catalog/activities/venues) too to give your customers a better idea of what attractions and landmarks they're going to see.

## Create your own destination catalog

Set up a scheduled action to sync [Musement cities](/api/catalog/cities) with your own destination catalog. It makes it easier to set up a dedicated destination page that lists available activities.

By mapping our cities to your destinations, you gain more control over how you display the catalog. You can customize your mapping to group multiple cities into a single destination or ignore the locations you aren't interested in. For more information on getting activities by one or more cities, [check out this page](/api/catalog/activities/searching#cities).

## Use multiple filters

Give your customers a better user experience by giving them more filters to find the activities they want. Whether it's a destination page or general search results, always include these popular filter options:

* [Available dates](/api/catalog/activities/searching#dates)
* [Categories](/api/catalog/activities/searching#categories)
* [Features](/api/catalog/activities/searching#features) and [services](/api/catalog/activities/searching#services)


## Pay attention to sorting

By default, our API sorts activities by the `relevance` property, from lowest to highest. We strongly recommend modifying the call to **sort results from highest to lowest instead** so that customers start the page with the most popular activities first.

Improve the user experience more by giving your customers control over the sorting direction and criteria. We encourage adding options to sort activities by popularity ([relevance](/api/catalog/activities/relevance#sorting)), [prices](/api/catalog/activities/prices#sorting) and [ratings](/api/catalog/activities/ratings#sorting).