CartPack LLC focuses on three major business niches, i.e. sales of ready-to-use packaging from own assortment, custom-made items manufactured according to client's technical specifications, merch and branded packaging for enterprises.
We use different methods of printing: printing on raw paperboard, laminating and more.
We produce custom boxes of specified shape, size and layout of the goods.
Ads budget - 4K UAH
Geotargeting - Ukraine ( excl. Cremia, Lugansk, and Donetsk regions)
Tracking of PPC performance by transactions and calls from Google Analytics
Objective - To get data sufficient to analyze the payback of this traffic source.
Tasks - Launch the searching campaign for ad groups specified by the Customer. Break down each ad group into an individual campaign for more accurate edits. Collect semantic core relevant to each ad group of the site. Work out keywords, to draw up a list of negative keywords. Write ad definitions describing competitive advantages of the Customer. Place three textual and one dynamic ad definition for A/B testing. To create and add extensions to improve of CTR ads.
Collection of keywords and negative keywords for ad groups of the site.
Launch of searching campaigns per each ad group individually. To set off targeting in Google Display Networks option since, we need the traffic from Search Network only.
Divide the keywords in each campaign into subgroups of different types. Use all types of matches separately. This is necessary so that the adjustments that we will make for optimization are as accurate as possible and do not spoil the results of other segments of the same campaign.
When launching ad campaign, create several text ads that differ from each other in their competitive advantages. Create one dynamic ad. This is necessary for A/B testing of the ads. Later on, ads with low CTR should be rewritten and improved.
We create add-ons to improve the CTR of ads.
During optimization work we work through queries, add negative words.
We make adjustments according to the established strategy, and modify it if necessary. It is better to do this as an experiment, so the campaign is not retrained and does not lose traffic and conversions.
In addition to adjustments for the rates and budget of the campaign, adjustments are also made for the segments of each campaign separately:
By location (when setting up, we immediately divide our targeting into separate areas and their centers. This is necessary in order to make adjustments to each area/center separately during optimization)
By day of the week (as well as the location itself, we specify when setting up separately for each day). For example, we need to advertise 24/7, but if we leave when configuring this point unchanged, then we can not make adjustments for each day separately. Therefore, we choose to advertise from Monday to Friday and add Saturday-Sunday separately.
You can also make adjustments to the time of each day separately. But to do this, you will need to change the show schedule manually, as shown in the example before.
According to the campaign outcomes with budget fixed for this source of traffic, we have got the following data:
Transactions - 64
Conversions (excl. transactions) - 406
Average price per transaction - 2,36 UAH
Income by ecommerce data - 86 045,37 UAH
Ads cost spent - 4 006,52 UAH
ROAS - 2150%
How useful was this post
Average rating 0 / 5. Vote count: 0
No votes so far. Be the first to rate this post.
As you found this post useful...
Follow us on social media!
Personal account - manager
Leads your projectsDives into the project, understand the specifics of the business and communicates with you in your languageManager contact with you at least once a week to show reports and discuss results
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
This cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites.
Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services.
Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
No description available.
This is set by Hotjar to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.
This is a Hotjar cookie that is set when the customer first lands on a page using the Hotjar script.