Geographic enrichment is one of the things server-side tagging does well, provided you treat the IP as something to consume rather than something to keep.

The short version: geographic reports that survive a privacy review is mostly a matter of doing the obvious thing carefully. Look up the geo on receipt, attach country and region to the event, drop the IP before anything else gets a chance to log it.

You give up forensic detail. For analytics that almost never matters; for fraud workflows it might. That trade-off is the one most teams underweight when they plan the work, and it is the one that quietly determines whether the project ships on time.

If you want a longer treatment, we have a deeper post in the series. For now, the takeaway is small enough to fit on a sticky note: Treat the IP the way you treat raw card numbers: it should never linger.