Cadent Aperture MX: alias cadent_aperture_mx to emx_digital #2912
Conversation
| @@ -1,6 +1,6 @@ | |||
| endpoint: "https://hb.emxdgt.com" | |||
| maintainer: | |||
| email: "[email protected]" | |||
| email: "[email protected]" | |||
There was a problem hiding this comment.
Sent an email to this email address for verification. Please reply "received".
There was a problem hiding this comment.
Is the contact email address for emx_digital to be changed as well?
There was a problem hiding this comment.
We've received and replied to the email address. Both bidder codes/names (cadent_aperture_mx and emx_digital) should be changed to this new @cadent.tv address.
| - video | ||
| userSync: | ||
| iframe: | ||
| url: "https://cs.emxdgt.com/um?ssp=pbs&gdpr={{.GDPR}}&gdpr_consent={{.GDPRConsent}}&us_privacy={{.USPrivacy}}&redirect={{.RedirectURL}}" |
There was a problem hiding this comment.
We tried validating this user sync URL but it does not seem to be working. Could you please check? Here is the URL that we are trying -
https://cs.emxdgt.com/um?ssp=pbs&gdpr=&gdpr_consent=&us_privacy=&redirect=https%3A%2F%2Fib.adnxs.com%2F%2Fsetuid%3Fbidder%3Dcadent_aperture_mx%26gdpr%3D%26gdpr_consent%3D%26gpp%3D%26gpp_sid%3D%26f%3Db%26uid%3D%24UID
There was a problem hiding this comment.
@EMXDigital Requesting to please address this comment.
There was a problem hiding this comment.
@gargcreation1992 we are looking into this now, will post an update shortly.
There was a problem hiding this comment.
@gargcreation1992 We've set the endpoint to return a 204 for the time being. Please let us know if this is sufficient for now to get this code merged in.
There was a problem hiding this comment.
@EMXDigital We would like to validate the user sync URL before this PR is merged.
There was a problem hiding this comment.
@EMXDigital I am still not able to see UID being set after calling the below endpoint -
https://cs.emxdgt.com/um?ssp=pbs&gdpr=&gdpr_consent=&us_privacy=&redirect=http%3A%2F%2Flocalhost%3A8000%2Fsetuid%3Fbidder%3Dcadent_aperture_mx%26gdpr%3D%26gdpr_consent%3D%26gpp%3D%26gpp_sid%3D%26f%3Db%26uid%3D%24UID
There was a problem hiding this comment.
@gargcreation1992 Depending on whether I'm hitting the URL fresh in an incognito browser (i.e., with nothing set on my browser yet), or hitting from an already identified browser, when I just hit that same endpoint in a browser, I am always ultimately 302-redirected to:
https://localhost:8000/setuid?bidder=cadent_aperture_mx&gdpr=&gdpr_consent=&gpp=&gpp_sid=&f=b&uid=[valid value]
Looks like it's filling in the UID [valid value] with an actual real value on my end. What are you seeing happening when you call that endpoint?
There was a problem hiding this comment.
I am getting 204. Here is the screenshot for your reference and below is the URL that I am trying to hit -
https://cs.emxdgt.com/um?ssp=pbs&gdpr=&gdpr_consent=&us_privacy=&redirect=http%3A%2F%2Flocalhost%3A8000%2Fsetuid%3Fbidder%3Dcadent_aperture_mx%26gdpr%3D%26gdpr_consent%3D%26gpp%3D%26gpp_sid%3D%26f%3Db%26uid%3D%24UID
There was a problem hiding this comment.
@gargcreation1992 I see from your profile that you are located in Pune,India. We have geolocation-based 204's. We are only planning on allowing business for now in North America. Are you able to run the same end point through a VPN that is mocking a North America geographic location? You shouldn't be getting a 204 if the Load Balancer thinks you're in North America.
There was a problem hiding this comment.
Thank you for your patience on this one @EMXDigital! We have tested this on our end and the url is working fine with North American location.
bsardo
changed the title
|
@EMXDigital Requesting you to please address the open comment. |
|
Resolved merge conflicts. |
No description provided.