Make better communication between App and Revive Ad server. You can use your own SDK to get ads from Revive Ad server using this API. dJAX API like middleware between Revive Ad server and SDKs.
Custom AdRequest REST API for Mobile SDK plugin is used to make better communication between App and Revive Ad server. You can use your own SDK to get ads from Revive Ad server using this API. dJAX API like middleware between Revive Ad server and SDKs.
Following Device based Targeting get supported
User IP [Sample: GT-I9300I]
deviceModel [Sample: GT-I9300I]
PackageName [Sample: android.adro.ads]
osVersion [Sample: 4.2]
location [Sample: 35.6970472,51.0696206]
Ad Request send from SDK to revive ad server using dJAX API along with zone id and targeting parameters mentioned.API process the ad request and match the targeting criteria and return the valid ads in JSON response.
Banner Response format:
Banner URL
Banner Text/Title
Banner Description
Banner Size
Click URL
Impression tracking url
Message described in Banner level
Output Response
Video ads:
Video ads return in VAST Response
Supports for Vast 2.0
Video event tracking reported
Linear & Non linear ads supported
Frequently Asked Questions
How does the dJAX API act as middleware between a mobile app and Revive Adserver?
+
The plugin inserts a custom REST API layer between your mobile SDK and Revive Adserver. When your app's SDK sends an ad request, it goes to the dJAX API endpoint along with the zone ID and targeting parameters. The API processes the request, matches it against the targeting criteria configured in Revive Adserver, and returns the winning ad in a JSON response — without your SDK needing to communicate directly with Revive's default delivery system.
What targeting parameters can be passed through the API with each ad request?
+
The API supports a comprehensive set of mobile targeting parameters including device type, handset manufacturer, OS and OS version, handset model name, screen width and height, telecom operator, connection type, data speed, time zone, user agent, bundle ID (App ID), and custom parameters such as age and gender. Device identifiers including DIDSHA1 and DIDMD5 are also supported for audience matching.
What is the difference between this plugin and the standard Revive mobile SDK?
+
The standard Revive mobile SDK delivers ads using Revive's default ad tag system and supports a fixed set of ad formats and targeting options. The Custom AdRequest REST API plugin allows developers to use their own proprietary SDK and structure ad requests in JSON format with full control over the targeting parameters passed. This is suited for teams who have built custom mobile ad delivery frameworks and need Revive Adserver to act as the backend decisioning layer.
What reporting capabilities does the API provide?
+
The plugin's API includes reporting features that allow you to track impressions, clicks, conversions, and revenue generated from mobile ad delivery. Publishers and developers can monitor ad performance, user engagement, and revenue statistics to make data-driven decisions for optimising mobile ad strategies within their applications.
Does using this plugin affect the size or performance of the mobile application?
+
No. Integration of the Custom AdRequest REST API does not cause any significant increase in app size. The API is lightweight and REST-based, meaning it communicates via standard HTTP calls without requiring heavy SDK libraries to be bundled into the app — making it suitable for performance-sensitive mobile applications.
