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

Zeta Global SSP: Make sid param required #3849

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

abermanov-zeta
Copy link
Contributor

Zeta Global SSP Adapter update: 'sid' is a required parameter.

Copy link

github-actions bot commented Aug 8, 2024

Code coverage summary

Note:

  • Prebid team doesn't anticipate tests covering code paths that might result in marshal and unmarshal errors
  • Coverage summary encompasses all commits leading up to the latest one, 1887ce0

zeta_global_ssp

Refer here for heat map coverage report

github.com/prebid/prebid-server/v2/adapters/zeta_global_ssp/zeta_global_ssp.go:22:	Builder			100.0%
github.com/prebid/prebid-server/v2/adapters/zeta_global_ssp/zeta_global_ssp.go:34:	MakeRequests		78.6%
github.com/prebid/prebid-server/v2/adapters/zeta_global_ssp/zeta_global_ssp.go:65:	getImpressionExt	75.0%
github.com/prebid/prebid-server/v2/adapters/zeta_global_ssp/zeta_global_ssp.go:82:	buildEndpointURL	100.0%
github.com/prebid/prebid-server/v2/adapters/zeta_global_ssp/zeta_global_ssp.go:87:	MakeBids		94.7%
github.com/prebid/prebid-server/v2/adapters/zeta_global_ssp/zeta_global_ssp.go:121:	getMediaTypeForBid	100.0%
total:											(statements)		88.9%

@bsardo bsardo changed the title Zeta Global SSP Adapter update: 'sid' is a required parameter. Zeta Global SSP: 'sid' is a required parameter. Aug 8, 2024
@bsardo bsardo changed the title Zeta Global SSP: 'sid' is a required parameter. Zeta Global SSP: Make sid param required Aug 8, 2024
@@ -1,5 +1,8 @@
endpoint: https://ssp.disqus.com/bid/prebid-server?sid=GET_SID_FROM_ZETA
enabled: false
Copy link
Contributor

@Sonali-More-Xandr Sonali-More-Xandr Aug 13, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please help me understand why you have set enabled: false? As per the Prebid Server Documentation, if you want to disable the bidder, you need to set disabled: true

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like copy-pasted from somewhere. Fixed. Thank you!

@@ -9,12 +12,14 @@ capabilities:
mediaTypes:
- banner
- video
- audio
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add json tests for audio

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Copy link

Code coverage summary

Note:

  • Prebid team doesn't anticipate tests covering code paths that might result in marshal and unmarshal errors
  • Coverage summary encompasses all commits leading up to the latest one, cf67e4d

zeta_global_ssp

Refer here for heat map coverage report

github.com/prebid/prebid-server/v2/adapters/zeta_global_ssp/zeta_global_ssp.go:22:	Builder			100.0%
github.com/prebid/prebid-server/v2/adapters/zeta_global_ssp/zeta_global_ssp.go:34:	MakeRequests		78.6%
github.com/prebid/prebid-server/v2/adapters/zeta_global_ssp/zeta_global_ssp.go:65:	getImpressionExt	75.0%
github.com/prebid/prebid-server/v2/adapters/zeta_global_ssp/zeta_global_ssp.go:82:	buildEndpointURL	100.0%
github.com/prebid/prebid-server/v2/adapters/zeta_global_ssp/zeta_global_ssp.go:87:	MakeBids		94.7%
github.com/prebid/prebid-server/v2/adapters/zeta_global_ssp/zeta_global_ssp.go:121:	getMediaTypeForBid	100.0%
total:											(statements)		88.9%

@abermanov-zeta
Copy link
Contributor Author

@Sonali-More-Xandr @onkarvhanumante Could you please take a look again? thank you.

@bsardo
Copy link
Collaborator

bsardo commented Sep 9, 2024

With a field now being required, this is a breaking change so we should hold off on merging until the next major release so that host companies are prompted to re-review their stored requests so they can make the necessary adjustments. Tagging as 3.0.

userSync:
redirect:
url: https://ssp.disqus.com/redirectuser?sid=GET_SID_FROM_ZETA&gdpr={{.GDPR}}&gdpr_consent={{.GDPRConsent}}&us_privacy={{.USPrivacy}}&r={{.RedirectURL}}
url: https://ssp.disqus.com/redirectuser?sid={{.AccountID}}&gdpr={{.GDPR}}&gdpr_consent={{.GDPRConsent}}&us_privacy={{.USPrivacy}}&r={{.RedirectURL}}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AccountID is not a supported macro for user sync endpoints. The information can be optionally provided, so I'm not opposed to adding the macro - but I wouldn't expect it to always be present. How does your user sync behave when the AccountID is unknown?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@SyntaxNode In case of user sync, sid param is not critical for us and doesn't really impact the behavior. However, it would be great for us to know what publisher we do cookie sync with (for internal statistics and troubleshooting).

Copy link
Collaborator

@bsardo bsardo Dec 6, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @abermanov-zeta, as @SyntaxNode mentioned, AccountID is not a supported macro for cookie syncing at this time. If you need this, could you please open a separate PR that adds support for it? If you don't need it at this time, please remove this from your redirect URL.

If you choose to open a new PR to add support for this macro, it will obviously be a macro resolved at runtime. You'll probably want to pull the account ID from endpoints/cookie_sync.go#parseRequest similar to how other runtime macro values are extracted for privacy (see privacyMacros variable) in this function, ensure that it is passed to handleResponse which then passes it to usersync/syncer.go#GetSync where the runtime macros appear to be resolved.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bsardo Thank you! I removed the macro from the redirect url for now. I'll open a separate PR to add support for it once I have time (hopefully, this year).

@bsardo
Copy link
Collaborator

bsardo commented Nov 4, 2024

Hi @abermanov-zeta, when you have time, please resolve conflicts.

Also, we recently released PBS 3.0, more specifically v3.1.0, which updates Prebid Server package import references throughout the project from v2 to v3.
For example:

import (
    "github.com/prebid/prebid-server/v3/adapters"
)

As a result, please merge with master (no rebase) and then ensure all Prebid Server package import references in the files you’ve changed are v3 such that the test suite passes so we can resume reviewing. Thanks!

Copy link

github-actions bot commented Nov 5, 2024

Code coverage summary

Note:

  • Prebid team doesn't anticipate tests covering code paths that might result in marshal and unmarshal errors
  • Coverage summary encompasses all commits leading up to the latest one, 7704f6f

zeta_global_ssp

Refer here for heat map coverage report

github.com/prebid/prebid-server/v3/adapters/zeta_global_ssp/zeta_global_ssp.go:23:	Builder			100.0%
github.com/prebid/prebid-server/v3/adapters/zeta_global_ssp/zeta_global_ssp.go:35:	MakeRequests		78.6%
github.com/prebid/prebid-server/v3/adapters/zeta_global_ssp/zeta_global_ssp.go:66:	getImpressionExt	75.0%
github.com/prebid/prebid-server/v3/adapters/zeta_global_ssp/zeta_global_ssp.go:83:	buildEndpointURL	100.0%
github.com/prebid/prebid-server/v3/adapters/zeta_global_ssp/zeta_global_ssp.go:88:	MakeBids		94.7%
github.com/prebid/prebid-server/v3/adapters/zeta_global_ssp/zeta_global_ssp.go:122:	getMediaTypeForBid	100.0%
total:											(statements)		88.9%

@abermanov-zeta
Copy link
Contributor Author

Hi @abermanov-zeta, when you have time, please resolve conflicts.

Also, we recently released PBS 3.0, more specifically v3.1.0, which updates Prebid Server package import references throughout the project from v2 to v3. For example:

import (
    "github.com/prebid/prebid-server/v3/adapters"
)

As a result, please merge with master (no rebase) and then ensure all Prebid Server package import references in the files you’ve changed are v3 such that the test suite passes so we can resume reviewing. Thanks!

@bsardo Done. Thank you.

@abermanov-zeta
Copy link
Contributor Author

abermanov-zeta commented Nov 21, 2024

@bsardo @Sonali-More-Xandr @SyntaxNode @onkarvhanumante @VeronikaSolovei9 Could you please review again? Thank you!

Copy link

github-actions bot commented Dec 9, 2024

Code coverage summary

Note:

  • Prebid team doesn't anticipate tests covering code paths that might result in marshal and unmarshal errors
  • Coverage summary encompasses all commits leading up to the latest one, 00591b1

zeta_global_ssp

Refer here for heat map coverage report

github.com/prebid/prebid-server/v3/adapters/zeta_global_ssp/zeta_global_ssp.go:23:	Builder			100.0%
github.com/prebid/prebid-server/v3/adapters/zeta_global_ssp/zeta_global_ssp.go:35:	MakeRequests		78.6%
github.com/prebid/prebid-server/v3/adapters/zeta_global_ssp/zeta_global_ssp.go:66:	getImpressionExt	75.0%
github.com/prebid/prebid-server/v3/adapters/zeta_global_ssp/zeta_global_ssp.go:83:	buildEndpointURL	100.0%
github.com/prebid/prebid-server/v3/adapters/zeta_global_ssp/zeta_global_ssp.go:88:	MakeBids		94.7%
github.com/prebid/prebid-server/v3/adapters/zeta_global_ssp/zeta_global_ssp.go:122:	getMediaTypeForBid	100.0%
total:											(statements)		88.9%

@bsardo bsardo added the PBS 4.0 label Dec 10, 2024
@bsardo bsardo added the adapter label Jan 6, 2025
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.

6 participants