🗺️ How can I create custom areas in Fleettracker and receive notifications when vessels enter or leave them?
Fleettracker allows you to define custom Areas/Places on the map to monitor vessel activity. You can use these areas to automatically trigger email notifications when a vessel enters or leaves a defined zone.
1. What are Areas (Places)?
Areas (also called Places) are user-defined zones on the map. To show already created areas on the map check the option Show Places/areas.
They can be used to:
- Monitor vessel movements in specific regions
- Track port arrivals and departures
- Automate notifications based on vessel activity
2. Creating a new Area
Step 1: Open the Chart
- Go to the Chart view
Step 2: Access the area/place function
- Open the map tools or settings menu
- Select the + icon to create a new Area / Place
Step 3: Define the area
- Draw the area directly on the map
(e.g. polygon or radius, depending on system setup) - Adjust size and position as needed
Step 4: Name the area
- Enter a clear and descriptive name
(e.g. “Rotterdam Port Zone”, “Singapore Anchorage”)
Step 5: Save the area
- Confirm and save your configuration
3. Setting up email notifications
Fleettracker allows you to trigger automatic emails based on vessel movement.
How to set it up:
- Login with your Fleettracker admin account
- go to Admin -> Settings -> Email Messaging -> Add new messaging
- Add one or more email recipients
- Select the complete fleet or selected vessels
- Select message type Area Enter/Leave Report
- Confirm with the Save button
Once activated:
- Fleettracker monitors vessel positions continuously
- When a vessel crosses the defined boundary:
- An email notification is automatically sent
This allows you to stay informed without manually checking the system.
4. Typical use cases
Areas and notifications are commonly used for:
- Port monitoring → arrival & departure alerts
- Geofencing → tracking vessels in specific regions
- Operations control → automatic updates for teams or customers
- Security → monitoring sensitive or high-risk zones
5. Best practices
- Keep area names clear and standardized
- Avoid overly large or overlapping areas
- Only enable notifications where needed to prevent email overload