It started as a messy pile of digital breadcrumbs. After every contest or casual FT8 session, I’d have a half‑empty ADIF file here, a manual pencil note there, and a GridTracker map full of colorful blips that vanished the moment I closed the window. My logging was a leaky bucket. Something had to change.
Then I stumbled on the integration. One toggle. One TCP port. One “aha” moment. gridtracker log4om
GridTracker gives me the story of the band — propagation paths, greyline openings, who’s hearing me. Log4OM gives me the truth — awards progress, QSL status, notes, and a unified log I can sync to QRZ, eQSL, and LoTW with one click. Together, they transformed operating from reactive button‑clicking into strategic grid hunting. It started as a messy pile of digital breadcrumbs
So if you’re still copying and pasting between windows or manually typing in grids from a map, stop. Set up the GridTracker → Log4OM pipeline. Your future self — the one chasing Worked All States or that last elusive DXCC entity — will thank you. Something had to change
GridTracker’s alert system pings me when a rare DX entity or a new grid appears. I work the station. Log4OM logs it. Later, when I run a “Missing Grids” report in Log4OM, the data is already there. No reconciliation weekends. No “wait, did I log that?”
Because a QSO you don’t log is a QSO you never made. And a grid you don’t track is a grid you’ll work twice.
That’s when I discovered the quiet power of connecting to Log4OM .