Expose completion state, raw data and page-supplied evidence on the fod object - #15
Merged
Conversation
justadreamer
force-pushed
the
feature/fod-page-contract
branch
from
August 5, 2026 07:35
0ca2999 to
c39af8a
Compare
The data/isComplete work on the fod object is an independent feature: it touches none of the request-body code and its own semantics are unsettled (a recorded failure latches isComplete, and the complete-from-cache path reports completion while a refresh is in flight). Taking it out leaves this change to one concern; the public state contract can come back on its own terms, as accessors rather than a state copy that every transition has to remember to re-sync.
The query string of the script URL does not take precedence over the body: its parameters are re-sent as form fields in the same body, so a duplicated key is two form fields of the same name and the winner depends on the server's form parsing. The "never stored" guarantee covers the evidence values, not the response they produce, which is cached in session storage verbatim. Also state what happens to non-string values, which the code coerces rather than rejects.
justadreamer
approved these changes
Aug 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Two additions to the JavaScript template:
fod) now exposes two public properties alongside the existingcomplete()/onChange()API:isComplete:falsewhile evidence collection is in flight,trueonce processing has finished (successfully or not; seedata.errors).data: the latest raw JSON payload. Unlike the property getters it keeps missing values asnullinstead of the null-reason text.<ObjectName>Evidence(defaultfodEvidence) before the script executes. Each entry is url-encoded and appended to the form-data body of the existing POST request. The values are never written to the URL, cookies or web storage, so this is the supported way to pass sensitive evidence.Both are documented in the README.
Why
This lets an on-page 51Degrees integration share its result with other consumers. The first consumer is the Prebid.js 51Degrees RTD module: it detects
fodon the page automatically and enriches the bid request from it instead of loading a second copy of the script.The evidence object gives pages a way to pass evidence that must not appear in a URL or persist in the browser.
Without
<ObjectName>Evidenceon the page the generated script behaves exactly as before.