Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update renderUrl -> renderURL capitalization #1381

Merged
merged 1 commit into from
Jan 16, 2025
Merged

Update renderUrl -> renderURL capitalization #1381

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions FLEDGE_Key_Value_Server_API.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ keys needed from request query strings and prevent potential key collision, even
though the keys may be unique across namespaces in today’s use cases.

* For a DSP, there are: `keys` and `interestGroupNames`.
* For an SSP, there are `renderUrls` and `adComponentRenderUrls`.
* For an SSP, there are `renderURLs` and `adComponentRenderURLs`.

The
[Protected Audience explainer](https://github.com/WICG/turtledove/blob/main/FLEDGE.md#31-fetching-real-time-data-from-a-trusted-server)
Expand Down Expand Up @@ -256,13 +256,13 @@ In the request, one major difference from V1/BYOS is that the keys are now group
</td>
</tr>
<tr>
<td>renderUrls
<td>renderURLs
</td>
<td rowspan="2"><em>Similarly, sellers may want to fetch information about a specific creative, e.g. the results of some out-of-band ad scanning system. This works in much the same way, with the base URL coming from the trustedScoringSignalsUrl property of the seller's auction configuration object.</em>
</td>
</tr>
<tr>
<td>adComponentRenderUrls
<td>adComponentRenderURLs
</td>
</tr>
</table>
Expand Down
Loading