We have discovered a loophole in Facebook: PWA 2.0 (3)
It has been a while since our Research & Development team started looking for a solution that would help stabilize the workflow on Facebook (and some other sources).
App bans, faulty deep links, botched app builds, distorted distribution and swarms of fraudsters reselling the apps — are few of the pains any affiliate knows only too well. We really wanted to find something new that will allow us to do without the apps. And we see two solutions:
Spoiler: we have opted for the second one and found a loophole in the Facebook mechanisms. Now we are ready to present you with a case-guide for using PWA with event optimization.
A friendly warning: you will not find 300 ROI in the cases below 
But earning money wasn't our goal this time. We needed to test out the technology/solution and demonstrate it to you. And we did it!
And now let's dive into the PWA, event optimization, and what we have discovered.
Step 1: hypothesis
So, we assumed that PWA can be used as an alternative to Webview applications. Alfaleads has already had a lot of work done in this direction — we have our own construction tool. Moreover, our PWA can send push notifications to users.
Step 2: development
However, something was missing — we still couldn't set up event optimization in FB. And now can proudly announce that we have finally managed to implement the event postback and we can work with event optimization.
This is how it works: there is a landing page that redirects users to PWA. This landing page has pixel tracking and powerful cloaking that filters out bot traffic. From the landing page, user goes to the "store" PWA page, which looks just like the well-known Google App store. The user downloads the PWA which has a Webview with the offer inside. Then he registers and makes a deposit. These events are posted back to our tracking platform, and we send them to Facebook from there.
Facebook has a learning mechanism that is trained to find the audience that performs target actions more often. For example, optimization for registration will increase the number of registrations and the CTR. As a result, the number of deposits should rise as well.
Now we only have to prove that the approach works in real life.
Step 3: practical application
In our experiment we took a Russian casino offer and compared the traffic flow in two cases: a) when driving directly to the offer page (with a pre-landing page); b) when driving to a Google Play replica page with a link to PWA.
Why don't we compare well-known Webview apps and PWA? It is no secret that a Webview app has a lifespan of 3–5 days on average (or none at all). Traffic loss is huge, accounts get banned, etc. For this reason, we turn to alternative schemes.
At the same time, we are studying performance of this approach for a different GEO — Australia. As soon as we have enough data, we will make a case demonstration for you.
Driving traffic directly to the landing page
We have implemented optimization for deposits and registrations on our landing and pre-landing pages. We tested out two options: using our own pre-landing page or choosing one from the advertiser database. Technical issues grew in number dramatically when we used our pre-landers and domain: the clickID was getting lost, the layout of pages was distorted, some devices displayed the pages incorrectly. Multitudes of variables undermine stability. Thus, it was necessary to monitor the process at all times. Therefore, it is much easier to use landing pages provided by the advertiser.
Launch algorithm:
Results:
Optimization for deposits did not work well, as the Facebook pixel does not have enough events with only one account. But optimization for registration went successfully: with the decrease in spending the number of registrations remained stable.
For our PWA experiment, we implemented only optimization for registration. We noticed that with PWA there were more deposits and the completion rate was higher. Considering the possibility of sending push notifications we get the maximum effect!
Results:
The results were more impressive than on average for classic Webview applications. For comparison, here is the average data for the applications: inst2reg = 1:10, reg2dep = 1:8.5. However, here you need to consider the installation price — in case of PWA it may be higher than with usual applications!
To confirm that the solution is also viable for large volumes of traffic, we attach statistics from our Alfamedia media buying agency.
Based on the results of our experiment, we came to the following set of conclusions:
Alfaleads provides affiliates with:
To repeat (and, of course, improve!) our case and start working with PWA, contact your affiliate manager — he will give you access to the construction tool and supply you with everything you need to start the journey. We provide a ready-made solution for PWA campaigns — you just need to choose the right offer!
Want to learn more about PWA? Find more information here!
Thanks, interesting to read.
I already enjoyed Marys speech at the affiliate virtual summit in April about Facebook
Originally Posted by twinaxe
I already enjoyed Marys speech at the affiliate virtual summit in April about Facebook
Home > Paid Traffic Sources > Facebook & Instagram