Stay organized with collections
Save and categorize content based on your preferences.
When you create a custom audience, you can specify some or all of the custom
audience metadata. This information can be passed directly when creating a
CustomAudience object. The CustomAudience.Builder also supports a
dailyUpdateUri field which can both supply and update the metadata. The
platform will run a background job every 24 hours to fetch updated metadata from
the dailyUpdateUri, or every four hours if the custom audience doesn't yet
have the AdData needed to participate in an auction. The platform can
update the following pieces of custom audience metadata:
User bidding signals
Trusted bidding data
AdData list
To update this metadata, a daily background update process queries against the
dailyUpdateUri defined in the custom audience which may return a JSON
response.
The JSON response may contain any of the supported metadata fields that need
to be updated.
Each JSON field is validated independently. The client ignores any
malformed fields, which results in no updates to that particular field in
the response.
An empty HTTP response or an empty JSON object "{}" results in no
metadata updates.
The response message size must be limited to 10 KB.
All URIs are required to use HTTPS.
trusted_bidding_uri must share the same ETLD+1 as the buyer.
Example: JSON response for background daily update
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-12-17 UTC."],[[["Custom audiences can have metadata specified directly during creation via the `CustomAudience` object."],["A `dailyUpdateUri` within the `CustomAudience.Builder` allows for both supplying and updating custom audience metadata through a background process that runs every 24 hours, or every 4 hours if `AdData` is needed."],["The platform updates user bidding signals, trusted bidding data, and the `AdData` list from a JSON response obtained by querying the `dailyUpdateUri`."],["The JSON response from the `dailyUpdateUri` can include any supported metadata fields, but malformed fields will be ignored, and empty responses result in no updates, with a maximum size of 10 KB."],["All URIs must use HTTPS, and `trusted_bidding_uri` must share the same ETLD+1 as the buyer."]]],["Custom audiences utilize metadata specified during creation or updated via a `dailyUpdateUri`. A background job fetches updated metadata from this URI every 24 hours, or every 4 hours if `AdData` is missing. The process updates user bidding signals, trusted bidding data, and the `AdData` list from a JSON response. Malformed JSON fields are ignored, and empty responses cause no updates. Responses are limited to 10KB, must use HTTPS, and trusted bidding URIs must match the buyer's domain.\n"]]