@Devon Miller yeah this is a real concern and worth thinking through carefully before you're debugging it in the field.
The magnetometer itself isn't directly sensitive to 2.4GHz RF — it's measuring DC and low-frequency magnetic fields, so the carrier frequency isn't the problem. What you actually have to watch out for is the switching currents on the power supply when the BLE front-end kicks into a transmit burst. Those create fast transient magnetic fields right at the module, and if your magnetometer is physically close, you can see spikes in the readings that correlate with TX activity. The effect is usually worst during high-power bursts and gets much better with distance, so if you have any flexibility in your physical layout, getting even a centimeter or two of separation between the two modules helps a lot.
The other thing I'd look at is your power rail. If the BLE module and sensors module share the same supply line without good decoupling, the transmit current spikes can show up as noise on the magnetometer's supply voltage, which causes a different but equally annoying artifact. Make sure you've got solid bypass caps close to both modules and ideally a small inductor or ferrite bead isolating the sensor supply from the BLE supply.
In practice most people running this stack don't have major issues, but if you're doing heading-sensitive navigation work where magnetometer accuracy really matters, it's worth doing a quick validation test — log magnetometer readings while toggling BLE TX on and off and see if you can spot any correlation before you commit to the final board layout.
