Once in the process of new lander creation, I was changing the titles, editing texts, trying different inscriptions on the buttons, and I realized that changes on the landers are usually inconspicuous. Yet you have to create new folders and files. After a month of an active work, you have of all sorts of landers with names like var2-iter1-2, white3-iter2-3, scanner4-button5-text1. Besides, you have to translate the landers very often, and it is a hard task. You will have to copy the text from each and every landing separately, search for it in the code or open each of the texts in the browser and copy from it.

I decided to optimize the process of landers creation, preserving and translation. I wrote a index.php script for myself, which was not that very difficult. It was written for the imobitrax tracker, but there is no need to including lp_track.php  in Voluum as the parameters are set in a different way. But it is not hard to adapt them for this service.

Here is a version as an example:
 


What does this script do?

This file is essential for the landing. PHP generates its code like a CMS generates website’s code. It can be considered as a mini-CMS.

The script makes a lander take into account the received parametres.

For example:

http://domain.com/index.php?h=1&txt=5&btxt=1&tmp=2&lg=EN

Parametre h=1 – tells the script to take heading 1 from the database

txt=5 – to take text 5

btxt=1 – to take text of the button 1

tmp=2 – to use a template of lending 2

lg=EN – texts in English

Where does the script take information from?

I refused to complicate the script and overload the server. That is why the database is just one file for each language.

There are several files en.php es.php in data folder  (source code is at the end of the article). In each of the file, there is information.

By the way, you can set any parametres you want here which you will use in your landing (the color of the background, the color of the text, etc.) but I recommend to keep it simple and not exaggerate.

The templates of the landings are in the templates folder. Each template is in its own folder, with a picture.

The following macros are used:
{h1} – place for the heading
{text} – place for the text
{btext} – place for the text on the button

The script chooses the appropriate template (by the number in launching parametres) and replaces texts for macros with the numbers from language parametres.

Usage

We collected a good base of texts, created a couple of templates and decided to make MVT-testing on the rotating campaign. Our procedure:

Let’s say we want to test 5 headings with all other parameters equal.

As a result, we get the following links:

http://domain.com/index.php?h=1&txt=5&btxt=1&tmp=2&lg=EN
http://domain.com/index.php?h=2&txt=5&btxt=1&tmp=2&lg=EN
http://domain.com/index.php?h=3&txt=5&btxt=1&tmp=2&lg=EN
http://domain.com/index.php?h=4&txt=5&btxt=1&tmp=2&lg=EN
http://domain.com/index.php?h=5&txt=5&btxt=1&tmp=2&lg=EN

Instead of copying the landers and changing their text, we just copied the link in 2 seconds and changed the required parameters.

You can make your own set of parameters and test in your own way.

For example, firstly templates, then texts (approaches), then headings, then text of the button, then the colour of the button, then the colour of the background. When you have it all in the database, these manipulations will not take much time, even if you have ten campaigns.

P.S. It is primarily a concept, a technical strategy, an approach. In autumn I will launch my own tracker which will have all the functionalities to keep a database for different landings’ parts, their generation according to a particular scheme, with a good set of templates for various verticals, which enables you to edit them and add your own.

Thanks for your attention 🙂

https://www.sendspace.com/file/f2cae4 – the source code