WebView & Direct Link
Below is the integration guide for WebView and Direct Link
Although we provide support for WebView or direct-link integration, this is not the recommended approach. Whenever possible, you should integrate our official SDK instead.
Using the SDK ensures:
Better tracking accuracy — SDK handles device signals and user sessions more reliably
Stronger fraud protection — Anti-fraud checks and security layers are baked into SDK flows
Automatic updates — You benefit from improvements and bug fixes without touching your integration
Faster integration — No need to manually handle WebView setup, edge cases, or command bridges
WebView or direct links should only be used in special cases where SDK usage is not possible (e.g., HTML-based apps, low-code platforms). Even then, you must strictly follow the rules in this guide to ensure reliability.
Your offerwall can be integrated either with our SDK or by embedding the URL directly via WebView. If you’re using WebView or direct links, please follow the instructions below to avoid common issues.
1. Building the Offerwall URL
You must append correct parameters to ensure tracking and reward delivery.
Base URL:
https://sdk.mychips.io/contentRequired Parameters:
content_id– your assigned adunit IDuser_id– a unique user ID on your side (can be a hash or UUID or numeric)webview– bool
Optional But Highly Recommended
gaid– Google Advertising ID is a unique, randomly generated identifier assigned by Google to Android devices, which enables advertisers to track and measure users’ advertising interactions across apps and services.idfa– Identifier for Advertisers is a unique, randomly generated code that Apple assigns to each user’s device, allowing advertisers to monitor and analyze advertising-related activity.gender–m,f, oroage– user age (numeric 0-100)os_version– version of the os
Final URL Example for iOS users:
Example final URL with values replaced for iOS users:
Final URL Example for ANDROID users:
Example final URL with values replaced for ANDROID users:
Best Practice WebView
These must be followed when integrating the offerwall via WebView or a direct link. Failure to implement them may result in broken reward flows, missing tracking, or bad UX.
✅ Rule
❓ Why It Matters
🛠 What to Do
content_id & user_id &webview=1 are mandatory
Without them, users can't be identified and rewards can't be tracked
Append both in the URL: ?content_id=...&user_id=...
gaid &idfa are highly recommended.
We highly recommend including the GAID or IDFA parameter, depending on the platform, as this helps improve eCPM performance.
Append the parameter to the URL depending on the platform:
iOS:
?idfa=...Android:
?gaid=...
Enable JavaScript in WebView
Required for rendering and logic of the offerwall
webView.getSettings().setJavaScriptEnabled(true);
Enable DOM Storage
Enables session/localStorage — often used by the offerwall
webView.getSettings().setDomStorageEnabled(true);
Disable WebView cache
Prevents bugs from loading outdated or broken content
webView.getSettings().setCacheMode(WebSettings.LOAD_NO_CACHE);
Open api.mychips.io/redirect URLs in external browser
These are used for conversion tracking and if not well implemented could affect trackability
Open External Browser
Handle mychips:// URL scheme
Bridge used by offerwall to trigger native logic (e.g. reward sync)
override and ignore this schema
Add a custom error page on failure
Prevents user from seeing a blank screen when offline or error occurs
Override onReceivedError() and show fallback HTML content
Implement proper back navigation logic
Prevents broken UX and enables going back within the WebView
close activity on back press when url contains "home"
Support file uploads in WebView
support require file/image upload/
Use WebChromeClient.onShowFileChooser() and route result back via onActivityResult()
Do not preload
preloading will affect impression tracking and impact eCPM negatively
Code Example
Below are sample codes for different languages.
Note: Replace the values of the Offerwall URL parameters with your actual data. The values used in the code example are for demonstration purposes only.
Last updated