Conversation
daniel-earle-scope3
commented
Aug 15, 2024
daniel-earle-scope3
commented
- Updated based on (https://www.notion.so/scope3/Update-docs-guides-3eb00757116348dfa83f46fc0b997299)
- Updated a typo and wording
- Updated based on (https://www.notion.so/scope3/Update-docs-guides-3eb00757116348dfa83f46fc0b997299) - Updated a typo and wording
| | `video_player` | Video player used to render video (if applicable) | | ||
| | `other_assets_bytes` | Metadata, text, html, etc | | ||
| | `ad_platforms` | Ad serving, verification, and measurement ad platforms wrapping or embedded in the ad format | | ||
| | `identifier` | The identifying information, including name, channel, and device type | |
There was a problem hiding this comment.
We call this adFormat in the docs and throughout the Scope3 application for integrate reporting. Should we be consistent here as well?
This identifier also does not contain the channel or device type. What we expect the identifier to for clients to give us does not contain that information nor does this field contain that for querying the API
There was a problem hiding this comment.
making changes as noted here.
if adFormat is the correct field for consistency, then let's use that
| | `creative_ad_format` | Either a basic or vendor-provided ad format | | ||
| | `identifier` | The identifying information, including name, channel, and device type | | ||
| | `vendor` | The name of the serving vendor | | ||
| | `ad_format` | Either a basic or vendor-provided ad format | |
There was a problem hiding this comment.
I'm not sure why we have both identifier and ad_format here?
The identifier would also just be an identifying information. I think including name, channel, and device type might be confusing what the user is meant to provide
2 participants
