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

Improve documentation for omidVendorAccess #1063

Closed
MarkusWollny opened this issue Sep 12, 2022 · 2 comments
Closed

Improve documentation for omidVendorAccess #1063

MarkusWollny opened this issue Sep 12, 2022 · 2 comments
Assignees

Comments

@MarkusWollny
Copy link

MarkusWollny commented Sep 12, 2022

Our ad agency asked us to configure our video player to allow full Open Measurement access for Double Verify. The current documentation just references the official Google IMA SDK docs and doesn't give an example for setting omidVendorAccess, so I guessed that setting

ima.options = {
  ...
  omidVendorAccess: {
    DOUBLEVERIFY: 'FULL',
    OTHER: 'FULL'
  }
  ...
}

should do just that, but they tell me that they aren't seeing the expected incoming data. I am not sure if this is due to a misinterpretation of the omidVendorAccess setting on my part or if there is perhaps something wrong on their end. Would it be possible to include an example setting in the documentation? Is there some programmatic way to verify the OMID rules in effect during development on my side?

@Kiro705
Copy link
Member

Kiro705 commented Sep 13, 2022

Hello @MarkusWollny ,

Please take a look at the IMA guide for setting access move rules. The key and value pairs should use the IMA constants.

The updated code sample should be:

ima.options = {
  ...
  omidVendorAccess: {
    [google.ima.OmidVerificationVendor.DOUBLEVERIFY]: google.ima.OmidAccessMode.FULL,
    [google.ima.OmidVerificationVendor.OTHER]: google.ima.OmidAccessMode.FULL,
  }
  ...
}

Please let me know if you have any follow-up questions,
Jackson
IMA SDK team

@Kiro705 Kiro705 self-assigned this Sep 13, 2022
@MarkusWollny
Copy link
Author

Thank you! I wasn't aware that google.ima was actually directly available inside the plugin's configuration - I guess I just overcomplicated things and should have simply tried that :)

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

No branches or pull requests

2 participants