The documentation for fetchAndJoinCustomAudience shows the field user_bidding_signals in snake case. The respective field when accessed from the bidding JS is userBiddingSignals in camel case (which took weeks to figure out, see #90).
This is specifically causing problems, as we have to use two different representations for a custom audience in our system - one for CA management and a different one for bidding - and make sure we use the correct one in each instance.
All other fields that I checked are in snake case, as expected.
The documentation for
fetchAndJoinCustomAudienceshows the fielduser_bidding_signalsin snake case. The respective field when accessed from the bidding JS isuserBiddingSignalsin camel case (which took weeks to figure out, see #90).This is specifically causing problems, as we have to use two different representations for a custom audience in our system - one for CA management and a different one for bidding - and make sure we use the correct one in each instance.
All other fields that I checked are in snake case, as expected.