PWAs in traffic arbitrage are more than just a page resembling an app store listing. They serve as a separate traffic delivery stage that can achieve installs, reopens, and push subscriptions before the user registers or deposits with the advertiser.
Benefits appear only when all stages are linked by a single attribution. If a PWA shows high click-to-install rates but FTDs cannot be traced back to the ad, the team optimizes an intermediate metric instead of revenue.
Our first choice for operating this funnel is DarkCore PWA Tracker. It connects the PWA builder, streams, click IDs, postbacks, custom conversion statuses, pixels, push, analytics, team access, and finance in one campaign context.
How the PWA Funnel Works
Facebook / TikTok / UAC
↓
Track Link and click ID
↓
PWA listing → install → open
↓
offer / advertiser
↓
registration → FTD → approve / redeposit
↓
postback → tracker → CAPI / Events APIEach arrow represents a contract between two systems. An error at any boundary can result in a beautiful top of the funnel and zero proven revenue.
What Happens on the First Click
The ad link must pass source parameters: campaign, ad set, ad, placement, creative, and platform click ID. The tracker adds its own unique click_id because the campaign ID describes a group of visits, not a single user.
Example of an incoming link:
https://track.example.com/click?campaign={{campaign.id}}&ad={{ad.id}}&fbclid={fbclid}After processing, the tracker creates an internal ID, for example dc_01K2..., and passes it on. Practical tables of macros are found in guides on Facebook URL parameters and TikTok macros.
Install Does Not Equal Offer Conversion
PWAs have their own events:
- install prompt display — and Chromium has two formats of it;
- install;
- first open;
- reopen;
- push subscription;
- push click.
The offer has others:
- registration;
- qualified lead;
- deposit;
- FTD;
- approve;
- redeposit.
These events cannot be combined into a single generic conversion. Otherwise, it is impossible to determine whether the installation, transition to the offer, or registration-to-deposit has dropped. DarkCore custom statuses allow preserving vertical values without reducing them to a single purchase.
Why PWAs Need Click IDs
Installs can happen immediately, while deposits may take hours or days. At the time of postback, the advertiser no longer sees the browser, PWA page, or original ad. The only reliable connection is the identifier passed forward and saved by the partner.
offer?aff_sub={click_id}The partner network saves the value in aff_sub, and after FTD returns:
https://track.example.com/p?click_id={aff_sub}&status=ftd&payout={payout}&transaction_id={conversion_id}The names of the parameters on the left and macros on the right may differ. The complete mapping described in the Postback URL guide is important.
Where Attribution Often Breaks
Between Ad and Track Link
The parameter was not added, did not substitute, or was lost after redirection. Check the actual URL after one test click, not just the template in the cabinet.
Between PWA and Offer
The PWA saved its own session but did not pass the tracker ID in the outbound URL. Installs are visible, but deposits become unattributed.
On Postback
The network returns a different sub ID, textual payout, or unknown status. HTTP 200 does not prove correct recording.
On Callback Repeat
The partner repeats the request after timeout. Without transaction ID and dedup, one conversion becomes two payouts.
On Status Change
registration, ftd, and approved come as an update to one entity or as different events—this needs to be determined in advance. Otherwise, totals will depend on the random order of callbacks.
Push as Part of the Revenue Funnel
Push notifications are not needed for the number of sends. A useful campaign has:
- selected audience;
- binding to PWA and stream;
- send and delivery event;
- open;
- subsequent conversion status;
- attributed revenue.
If the service shows only sent/open, it is impossible to assess the profit of retention. DarkCore Push Notifications uses the same PWA and conversion entities as routing and analytics.
PWA, Direct Link, and WebView
PWAs are not suitable for every combination. Sometimes Direct Link provides fewer steps, and store/WebView apps offer more native capabilities. The decision depends on the source, lifecycle, push, domain control, and production cost. For selection, use a separate comparison PWA vs WebView.
How to Test PWAs Before Budgeting
- Create one test Track Link with signed parameters.
- Complete install and first open on a real device.
- Check the outbound URL in the offer and actual click ID.
- Send registration with a separate transaction ID.
- Send FTD, payout, and currency.
- Repeat the same callback and confirm the absence of a duplicate.
- Change status and check history and totals.
- Send the event back to the ad platform with the same event ID.
- Check the report by campaign, creative, PWA, offer, and buyer.
- Record rollback for the domain, link, and postback.
What to Measure
| Stage | Main Metric | Quality Check |
|---|---|---|
| Click → PWA | landing load and unique clicks | Raw click is present once |
| PWA → install | click-to-install | Install is linked to the original click ID |
| Install → open | activation rate | Reopen does not create a new paid click |
| Open → registration | install-to-reg | Registration came from the correct offer |
| Registration → FTD | reg-to-dep | FTD has payout, currency, and transaction ID |
| FTD → platform | event delivery | Event name, value, and dedup are correct |
High click-to-install rates do not compensate for weak registration-to-deposit rates. Optimization priority should move towards the event linked to actual payout.
Where DarkCore Fits In
PWA Tracker stores installs, opens, push, and Direct Link alongside the campaign lifecycle. Streams manage the route and fallback, analytics segment the result, and finances continue the same set of facts in P&L and reconciliations.
This does not cancel out the external PWA service. But it provides an independent loop where it can be proven that app delivery actually brought FTDs, not just intermediate installs.
FAQ
What is a PWA in arbitrage in simple terms?
It’s an installable web app between an ad click and an offer. It can look and behave like an app, work with reopens and push notifications, but is delivered via the web.
Can you direct traffic straight to a PWA?
Technically yes, if the source, campaign policy, and infrastructure allow it. Operationally, it is safer to use Track Link, which records parameters, routing, and fallback to PWA.
What is more important: install or FTD?
Installs show the quality of an intermediate step. FTDs are closer to economics. The scaling decision should consider the entire funnel and payout, not just the install percentage.
How to choose a PWA builder?
Compare services by format, meter, domains, routing, postback, push, roles, and export in the ranking of best PWA services.