Skip to content

Mobile app rendering: if burl is missing from bid, write ad markup after MRAID-viewable#248

Open
rickyblaha wants to merge 2 commits intoprebid:masterfrom
rickyblaha:yahoo-mobile-render-after-mraid-viewable-when-burl-missing
Open

Mobile app rendering: if burl is missing from bid, write ad markup after MRAID-viewable#248
rickyblaha wants to merge 2 commits intoprebid:masterfrom
rickyblaha:yahoo-mobile-render-after-mraid-viewable-when-burl-missing

Conversation

@rickyblaha
Copy link

To reduce discrepancies, when burl is missing from mobile app bids, rendering of ad markup is now delayed until MRAID-viewable happens, so tracking pixels present in ad markup do not get called too soon.

Included units tests along with a simple mock of MRAID 2 and MRAID 3 that has only enough features for these tests.

Also included a simple log function called during this rendering sequence to help with debugging. Once ad render already happens, you can use Safari Dev Tools to inspect the web view, go to the console and type pucLogs to see all the console logs that happened prior to opening dev tools.

Ricky Blaha added 2 commits December 19, 2024 02:27
… if there is a burl present. If no burl, render the markup only after mraid viewable happens.

* Added console logs to observe this behavior that stick around in `window.pucLogs` so they can be viewed once a web view is inspected after render has already taken place.
* Added simple MRAID 2 and 3 for use in the unit tests for this change.
@arjunt
Copy link

arjunt commented Mar 15, 2025

@YuriyVelichkoPI - we should complete the review of this PR and the open measurement impression tracking PR for Mobile.
I understand the there is a plan to release a new version of the PUC, so would be good to complete before that. Thanks.

@mmullin
Copy link
Contributor

mmullin commented Apr 24, 2025

@ChrisHuie FYI

@justadreamer
Copy link

discussed in PMC:

  • Yahoo has a powerful feature-flag infrastructure that allows them to conditionally enable such features through a flag passed as a key-value, this allows limited testing
  • The suggestion is to integrate a feature-flag support and enable this feature conditionally when a certain key-value is sent
  • That should give some confidence in deploying and a way for pubs to opt-in to this feature

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants