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

Bidder user sync configs #2

Merged
merged 2 commits into from
Jul 6, 2021
Merged

Bidder user sync configs #2

merged 2 commits into from
Jul 6, 2021

Conversation

VeronikaSolovei9
Copy link
Collaborator

@SyntaxNode
Added bidder user sync configs.

I found some user syncers without userSync urls:

"adocean", adapters.SyncTypeRedirect
"adtarget", adapters.SyncTypeIframe
"adtelligent", adapters.SyncTypeIframe
"adxcg", urlTemplate, adapters.SyncTypeRedir
"audienceNetwork", adapters.SyncTypeRedirect
"bmtm", adapters.SyncTypeRedirect
"criteo", adapters.SyncTypeRedirect
"dmx", adapters.SyncTypeRedirect
"gamma", adapters.SyncTypeIframe
"invibes", adapters.SyncTypeIframe
"mediafuse", adapters.SyncTypeIframe
"rtbhouse", urlTemplate, adapters.SyncTypeRe
"rubicon", adapters.SyncTypeRedirect
"verizonmedia", adapters.SyncTypeRedirect
"viewdeos", adapters.SyncTypeIframe
"vrtcal", adapters.SyncTypeRedirect

Also there are some configs where userMacro is empty:
"amx"
"connectad"
"consumable"
"conversant"
"gumgum"
"ix"
"pubmatic"

Please double check next configs, not sure about url:
"adnxs"
"grid"
"lockerdome" -> don;'t know about what url should be in this case
"trustx"

Copy link
Owner

@SyntaxNode SyntaxNode left a comment

Choose a reason for hiding this comment

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

I found some user syncers without userSync urls:

That's fine. We no longer require code to enable user syncing for adapters. Hosts which configure user syncing for these adapters will need to update their config to keep them working since we loose information on the sync type. I'm not sure if that's a big deal.

key: "adnxs"
redirect:
url: "https://ib.adnxs.com/getuid?{{.RedirectURL}}"
userMacro: "$UID"
Copy link
Owner

Choose a reason for hiding this comment

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

This is the correct content. The key and redirect fields need to exist on the same indentation level:

userSync:
  key: "adnxs"
  redirect:
    url: "https://ib.adnxs.com/getuid?{{.RedirectURL}}"
    userMacro: "$UID"

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Fixed. I also checked other "keys" - this is the only one case with wrong formatting

@SyntaxNode
Copy link
Owner

SyntaxNode commented Jun 30, 2021

Also there are some configs where userMacro is empty:
"amx"
"connectad"
"consumable"
"conversant"
"gumgum"
"ix"
"pubmatic"

The AMX adapter looks to have strange behavior. I've email them to work through it. The others append the uid to the end of the redirect url instead of using a macro. I'll add a note to the default redirect url mentioning this important behavior. I think that's better than copying the redirect url template to each of these adapters, although it would prevent accidental breaking changes in the future. What do you think? We could also add a comment to these adapters too, something like:

userSync:
  iframe:
    url: "https://cdn.connectad.io/connectmyusers.php?gdpr={{.GDPR}}&consent={{.GDPRConsent}}&us_privacy={{.USPrivacy}}&cb={{.RedirectURL}}"
    userMacro: ""
    # connectad appends the user id to end of the redirect url and does not utilize a macro

or something like this with the user macro omitted:

userSync:
  iframe:
    url: "https://cdn.connectad.io/connectmyusers.php?gdpr={{.GDPR}}&consent={{.GDPRConsent}}&us_privacy={{.USPrivacy}}&cb={{.RedirectURL}}"
    # connectad appends the user id to end of the redirect url and does not utilize a macro

userSync:
redirect:
url: "https://lockerdome.com/usync/prebidserver?pid="+cfg.Adapters["lockerdome"].PlatformID+"&gdpr={{.GDPR}}&gdpr_consent={{.GDPRConsent}}&us_privacy={{.USPrivacy}}&redirect={{.RedirectURL}}"
userMacro: "{{uid}}"
Copy link
Owner

Choose a reason for hiding this comment

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

The LockerDome adapter is using the PlatformID in an unintended way. I suggest we comment out their userSync and add a comment:

# lockerdome requires a platform id for their user sync process. replace <<PlatformID>>
# in the url below and uncomment the userSync section to enable.
#
#userSync:
#  redirect:
#    url: "https://lockerdome.com/usync/prebidserver?pid=<<PlatformID>>&gdpr={{.GDPR}}&gdpr_consent={{.GDPRConsent}}&us_privacy={{.USPrivacy}}&redirect={{.RedirectURL}}"
#    userMacro: "{{uid}}"

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Modified content to comment.

@SyntaxNode
Copy link
Owner

Please double check next configs, not sure about url:
"adnxs"
"grid"
"lockerdome" -> don;'t know about what url should be in this case
"trustx"

I left comments for adnxs and lockerdome. The others look correct.

@sonarqubecloud
Copy link

sonarqubecloud bot commented Jul 1, 2021

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@VeronikaSolovei9
Copy link
Collaborator Author

Sorry I closed it accidentally, changed it back to "Open"

@VeronikaSolovei9
Copy link
Collaborator Author

userSync:
  iframe:
    url: "https://cdn.connectad.io/connectmyusers.php?gdpr={{.GDPR}}&consent={{.GDPRConsent}}&us_privacy={{.USPrivacy}}&cb={{.RedirectURL}}"
    userMacro: ""
    # connectad appends the user id to end of the redirect url and does not utilize a macro

^ Added a comment at the end of file for syncers with empty userMacro

@SyntaxNode SyntaxNode merged commit 5f74c4c into usersync_v2 Jul 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants