In the context of linearized weak-field gravity, the amplitude (more formally, the "peak gravitational wave strain h") from a compact source (such as a binary inspiral measured by Ligo) falls off as 1/r, i.e. ##h \propto 1/r##.
There are two polarizations of the GW, generally written as ##h_+## and ##h_x##, one can consider ##h = \sqrt{(h_+)^2 + (h_x)^2}##. But for detectors such as Ligo, only one component is measured, thus the Ligo measurement of amplitude will under-represent the "real" amplitude.
See for instance the wiki article
https://en.wikipedia.org/wiki/Gravitational_wave. The Ligo detection paper
http://journals.aps.org/prl/abstract/10.1103/PhysRevLett.116.061102 might also be of some interest.
Energy is tricky to define in GR, but in the context of linearized gravity the average energy flux carried by a GW is proportional to the square of the rate of change of h, i.e. ## E \propto \dot{h}^2##, where the over-dot represents taking the time derivative. The reference I have online, http://www.tat.physik.uni-tuebingen.de/~kokkotas/Teaching/NS.BH.GW_files/GW_Physics.pdf, actually writes this as ##E \propto \omega^2 h^2##, which applies for sinusoidal GW's. Since non-sinusoidal waves are important in the Ligo case, I'll give the more general formula. I'd give a better reference on this if I had one, this is what I have available.
If one is not interested in the effects of frequency on GW's, only about the effects of distance, one might say that ##h \propto 1/r## and ##E \propto 1/r^2##
It may be worthwhile reviewing the defintion of "Energy Flux" - wiki gives "
Energy flux is the rate of transfer of
energy through a surface. The quantity is defined in two different ways, depending on the context." The right context in this situation is that the average energy flux is the average rate of energy transfer per unit area.
The part about "averaging" the energy is important for technically reasons. It's an error to assume that GW energy can be localized in any traditional manner. It's rather difficult to explain these technical aspects, the general approach I've seen in popularizations is to ignore the issue entirely. I'm not sure how much harm ignoring this issue does for a broad, non-specialist understanding, so I won't spend a lot of words emphasizing the issue, I will just mention that it exists.