Your website needs to have a user action (such as sending a form or at least clicking a button), and there needs to be 500 of these actions per month on average, with more actions per month being better.
Specific examples:
By returning all the money you paid for the service.
If your website's revenue or conversion rates (according to circumstances) do not increase in a way that would return the investment in 3 months after the changes are permanently deployed, we will return all the money you paid for the service.
Details:
The standard procedure is as follows:
— several possible methods of deployment are:
The testing takes at least 14 days, and requires achieving at least 500 conversions, done by users during the testing period.
All website improvements are implemented "remotely" – the changes are applied through JavaScript "Website alteration code", which is added to the website source code. No professional programming is usually required from your side.
Details:
These changes usually do not collide with "technical edits" of your development team (i.e. adding a new banner, adding "Add to favorites"–type of functionality, a discount voucher text field etc.). However, if you are planning extensive website edits (such as editing the structure of the HTML source code), it would be appropriate to inform Increver of such plans (at ).
Yes, before the test is launched, you will be shown the changes made to your website (visible only for you) for a final confirmation.
Yes, the changes are displayed in the mobile/tablet version of the website as well. The only exception are elements not found in these versions. Elements with a different appearance will be treated.
No. We strongly recommend you to remove the codes of other tools during Increver testing. As the services are technically similar, there is a risk of inappropriate collisions or influencing the data collection process.
After the testing phase, successful changes may be deployed as follows:
Increver code(s) can be placed almost anywhere in the source code of your website, but if you follow our guidelines, the website will display in a faster, more user friendly way – you will prevent "flickering" of the website, which might occur otherwise.
We strongly recommend you do not.
You risk website problems such as slower loading times, "flickering" of the website during loading, and more. This problematic behavior cannot be universally prevented because of how HTML and JS works.
If you need to use the Google Tag Manager or a similar tools, we can try to find a satisfying solution, but this might require further cooperation from your side.
Yes, these and similar orders, created typically before and immediately after the testing is launched (to check proper rendering and functionality of the website), can be deleted.
In detail:
Testing orders are created to check the functionality of the website. The orders come from e-mails beginning with "tester" and ending with the "increver.com" domain. All such orders can be deleted immediately. Testing orders are created immediately after the testing is started – it might be easier for you to delete them all at once. Please do keep the account created by a similar e-mail address, thank you.
The best way is to e-mail us (at ) with a link to a specific webpage with rendering issues, along with the name of your browser (incl. version). We recommend you to attach screenshots as well – it helps to speed up the process.
Yes. If you send us (at ) any number of IP addresses, we will add them to the blacklist, and exclude them from the testing.
That means any orders or other user actions ("conversions") completed during testing will not be included in the results of the test.
The removal of data associated with the excluded IP addresses takes place 2× a day – approximately at midnight and at noon, CET (data is deleted sequentially in all Increver tests – it is possible that admin will reflect the changes some time after midnight/noon).
This temporary data storage is used for functionality checks of the testing process. Since the excluded data is deleted regularly, no influence on the results is present.
If the question was asked hours or days after the testing process is launched:
It is too soon for any kind of evaluation. Depending on conversion type, at least a minimum of 250 conversions per variant is required (so at least 500 conversions are required for the very first evaluations). Constant number changes are okay – at first, with little data available, the results are a product of randomness.
It is only an "imperfection" of the recording of the website in the Smartlook application. Real visitors see the website correctly.
(Answer applies to the vast majority of the cases; as of now, this is true for all recorded cases.)
The changes which should be tested are generally chosen on the basis of the III model:
(Note: a similar model is the "PIE" model.)
If a successful change is a change with any positive results (that is not a statistically significant result over 95 % CTBO), then:
Approximately 60 % (6 out of 10) tested improvements have a positive result (not a statistically significant result over 95 % CTBO). That is a success rate comparable to the results of world-class experts of this area.
By connecting and overlapping the words representing the main idea of our service: increase revenue forever.
The result also resembles the "Inc." suffix, and the verb "rever(se)", indicating the guaranteed recovery of investing into Increver, ensured by increasing the revenue of your company by increasing the revenue of your company.
Increver is a lightning-fast, innovative company. Some of the answers may not be perfectly accurate – if you feel that is the case, please tell us at . Thank you! — the Team of Increver.com