CPC & CPV campaigns
The CPC and CPV modules sell timed site visits and video views. The visitor must dwell for the required time before the reward is credited.
Offerwall & App Monetization Platform
Preads — launch your own profitable ad network
A self-hosted Laravel platform that turns a website or app into an offerwall. Publishers embed a wall or call the REST API, Preads tracks every click and conversion, credits the balance, and pays out on a monthly invoice.
What ships in the box
32
offer-network adapter classes
34
network records pre-loaded, ready for your credentials
31
payment processor drivers on one interface
8
bundled addons, enabled on install
68
tables in the shipped database schema
22
admin permissions across three roles
13
PHP extensions the installer verifies
27
editable transactional email templates
Counts are of the files and schema in the release you receive. Offer-network and payment gateway credentials are deliberately not included — you supply your own.
One platform, two sides of the same market
An ad network has two customers at once. Preads is built for both — advertisers who buy campaigns and publishers who monetize traffic.
One screen for CPV, CPC, Banner and Microjob campaigns: views delivered, spend, remaining balance and a seven-day trend.
Banner placements
Advertisers buy image and text placements. Delivery, impressions and clicks are logged; currency, targeting and campaign approval are admin-controlled.
Micro jobs
Advertisers post small tasks, workers submit text and image proof, and the advertiser or an admin approves it to release the reward.
Campaign analytics
A single dashboard reports views delivered, spend, remaining balance and a seven-day trend.
Country & device targeting
Offers are filtered by detected country and device, by category, and by the platform on the app.
Fraud-checked delivery
A weighted score combines IP reputation, device fingerprint and behavioural signals. Each check is written to a fraud score record so a decision can be reviewed afterwards.
Publishers embed a wall or call the REST API. Preads tracks every click and conversion, credits the balance, and pays out on a monthly invoice.
Web offerwall
Embed the wall in a page with one <iframe>. Users browse offers, filter by device, search, and open an offer detail view.
Native app monetization
Apps register with the android or ios platform and open the same wall in a web view, or fetch offers over the REST API and render them natively.
Content & link lockers
Gate a URL behind a set number of offer completions, with a per-device template and a session progress endpoint — or gate a link that redirects once the requirement is met.
Wallet & monthly payouts
Approved conversions credit the publisher's balance. On the 1st of each month, eligible approved rewards become an invoice against the saved payout method, which an admin approves.
Detailed reporting
Revenue and conversion reporting with date, network, publisher, app, device and country filters; a revenue chart against publisher cost; profit and margin; and per-network chargeback reporting.
API-driven integration
Skip the wall entirely. Fetch offers over HTTP, build your own UI, and let Preads handle tracking, crediting and reporting underneath.
What an offerwall actually costs to build
The offerwall is the visible page. The work is everything behind it.
Talking to dozens of networks
Every offer network has its own authentication scheme, offer endpoint and response format. Each one is a separate integration to write, test and keep working.
Trusting reported conversions
A conversion arrives as a postback from an untrusted caller. You have to match it to a click, decide whether it counts, and stop a forged postback from crediting a balance.
Onboarding publishers and reviewing their apps
Anyone can register. Someone has to decide which sites and apps get access, issue them credentials, and revoke them again when they abuse the wall.
Paying out without losing money
Conversions get rejected and charged back after the fact. A payout process that ignores that will eventually pay more than was ever earned.
Each of these is a solved problem inside Preads, with the code in the box rather than a vendor in the middle.
One platform, from click to payout
The path a conversion takes through Preads. Every step below is a real code path in the release.
-
1
Network offers are imported.
Adapters for each network fetch and import offers on a schedule
(
php artisan offers:auto-import) or on demand from the Network Hub. -
2
A publisher registers an app.
It carries a platform, a currency and an exchange rate, and it stays
pendinguntil an admin approves it. -
3
Credentials are issued.
The approved app receives its own
apiKey,apiSecretandpostback_secret. -
4
The wall is embedded, or the API is called.
An
<iframe>pointing at/wall, orGET /api/v1/offerswith the key and secret. -
5
An end user clicks an offer.
The click is recorded against the app and the end user, fraud-checked, and a
click_idis issued and carried into the network URL. -
6
The network posts the conversion back.
The inbound postback is matched by
click_id. Duplicate transaction IDs are rejected, and the payout recorded is read from the database, not from the request. -
7
The reward ledger is written.
A
conversion_rewardsrow splits the money three ways: operator margin, publisher payout and end-user reward. - 8 The balance moves. Approved conversions credit the publisher's balance; rejected ones reverse it and adjust any invoice already raised.
- 9 The publisher is told. An outbound postback fires to the publisher's URL with the transaction, reward and status, logged for delivery.
- 10 A monthly invoice is generated. On the 1st, eligible approved rewards become an invoice against the saved payout method, which an admin approves.
Monetization surfaces Preads covers
Each of these maps to a shipped module. Where a limit exists, it is stated rather than implied.
Web offerwall
Embed the wall in a page with one <iframe>. Users browse
offers, filter by device, search, and open an offer detail view.
Native app monetization
Apps register with the android or ios platform and
open the same wall in a web view, or fetch offers over the REST API and
render them natively.
Surveywall
A second wall filtered to offers categorised as surveys, with its own route and its own embed.
Content lockers
Gate a URL behind a set number of offer completions, with a per-device template and a session progress endpoint.
Link lockers
The same gating model for a link, which redirects the visitor once the requirement is met.
Timed and video offers
The CPC and CPV modules sell timed site visits and video views. The visitor must dwell for the required time before the reward is credited.
Banner placements
Advertisers buy image and text placements. Delivery, impressions and clicks are logged; currency, targeting and campaign approval are admin-controlled.
Micro jobs
Advertisers post small tasks, workers submit text and image proof, and the advertiser or an admin approves it to release the reward.
An API-driven integration
Skip the wall entirely. Fetch offers over HTTP, build your own UI, and let Preads handle tracking, crediting and reporting underneath.
What this does not include.
Native mobile SDKs do not ship with this release. Mobile integration is the HTML
iframe or the REST API — a WebView in your app, or your own screen built on
the API.
What the platform actually does
Grouped by the job each part of the system performs.
Offer delivery and the wall
Offerwall, surveywall and partner walls
Three delivery surfaces: the full wall, the survey-filtered wall, and an iframe partner wall that hands traffic to networks configured for iframe mode.
Live filtering and search
Offers are filtered by detected country and device, by category, and by the platform on the app. The wall adds a search box and a device filter.
End-user identification
The publisher passes its own userId on every embed and API
call. Preads attributes clicks, conversions, balances and rewards to it,
which is what lets you run your own reward economy.
Conversion and reward history
A user-facing history view joins the user's clicks to their conversions and shows what each one earned and whether it completed.
Integration
REST offer API
GET /api/v1/offers authenticated by the app's
apiKey and apiSecret. Supports
country, platform, category,
limit, offset and
sort, and returns a structured success/error envelope.
Tracked click redirect
GET /api/track records the click, runs the fraud check, and
302s to the offer URL with {click_id} substituted into it.
Your userId and four aff_sub slots are carried
through the whole flow.
Inbound postbacks from networks
A single /api/postback endpoint receives every network. It
resolves the click from any of nine accepted parameter names, routes the
request to the handler for that click type, and answers in the plain-text
form networks expect.
Outbound postbacks to you
Set a postback URL per app and Preads calls it on conversion with
{user_id}, {transaction_id},
{offer_name}, {payout}, {reward},
{status}, {country} and
{aff_sub}–{aff_sub4}. Every attempt is
logged with its response.
The whole web integration
<iframe
style="width:100%; height:800px; border:0; padding:0; margin:0"
scrolling="yes" frameborder="0"
src="https://your-domain.com/wall?apiKey=YOUR_API_KEY&userId=YOUR_USER_ID"></iframe>
Replace YOUR_USER_ID with your own user identifier on every
request. The same snippet works for /surveywall. No SDK, build
step or JavaScript bundle is required for web integration.
Offer networks
34 network records ship pre-loaded, covering both integration modes. Each one is a configuration screen: you paste the credentials from your own account with that network, then import its offers.
API mode — 28 networks
- AdGate Media
- Lootably
- CPAGrip
- CPALead
- Adtowall
- PrimeWall
- Torox
- Offery
- Revlum
- TaskWall
- UpWall
- Notik
- Farly
- HangMyAds
- AdBreak
- Admantium
- AdSwed
- KiwiWall
- Adscend Offers
- Wannads
- Ogads
- CPXResearch
- Adgem
- AyetStudios
- CPIDroid
- Vira
- Abluemedia
- Skyup
Iframe mode — 6 networks
- BITLABS
- Monlix
- Pubscale
- Playtimeads
- Gemiad
- Pixylabs
Network names are the records included in the schema. Whether a given network pays you, and how much, depends on your own account with them and on the traffic you send.
Publisher management
Accounts, apps and review
Publishers register, verify their email, and submit apps for review. An admin approves, rejects with a reason, or suspends. Status is checked on every request, so a suspended app stops working immediately.
Two-factor authentication
TOTP with a QR code and recovery codes, or an email code as the second factor, for both admin and publisher accounts. With login history and account lockout after repeated failed attempts.
Referral programme
Every publisher gets a referral code. A percentage of the referred publisher's approved conversion revenue is credited to the referrer's balance and is eligible for payout like any other reward.
Self-service support
Publishers raise, reply to and close their own tickets with attachments. Admins assign, prioritise and change status from the same queue.
Fraud prevention
Risk scoring on clicks and conversions
A weighted score combines IP reputation, device fingerprint and behavioural signals. Each check is written to a fraud score record so a decision can be reviewed afterwards.
Device fingerprinting
The shipped fingerprint script collects browser and canvas signals, hashes them, and posts them in. Multi-account use of one device is detected from how many user IDs that device has been seen with.
IP intelligence
Six provider adapters are wired in — IPQualityScore, AbuseIPDB, IPHub, ProxyCheck, MaxMind and IPinfo — each tried in turn, with results cached. VPN, proxy, Tor and datacenter ranges are scored, and Tor exit nodes are blocked outright.
A review queue
Blocked clicks and conversions land in a pending queue with their score and flags, where an admin can approve, reject or block. Blocked devices and IP allow/block lists are managed from the same screen.
Money: revenue, payouts and accounting
Per-app currency and revenue share
Each app carries its own currency code and exchange rate to USD, so end-user rewards are denominated in the app's currency while the ledger stays in USD. Publisher revenue share is negotiated per publisher.
Monthly payout invoices
Payouts are invoice-based. On the 1st of each month, eligible approved rewards become an invoice against the publisher's saved payout method, with a configurable term, minimum, maximum, percentage fee and fixed fee.
31 payment processors
Card, wallet and crypto gateways all implement one interface, so enabling a new one is configuration rather than code. Per-currency minimums and charges override the platform defaults.
Chargeback handling
Network chargeback reports import as CSV per network and accumulate against the publisher, so reversals are visible rather than silently absorbed.
Administration
Three admin roles, 22 permissions
Super admin, admin and support. Every sensitive screen — settings, networks, offers, publishers, fraud, withdrawals, logs, system info — is gated behind a named permission, and only a super admin can move money.
Reporting
Revenue and conversion reporting with date, network, publisher, app, device and country filters; a revenue chart against publisher cost; profit and margin; postback delivery logs; and per-network chargeback reporting.
Branding without a code change
Site name, logo, favicon, social image and social-sharing tags are admin settings. Frontend themes can be uploaded and activated, and each theme's sections edited in place.
Auditable settings
Settings changes are versioned, diffable and revertible. Payment secrets are stored encrypted, and outbound postback URLs are validated as public addresses before they are saved.
Every screen, as it ships
Captured from the release. Select any image to open it full size.
Admin panel
Publisher panel
Advertiser panel
Offerwall and public site
Names and balances visible in these captures are demo data from a seeded installation. Your installation starts empty.
From purchase to a paying wall
The operator's path, then the publisher's, then the user's.
Install it
Upload the files, point a vhost at the public directory, open the site and complete the built-in installer: requirements, licence, environment, first admin account, site settings.
Connect your sources
Import the schema through the installer, then open the Network Hub and enter the credentials for the networks you have accounts with. Run the first offer import and the catalogue is live.
Approve publishers
Publishers register and submit their sites or apps. Review them in the admin, approve, and they get credentials and an integration snippet.
They embed the wall
One <iframe> in a page, or a call to
/api/v1/offers. Their userId rides along on
every request so rewards can be attributed to their own users.
Users complete offers
Clicks are recorded and fraud-checked. The network reports back, conversions are matched and approved or rejected, and the reward ledger is written.
Balances become invoices
Approved rewards credit the balance. The monthly job turns eligible amounts into an invoice, an admin approves it, and the publisher sees it in their wallet.
Two scheduled jobs are required.
Offer auto-import runs hourly and monthly payout generation runs on the 1st. Both
need a cron entry on your server:
The stack, as shipped
Standard Laravel, standard MySQL. Nothing exotic to host.
- Laravel 12
- PHP 8.2+
- MySQL — 68 tables
- Server-rendered Blade
- REST API with apiKey + apiSecret
- TOTP two-factor
- Rate limiting per surface
- 8 addons on a manifest
Money: one interface, many routes
Card, wallet and crypto gateways all implement one interface, so enabling a new one is configuration rather than code.
31 payment processor drivers
Card, wallet and crypto gateways, all on one interface.
35 gateway records
Shipped in the schema and imported by the installer.
Cards, wallets & crypto
All three kinds implement one interface — enabling another is configuration rather than code.
Per-currency rules
Per-currency minimums and charges override the platform defaults.
Exactly what you receive
The distinction on the right matters as much as the list on the left.
In the package
- Full source code — the complete Laravel application, readable and editable, with no obfuscated or compiled-only parts.
- The database schema — 68 tables, 71 settings, 34 network records, 35 gateway records and 27 email templates, imported by the installer.
- Eight addons — Content Locker, Link Locker, CPC, CPV, Banner Ads, MicroJobs, Payments and the System Updater.
- The admin panel — publishers, apps, offers, networks, analytics, fraud, payouts, settings, templates and pages.
- The publisher panel — apps, offers, conversions, clicks, postbacks, wallet, referrals and tickets.
- The advertiser panel — campaign creation and stats for CPC, CPV, Banner and MicroJobs.
- The offerwall front end — wall, surveywall, partner walls, user history and the public landing pages.
- 31 payment drivers behind one interface, each configurable from the admin.
- The built-in web installer — requirements check, licence, environment, admin account, settings.
- A frontend template and a template editor for restyling without a code change.
- 27 email templates with editable variables, preview and send logs.
- The System Updater — upload an update archive, take a backup, apply the schema diff.
Not included
- Offer-network accounts or credentials. All 34 network records ship blank. You need your own accounts, and eligibility to receive offers from them.
- Payment gateway credentials. The drivers are there; your merchant accounts are yours to open.
- IP-intelligence API keys. Six providers are supported; the keys are optional and configured by you.
- A hosted instance. You receive the application, not a running server. SSL and a mail transport are yours to set up.
- Native mobile SDKs. Not part of this release — mobile integration is the iframe or the REST API.
- Custom development. The code is yours to extend; the package does not include bespoke feature work.
- Revenue, traffic or approval guarantees. Earning depends on your traffic and the rates the networks you connect actually pay.
No admin credentials ship with the product.
The
admins table is empty on purpose. The installer creates the first
super-admin account you choose.
Live Demo
Look at the running product
The demo is the product, on a public domain, with seeded data so every screen has something in it. Walk the wall, the admin panel and the publisher panel before you decide.
- The public landing page and publisher registration.
- The offerwall itself, including the surveywall and the addon tabs.
- The in-product documentation a publisher reads after signing in.
- The integrated screenshots on this page were captured from an installation like the demo.
The demo is read-only and its data is not yours. Nothing you see there is a promise about revenue.
Quick access
Copy the URLs and the wall embed you will actually use. Preads ships no default admin credentials by design — the installer creates the first account for you.
Live demo
https://preads.hansaldev.com/
Documentation
https://preads.hansaldev.com/documentation
Wall embed — one iframe
<iframe style="width:100%; height:800px; border:0; padding:0; margin:0" scrolling="yes" frameborder="0" src="https://your-domain.com/wall?apiKey=YOUR_API_KEY&userId=YOUR_USER_ID"></iframe>
Read before you integrate
Publisher and integration documentation, served by the product itself at
https://preads.hansaldev.com/documentation. It is also included in the release, so you are not
dependent on the demo staying online.
Scope of the documentation.
This is integration documentation for publishers and advertisers. Installation,
configuration and administration are covered by the built-in installer's own
screens and the admin settings they write to, not by a separate buyer manual.
Licence, updates and support
Plain statements, including the parts that are limited.
Licence
You receive the complete source code and the right to run it on a server you control and modify it for your own operation.
The product is sold as a regular licence for a single installation. You cannot resell or redistribute the source as a competing product. The full terms are presented and accepted during installation, so they are recorded on your own instance as well as here.
Updates
The System Updater is included. You upload an update archive and it backs up the database and files, applies any missing tables or columns, and copies the new code across.
Because the updater ships with the product, you are not dependent on a vendor connection to keep an installation maintained. Future releases are a commercial question for the vendor at the point of purchase; this page does not promise a lifetime update commitment.
Support
HansalDev provides support on a commercial basis, and you can raise a request through the contact form before or after purchase.
This page deliberately makes no response-time or 24/7 availability promise. The support ticket system inside Preads is for your publishers to raise issues with you as the operator, not a channel to the vendor.
Questions a technical buyer asks
Answered from what the release actually does.
Yes, in full. The application, the addons, the database schema and the assets. Nothing is compiled-only or obfuscated, apart from one third-party delivery script.
Upload the files, point your vhost at the public directory, make storage and bootstrap/cache writable, and open the site. The built-in installer walks through the requirements check, licence, environment, database import, first admin account and site settings. No command line is required to complete the install.
PHP 8.2 or newer with thirteen specific extensions, MySQL, a writable storage directory, working outbound HTTPS, and a cron entry for the two scheduled jobs. Node.js is not required.
Two ways. Embed it with an iframe pointing at /wall with your apiKey and your own userId, or call GET /api/v1/offers with your apiKey and apiSecret and render the offers yourself. There is no JavaScript SDK to install.
Apps register with the android or ios platform and then use the same iframe — typically a WebView — or the REST API to render offers natively. Native mobile SDKs are not part of this release.
A click is recorded against the app and your userId, gets a click_id, and that click_id travels into the network URL. When the network posts back, the postback is matched on that click_id to the original click.
Inbound: one endpoint accepts every network. It resolves the click from any of nine accepted parameter names, rejects a transaction_id it has already recorded, and routes the request to the handler for that click type. Outbound: set a postback URL per app and Preads calls it on conversion with the transaction, reward and status macros you can place in the URL.
Not by changing the amount. The payout recorded comes from the offer in the database; a value sent in the request is logged for comparison but not used. Postbacks are also fraud-scored, and a blocked conversion is forced to rejected.
Thirty-four network records ship pre-loaded, covering 28 API-mode and 6 iframe-mode networks. Each one is a configuration screen and ships without credentials, so you need your own account with the networks you want to use.
Yes. Adding a network means writing one adapter class against the importer base class and adding a record. The Network Hub, the scheduled import and the offer catalogue pick it up from there.
Approved conversions credit the publisher balance. On the 1st of each month, eligible approved rewards become an invoice against the payout method the publisher saved. An admin approves it. Minimums, maximums, fees and the payout term are all configurable.
Revenue, conversions, clicks, conversion rate, earnings trends, and breakdowns by app, offer, device and country, plus postback delivery logs and network chargeback reporting. It does not report impressions, eCPM or EPC, and there is no export for publisher conversion data.
Yes. Weighted risk scoring on clicks and conversions across IP reputation, device fingerprinting and behaviour; six IP-intelligence provider adapters; hard blocking of Tor exit nodes; multi-account detection per device; and an admin review queue with approve, reject and block actions.
Yes, without touching code. Site name, logo, favicon and social image are settings. Frontend themes can be uploaded and activated, and each theme section edited from the admin.
Yes, in the release, and it is also online. It is integration documentation: API access, parameters and response, postbacks, content lockers and link lockers. Installation is covered by the installer itself.
Support is available on a commercial basis and can be arranged before purchase. No response-time or 24/7 commitment is stated here, because none has been contracted.
No minimum to register or integrate. Payouts are subject to the minimum threshold you configure in Payment Settings, and earnings depend on your traffic and on what the networks you connect actually pay.
The licence covers one installation. Running several separate public instances is outside it. If you need a multi-tenant arrangement, raise it with HansalDev before you buy.
One price, for the source code
A single commercial licence. No per-publisher fees, no revenue share to us.
Single Licence
Popular
-16%
Version 2.4.0
Preads — Offerwall & App Monetization Platform
Complete source code, one commercial licence, one installation.
$299.00
$
250
USD one-time
- Full source code
- 68-table schema
- 8 addons included
- 32 network adapters
- 31 payment drivers
- Web installer
- Documentation
- System updater
- Admin & publisher panels
- Fraud detection
One-time payment. Taxes, if any, are added at checkout. Your own offer-network and payment-gateway accounts are a prerequisite, not part of the price.
The regular licence covers one installation. For a multi-instance arrangement, raise it with HansalDev before you buy.
Customization
Shape Preads around your workflow — quoted per project.
The package ships without bespoke feature work, but the code is yours to extend — and HansalDev can extend it for you. Common requests drawn from the same codebase:
- A custom frontend theme, built and editable in the template editor
- A new offer-network adapter against the importer base class
- Extra payment drivers on the same one-interface pattern
- Integration into your existing stack or API consumers
Scoped and agreed with you before any work starts. Not a promise of a fixed price — the quote follows the conversation.
New Project
Commission a new build from the HansalDev team.
Rather than adapting an existing script, start a dedicated engagement: a new product planned, designed, built and documented for your market.
- Scope workshops around your monetization model
- The same Laravel foundation this page documents
- Milestones agreed up front, code handed over in full
- Post-launch support available commercially
Tell us the market, the revenue model and the integrations — we reply with how we would scope it.
Other products
Best seller
Save $14.00
GPT & Rewards Platform
VibeCash
Launch your own GPT rewards website: offerwalls, surveys, tasks, referrals, cashouts and gamification with a full admin panel.
Launch your own profitable ad network
Get the source code, install it on your server, connect the networks you already have accounts with, and start approving publishers.