[conversions] Use base 10 encoding for impression and conversion data
What: No longer parse impressiondata as hex, or use hex when sending conversion reports. Why: This causes needless conversions for developers, as raised on https://github.com/WICG/conversion-measurement-api/issues/60 Note that the conversions database stores imp and conversion data as strings currently because they are represented as hex. These can be converted to strings now, but this is left as a followup. Bug: 1163599 Change-Id: I5b164c380a97cb272c6a0ee698df8b744feb58ae Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2611958Reviewed-by:Charlie Harrison <csharrison@chromium.org> Reviewed-by:
Nate Chapin <japhet@chromium.org> Commit-Queue: John Delaney <johnidel@chromium.org> Cr-Commit-Position: refs/heads/master@{#842561}
Showing
Please register or sign in to comment