Ah, that would ultimately be an oopsie on our end. We had it configured properly (yay), but almost immediately something happened to un-configure it (ugh), and we didn't re-configure it (d'oh). It has just been fixed, and should be working soon!