Repository navigation
Integrating VAST Ads with DP2SceneGraphWizard #173
Replies: 46 comments 36 replies
|
This project does support ad monetization. The wizard will accept a URL for your ad server and expects to receive ad pods when scheduling ads based on your feed file ad schedule. Have you tried specifying an ad server in the wizard? |
|
@rrirower it still not working |
|
The sample vast tag you sent contains required text substitutions. For example, the vast url contains |
|
@rrirower This is what the ad company said: Regarding the "[REPLACE_ME]" placeholders in the VAST tag, these are macro slots that need to be dynamically populated by your ad server or player for each individual request. Essentially, instead of the static "[REPLACE_ME]" text, your system should automatically insert the specific data describing the unit of traffic being sent to us (such as Device ID, App Name, User Agent, etc.). This ensures that the information is accurate for every ad call. Best regards.. |
|
hello Yes - please see the response below; Hello, As promised, I am getting back to you regarding your developer's questions. To clarify the workflow: the macro slots in the ad request do indeed need to be dynamically populated by the ad server or the video player making the request. However, in our current integration, Adtelligent is acting as a demand partner (advertiser), not as the ad server. Your system or ad server is responsible for replacing those macros with actual user data before sending the request to us. As a side note, Adtelligent does have an enterprise ad server, but it is an entirely separate product. If you are ever interested in exploring that as a solution for your stack, I would be happy to connect you with the respective team. To help your developer move forward, here is the VAST request template specifically formatted with standard Roku macros: Important Note: Please ensure that the * symbols in the app_name=* and app_store_url=* parameters are replaced with the specific, hardcoded values for each individual app you are monetizing. The rest of the capitalized Roku macros should be dynamically replaced by your system on every call. Please let me know if this clears things up or if your developer has any further questions! |
|
i will wait for your response |
|
okay |
|
Maybe it's because there's no ads published? Maybe that's what it means.? |
|
@rrirower Sure no problem - I will loop you in on a separate thread. Thank you, |
|
can you send me your mail |
|
okay |
|
i created a feed using your software - i don't see any adBreak objects |
|
or can you send me feed sample that contains 'adBreak' objects |
|
hello |
|
okay |
|
okay |
|
or This video link can not work https://bnrokuserver.s3.us-east-1.amazonaws.com/Videos/0729+(2).mp4 |
|
https://api.npoint.io/c945e2fc4bb48d1c5c54.json |
|
okay |
|
i have define it to 00:00:00 |
|
yes, i want to Ask questions |
|
okay |
|
please can you help me check it if it twork |



Uh oh!
There was an error while loading. Please reload this page.
@rrirower
Hello, I’ve been exploring DP2SceneGraphWizard and it’s been helpful for building SceneGraph components.
I’m currently working on monetizing a Roku channel using a third-party ad provider that supplies a VAST tag URL.
I wanted to ask if it’s possible to integrate VAST ads within a SceneGraph app generated using this tool.
Does DP2SceneGraphWizard support structuring or generating components that work with RAF, or would this need to be implemented manually in the video player logic?
Any guidance or best practices would be appreciated. Thank you!
All reactions