Digital Marketers are responsible for all inbound marketing.
Note: Some of the following labels only exist on the Digital Marketing Programs project level.
#digital-marketing: General digital marketing conversation and questions#dmpteam: Discussion for DMP team membersWe use Google dataStudio to create an easy to share and repeatable process for sharing analytics data for about.gitlab.com. dataStudio allows us to combine data from Google Analytics, Google Ads, and a variety of other sources to create reports with key data for any GitLab team.
When we connect data from Google Sheets everyone on the DMP team needs to able to access and edit data as needed. To accomplish this we add all Google Sheets used in dataStudio to the Shared Drive in the dataStudio sub-folder. Be sure you only share your Google Sheets in the shared drive because dataStudio does not currently support sharing data sources from shared drives.
Page field in this dataStudio report Page-level Google Analytics data.Landing Page field in this dataStudio report Google Search Console keyword lookup.Query field in this dataStudio report Google Search Console landing page lookup.If you would like to request a paid digital marketing promotion in paid search, paid social, paid sponsorships or other paid marketing to support your event, content marketing, or webcast, asset, etc. create an issue in the Digital Marketing Programs Repo and use the mktg-promotion-template
If you request a digital marketing promotion you probably also need a marketing campaign and should consult with the Marketing Program Managers.
LinkedIn Inmail campaigns are a good way to reach people at specific companies, industries, and more. They work best for inviting people to events and webinars if you do not have specific people in mind (unlike a Marketo campaign). If you would like to request an Inmail campaign as part of your markeing campaign, create an issue in the Digital Marketing Programs Repo and use the linked-inmail template.
Awareness Stage |
Consideration Stage |
Purchase Stage |
|---|---|---|
| Top of funnel:
Thought leadership, educational, informational, not GitLab-specific, high-level information on a subject, no product information |
Middle of funnel:
Customer, GitLab-specific |
Bottom of funnel:
Anything with a form-fill (trial, demos, analyst reports, reports, eBooks, webinars, whitepaper) |
| Content goals:
Prove that you understand the problem the visitor is trying to solve. People are looking for answers to questions, lists often work well here. They may also need education on what they need to know about their problem and our solution. This is a good place for thought leadership that does not mention GitLab. Any recorded videos should be very short -- 5 minutes or less is best. |
Content goals:
Prove we are better than competitors. Prospect is almost ready to become a lead. Almost. They want to be sure GitLab is the right choice. This is the evaluation stage, where people are doing a lot of research as to whether GitLab is the right fit. |
Content goals:
As personalized and persuasive as possible. Address possible objections or concerns about a purchase. Customer may need to explain GitLab to their boss. This is where we need to show how easy it is to become a customer and use GitLab. |
Content examples:
|
Content examples:
|
Content examples:
|
Please visit the content marketing handbook page for more information.
A process of collecting and analyzing data, formulating hypotheses, and conducting experiments to increase the percentage of website visitors that convert into leads or potential customers. Testing and experiments generally occur on website pages that include desired actions such as watching a product demo, signing up for a newsletter, or signing up for a free product trial. This also extends to email recipients in email marketing wherein the recipient responds to the main call-to-action (CTA) of an email, driving additional traffic to the website, and converting into a new customer or upsell a current customer.
Goals
In order to draw accurate conclusions from a test, a large data set (sample size, time) is required. Customer behavior is not always consistent and responses fluctuate between times, offerings, and segments (e.g. device type, location, new vs. returning visitors). Other considerations include seasonality, competitor landscape, and industry evolution.
When analyzing results, it’s important to take different segments into account. Testing one element may reveal statistical significance in one area and affect another poorly. For example, an increase in conversions on the website via desktop could cause a decrease in conversions for mobile and vice versa.
In order to iteratively improve the site, we should test all major site changes before implementing. Testing requires a control and a variant within the same time period, while holding all other variables constant. Using a/b testing tools will allow us to create tests that follow testing best practices and gather data about what works or does not work to encourage people to spend time on our site or have a conversion event. With testing, we can make informed decisions about what works for our audience and helps them reach their goals, and what works for us to help use meet our business goals.
Body
Send Time
Subject Line
Call-to-Action (CTA)
Rather than simply testing ideas that we feel are relevant, we focus on building a solid hypothesis using data and information to ensure we are testing a hypothesis with the best chances of conversion. Theoretically, there are two approaches to building a hypothesis:
ab-test template. Assign the issue to @sdaily.HP for the homepage. If you have an MVC update to any of the pages in the Doing column, contact @sdaily and we can scheduled tests around MVC updates or determine if updates can wait for tests to finish. Tests take 1 day to 4 weeks depending on traffic and conversion volume.Website pages with active tests running will have an additional script installed called an anti-flicker snippet. Without this script installed, visitors may experience the page flickering and briefly see the original page before the test loads. This can skew the results of the test and confuse visitors. Tests can and will run without the anti-flicker snippet installed, but there is a chance it running without can impact visitor experience.
To install the anti-flicker script, add google_optimize: true to pages with active tests.
We should link to resources that will help our readers. Be sure to include links to blog posts, guides, and other reference material. You can also include links to company or product websites if they are relevant to your topic. These links do not need to be "nofollowed" if they are informational.
However, we should use Google's guidelines on nofollowing links when we exchange a link for a product or service. It's also a best practice to ask for a nofollow link when we sponsor and disclose our links to sponsored content.
All URLs that are promoted on external sites and through email must use UTM URL tagging to increase the data cleanliness in Google Analytics and ensure marketing campaigns are correctly attributed. For a primer course, please see the training video. This explains the why and how of URL tagging.
Our internal URL tagging tool can be accessed on Google Sheets under the name "Google Analytics Campaign Tagging Tool" which can be found on the Google drive. You will also find details in this spreadsheet on what "Campaign Medium" to use for each URL.
UTM best practices: lowercase, not camelcase, and no spaces, .com or special characters (&*%$+#@, etc.) for new tags. if you need a new campaign medium, please check with the Digital Marketing Programs team as new mediums will not automatically be attributed correctly.
Regular website health checks should be performed. These checks are meant to ensure that there are no issues with the website that could cause issues with traffic to the site. These are the following things to check to ensure the health of the site:
Issues to look for in each of these tools:
Search Traffic > Manual Actions for any URLs that have been identified as spam or harmful content. Forward security warnings to the Abuse team and follow the DMCA complaint process with the support team.There are times we need to keep pages out of search indexes. For example, we might duplicate most of a page to improve conversion for an ad campaign. It's relatively rare to use this, but it's an important tool that helps us increase organic reach and paid advertising efficiency.
All pages are set to meta name="robots" content="index, follow" by default. To exclude a page from the index add noindex: true to the frontmatter, and this will set the robots metadata to meta name="robots" content="noindex, follow".
Occasionally we need to change URL structures of the website, and we want to make sure that people can find pages they need. We use 301 redirects to send people to the right URL when it's appropriate.
We will redirect URLs included in Google's search index. A simple test to see if a page is indexed is to search for the URL with a site modifier, site:url, using Google.
It's a best practice to reduce the number of internal redirects as much possible, which means we need to try and update links across about.gitlab.com when we change URLs. When you request a redirect you can indicate whether or not you were able to search across about.gitlab.com and update the links for a page that moved.
The Digital Marketing Programs team can set up and manage all redirects for about.gitlab.com.
To redirect an outdated page, open an issue with the set up a new redirect template in the Digital Marketing Programs project. You'll need to provide the following:
If you have any questions or concerns regarding your redirect request, ask for help in the #digital-marketing channel on Slack.
The Digital Marketing Programs team uses these technical details for the redirect process on about.gitlab.com.
We use Google Tag Manager(GTM) to simplify activity tracking on about.gitlab.com with Google Analytics. This documents the system the Digital Marketing Programs team uses with our Google Tag Manager container.
We use semantic names for tags, triggers, and variables to make it simpler to determine what these components are supposed to do. Use an em dash (shift+option-_) to divide the components of each GTM component name.
Tags start with the platform, followed by the tag’s purpose, and are finally contextualized to about.gitlab.com. Any tags related to timed events need the timeframe indicated in a note attached to the tag in GTM to make it clear when to remove a tag.
Triggers start with a description of the action triggering a tag, followed by contextualization for about.gitlab.com.
Variables start with the tag or trigger they reference, followed by contextual data about their purpose.
If you are making changes to the GTM container and have questions about what to name one of these components the Digital Marketing Programs team can help.
Today we’re using the dataLayer sparingly on about.gitlab.com, with our primary use focused on differentiating blog content with postType. We’ll expand how we use the dataLayer to create content groupings for improved customer journey insights and document those updates here.
We need consistent tags across Google Analytics events and have introduced the following structure to our event tags. Our goal is to cover important visitor events with the smallest number of tags in Google Tag Manager. Reducing the number of tags and the overall complexity of our Google Tag Manager container helps us spot and fix coverage issues faster.
These three components help us organize and identify specific event data. Event Categories help us group specific customer journey steps, Event Actions describe visitor interactions with about.gitlab.com, and Event Labels provide contextual details for reporting our performance.
Example Event Label
{{Page URL}} | {{Referrer}} | {{Click text}} | {{Click URL}} | {{Click Class}}
Google Analytics limits event label fields to around 2000 characters, and we'll update the handbook if we start to see truncated event labels.
We're using Simo Ahava's Googl Sheets Add-On to sync notes for our tags and create a GitLab Google Tag Manager inventory This simplifies scanning and searching over the Google Tag Manager web app.
Whenever we make major changes to tags through Google Tag Manager we document them in changes of note. Examples of changes we document are adding or removing tags, changing tag sequencing, or changing when a tag is fired.
Search term volume is hard to estimate. Different tools use different methodolgies and models for reporting this data. AdWords provides data from Google, but the ranges are broad and terms can be combined into a single phrase. Google Trend data normalizes search trends from 1 to 100 based on the terms you're exploring, which doesn't give us any idea of how many people are using a particular phrase.
For our keyword research we rely on Moz Keyword Explorer data because it provides a narrower volume with full phrase integrity. When we report keyword volume, this is the tool we use for this data.
Dimensions are the different attributes of your data. For example, the landing page is a dimension that is the first page a person views when they come to the site.
Metrics are the numbers that are being measured, such as number of page views or number of sessions.
Each dimension and metric has a scope, so it’s important to understand the three different scopes:
Due to the scoping, not every dimension can be combined with every metric. In most cases, the dimensions and the metrics should match the scope.
You can use the calendar in the top right to set the active date range. You can also select the compare to box to compare metrics from different time periods. This will allow you to see month over month or year over year growth for the desired metrics.
Annotations are used to mark a point in time in Google Analytics. They can be used to mark an important event such as a change to the setup of Google Analytics, or an event that heavily impacted traffic positively or negatively.
To create an annotation, double-click on a date. The double-click will bring up the annotation field where you can enter details, and select private or public. Public annotations can be seen by anyone that has access to that view within Google Analytics, and private annotations can only be seen by you.
Most reports have a data table below the graph. The data tables contain a dimension and associated metrics.
The Primary Dimension of the data tables can be changed by selecting a different primary dimension from above the table.
A secondary dimension can also be added by clicking on the Secondary Dimension button above the table and selecting the secondary dimension you’d like to add to the table.
The audience reports are used to understand characteristics of your users such as location, and browser used, and user behavior over multiple visits such as average session time.
The acquisition reports help you know how people find the website. These reports will help you to analyze the benefits of the different digital marketing efforts that you are involved in.
The All Traffic > Channels report breaks down all the different channels that are sending traffic to the site. You can click on any of the channels to drill down and get more granular data about that specific channel. For example, if you click on the Referral channel, you will see which sites are referring traffic to your site.
The behaviors section is about how users use the website. This includes what pages of the site people are looking at as well as how they flow through the site.
The All Pages report shows the number of times a given page was viewed within the selected period of time. You can change the primary dimension to Page Title if it is easier to tell what the page is by looking at the title rather than the URL.
Avg. Time on Page and Bounce Rate can be used to find underperforming content or content that is very engaging to users and can be used in future marketing efforts.
The Landing Pages and Exit Pages reports are scoped at the session and tell us how many people are beginning a session at a certain page (landing page) and how many people are ending a session at a certain page (exit page).
These reports can be valuable to see what content is bringing people to the site and what content is causing people to leave the site.
Events can be set up to track actions that people take on the website, such as clicking links or selecting drop downs. These events can be set up in Google Tag Manager and for the most part won’t require any additional code to be placed on the website.
