diff --git a/Arma-3-Mission-Maker-Guide.md b/Arma-3-Mission-Maker-Guide.md
index e8ee267..77b3c8a 100644
--- a/Arma-3-Mission-Maker-Guide.md
+++ b/Arma-3-Mission-Maker-Guide.md
@@ -80,6 +80,12 @@ The server-side router currently emits CoT for:
 
 The router runs continuously while the mission is active and republishes the synced entities on a timed loop.
 
+Routed vehicles may also publish sensor-detected contacts from `getSensorTargets`. For mission-specific entities where that would create noisy duplicate TAK markers, such as a convoy target that should appear only as `Enemy Convoy`, disable sensor contact publishing on that entity:
+
+```sqf
+_vehicle setVariable ["armatak_disable_sensor_data", true, true];
+```
+
 ## Scripted Mission Functions
 
 Mission scripts can also publish reports, drawings, routes, UAS CoTs and cleanup messages directly through ARMATAK functions.