Adgebra Help Center
About usFAQsAdvertisersPublishersLoginBlog
  • About Us
  • Getting Started
    • General
      • Why Advertise with Adgebra
      • Type of Accounts
      • Registration
      • Ad Formats
      • Adgebra Audience
      • Prepaid/Postpaid Accounts
      • Training & Support
    • Adgebra Wallet
      • Payment Methods
      • Payments T&C
    • Account
      • Details
    • Brand
      • Brand Specifications
      • Pixel Types
      • Postback Tracking
      • Adgebra Pixel using GTM
      • Blocking
    • Campaign
      • Information
      • Strategy
      • Scheduling & Targeting
      • Pricing & Budget
      • Blocking
      • Adding Creative
    • Troubleshooting
      • Campaign is not delivering
      • The campaign was running previously but has now stopped delivering.
      • The campaign is delivering, but not at its full potential.
      • Campaign Over-delivery
      • The campaign is not tracking conversions
      • Conversion Discrepancies
    • Creative
      • Creative Specifications
      • Impression Tracker
    • Reports
      • Placement Analysis
      • Detail Analysis
      • Trend Analysis
      • Conversion Analysis
      • Widget Analysis
      • Translation Summary
      • Partner API Report
      • Partner Widget API Report
    • Publisher
      • DIY Partner
      • Tag Placements
      • Partner Payment T&C
      • Partner API Integration
    • Site
      • Site Addition
      • Site Informartion
      • Ad Widgets
    • Traslator Guide
    • Adgebra oRTB
      • Overview
      • Terminology
      • RTB Ecosystem
      • RTB Basics
      • Win Notifications & User Syncing
      • Object Specification
    • Adgebra API Reports
      • Account Report API
      • Partner Report API
Powered by GitBook
On this page

Was this helpful?

  1. Getting Started
  2. Adgebra oRTB

Win Notifications & User Syncing

The platform supports two OpenRTB implementations:

1. OpenRTB without “nurl” (default). In this scenario, “nurl” field is absent in bid responses and the system will record wins

automatically when impression happens. SSP has to replace ${AUCTION_PRICE} before the ad markup is being rendered.

2. OpenRTB with “nurl”. Win URL is represented as a separate bid response field. In case of 2nd price auction usage, “nurl” has

to be called before the actual impression happens.

SSP Initiated User Matching

To sync a particular user with AdKernel, the SSP should initiate the user to call for image or iframe pixel using the following URLs:

Image: <img src='//sync.adkernel.com/user-sync?zone={zone_id}&t=image&r=SSP_REDIR_URL' style ='display:none' width='0' height='0'></img>

Iframe: <iframe src='//sync.adkernel.com/user-sync?zone={zone_id}&r=SSP_REDIR_URL' style ='display:none' width='0' height='0' frameborder='0'></iframe>

Where:

- SSP_REDIR_URL is URL-encoded redirect URL to SSP that shall include macro {UID} which will be replaced with buyer’s userId;

- {zone_id} - SSP-specific zone id.

After performing successful user sync, SSP needs to sent DSP’s user id in user.buyeruid bid request field.

PreviousRTB BasicsNextObject Specification

Last updated 7 months ago

Was this helpful?