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.

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

Introduce SDK configuration properties for Creative Factory Timeout #663

Closed
YuriyVelichkoPI opened this issue Aug 10, 2023 · 0 comments · Fixed by #664
Closed

Introduce SDK configuration properties for Creative Factory Timeout #663

YuriyVelichkoPI opened this issue Aug 10, 2023 · 0 comments · Fixed by #664
Assignees
Milestone

Comments

@YuriyVelichkoPI
Copy link
Contributor

YuriyVelichkoPI commented Aug 10, 2023

Motivation

Provide publishers with an API to change the timeout for requesting and rendering the ad.

Objectives

  • Introduce the following properties to customize the SDK behavior:
    • PrebidMobile.creativeFactoryTimeout to customize BANNER_TIMEOUT.
    • PrebidMobile.creativeFactoryTimeoutPreRenderContent to customize INTERSTITIAL_TIMEOUT and VAST_TIMEOUT.
  • Introduce customization of these properties via Server Side Configuration using the bidrequest.ext.prebid.passthrough object. See details here and here.
    • cftbanner to customize BANNER_TIMEOUT.
    • cftprerender to customize INTERSTITIAL_TIMEOUT and VAST_TIMEOUT.
  • Introduce the following policy of selecting the needed timeout in runtime:
    • If the timeout is present in the passthrough object, use it (Priority I).
    • If the timeout is set via the SDK API PrebidMobile.creativeFactoryTimeout* use it (Priority II).
    • Use the default value (Priority III).
  • TBD: need to wait for pub's feedback about the default value. Maybe it makes sense to increase it.
  • Add tests
@YuriyVelichkoPI YuriyVelichkoPI changed the title Introduce SDK configuration property for Creative Factory Timeout Introduce SDK configuration properties for Creative Factory Timeout Aug 10, 2023
@jsligh jsligh self-assigned this Aug 10, 2023
@YuriyVelichkoPI YuriyVelichkoPI added this to the 2.1.3 milestone Aug 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants