If the self-tests succeeded, then you’re good. Assuming you have a dynamic IP, you won’t see much regular traffic as your connection info will change every ~12h. There’s an option for your torrc to change the bridge distribution method, which might give you more traffic. Unfortunately, I forget what it was called.
I found it! It’s ‘BridgeDistribution “option”’ (in /etc/tor/torrc) ‘https’ (or ‘any’) is probably what you want. This advertises your bridge on https://bridges.torproject.org meaning whoever grabs a bridge from there probably doesn’t have a censored internet connection and would be fine with a non-stable (dynamic) bridge.
‘email’ would give your bridge info to someone who emails bridges@torproject.org as a way to circumvent some low-tier censorship.
There’s also an ‘unallocated’ slot which are bridges given to activists during protests or to Tor developers or whatever, but I don’t know if there’s an option to specifically select that (there was some discussion on whether ‘none’ should put a bridge into this slot or not advertise a bridge at all, but I don’t know what they did in the end.)
Lastly, I don’t think there’s a big problem running a normal relay with a dynamic IP as the IP change should be recognized right away. The difference is much bigger when running a bridge. Bridges with static IPs are very important as they can be written down and handed to a friend in a heavily censoring country and it can be relied on to be stable. Try that with a dynamic IP and your bridge will be valid for only a few hours. The good thing about dynamic bridges however is that, since some governments (like China f.e.), might start making lots of requests to bridges.torproject.org and blocking those bridges immediately, your dynamic bridge IP will be useless to them within a few hours and will effectively turn into a new unblocked bridge for someone who just wants a bridge to hide that they’re using Tor at all.
Have fun and thanks for running a bridge relay!