How to create your first campaign?
Here you'll find a short tutorial on how to create a campaign using Geeklab's Campaign builder.
At the beginning of creating the campaign, you have the option of manually enter all of the data or to fetch the data from an existing app/game in the app stores. You can also copy an old variant from previous campaign. If you get the data from app stores, you have the option to choose from which country and on what language the data will be fetched. Also, whether you get it from the App Store or from Google Play. (Huawei AppGallery will be available soon.)
We've subdivided the creation process into different modules. Even if you exit the campaign builder before submitting the campaign, all of your changes will be stored.
1. Select an app/project. This will help you in many ways after conducting campaigns. Select a name, category and sub-category and add an icon. This will be only visible for you team so don’t stress about the legitimacy off the app.
2. Short name of the campaign and description like: ICON_TEST_IOS_FB . The goal here is to keep your team informed about what the test is all about, but also so that when you return to the test later, you don't have to spend extra energy trying to remember what the test was all about.
3. Lastly choose which app store to use and on what language. Note: While all the languages are supported, not all of them have been whitelisted yet. If you'd like to use one that isn't currently available, please contact us. We'll make it available within 24 hours.
1. Name the first variation. Naming each variation so that all of your teammates understand what it represents. For example, if you have the actual store page and a few motivations to test, you can label the actual store page variation ‘Control' and others with motivations such as ‘achievement' and ‘competition.' (Only your team can see this.)
2. Add Title, Subtitle and app description for the app Notice: When fetching data from the store it will automatically fill the boxes with the text from the selected app store.
3. Categories have to be selected manually in any case. It will be visible in the look-a-like app page.
SIDENOTE: A campaign preview can be found on the right side of the campaign builder. It will show the changes made in the text and visual modules. It is not the final version of your product page.
Visuals can be easily dragged and dropped inside the white boxes. You may also drag and rearrange the order of the screenshots in the screenshots. Aspect ratios for the assets:
|iOS App Store||Google Play Store|
|Icon||1: 1||1: 1|
|Screenshot||2688 x 1242 or 1242 x 2688 |
Google allows you to use any sized visuals. To be eligible for recommendations in formats that use screenshots the resolutions must be
4 x 16: 9 or 9: 16 screenshots for apps & 3 x 16: 9 or 9: 16 screenshots for games.
|Video||2688 x 1242 or 1242 x 2688||You can use any sized videos here. Note: In the actual Play Store, the video is linked through YouTube. Standard ratio for YouTube is 16: 9 or 9: 16.|
|Feature art ||4: 1 ||4: 1 Will be the thumbnail of the video|
Smaller things like promotional text or reviews and ratings can be added or updated here. The age rating and privacy labels can also be updated and tested.
If you leave any of these blank, the default values will be used.
To add more variations, simply click the '+' symbol. It will create a new variation using all of the previous variation's data. All you have to do now is change the variation's name and the needed changes for a/b test.
Final Destination = User that clicks the ‘get’ button will be directed to this URL. It can be the actual store page, but also link to let’s say Testflight or survey.
Survey = Geeklab includes a built-in survey tool, which can be accessed via the ‘create a new survey' link or the ‘SurveyLab' tab in the sidebar. You can either use an existing template or create one from scratch.
After the survey is ready you can find it from the ‘Select survey’ box.
NOTE: When selecting the survey, it will give a ‘/survey/qwertyqwerty/’ URL for the final destination. Don’t add Geeklab.app domain before the survey.
Attribution = While pixels are not required, we strongly recommend using them to make paid UA as efficient as possible. You can find a thorough guide on implementing Facebook pixel from this link : https://geeklab.app/posts/ios14-pixel .
Lastly you can add demographics data for your variants. Here is another blog post to help setting up the demographics: https://www.geeklab.app/posts/demographics .
Now, submitting the campaign will show you what the differences between the variations are, as well as whether you are missing any needed information. You will be unable to submit the campaign until all needed steps have been completed.
CONGRATULATION ON YOUR CAMPAIGN!!!!🚀🎉
You now have tracking links for the campaigns and variations. These are available in the ‘Campaigns & Variations' side tab. You have tracking links for the entire campaign as well as for each variant separately. We recommend using the campaign tracking link if you intend to run a single ad for all variations. This will automatically divide the users into the variations randomly, resulting in more comparable statistics.
If you wish to use separate variants for separate ads you can find the tracking link for each variation under each variation. Tracking link will be used in ad campaign as the URL where the user will be sent after clicking on the ad.
Preview link allow you to view the look-a-like store page without collecting any data. Be careful not to use this link in the ad campaign.
To edit campaign after submitting it, you can edit each variation separately from the edit button found under each variation in 'Campaigns & Variations' side tab.
Awesome, everything should now be ready to begin sending traffic to you campaign. If you encounter any problems along the way don't hesitate to write in the live chat. Our team will shortly guide you through the problem.