Marketing Analytics

Charter

Marketing Analytics supports the entire Marketing team to develop and execute a Global Marketing Strategy working with Marketing Leadership and GTM teams, as well as owning the overall measurement strategy for GitLab marketing working with the data team.

Meet the Team

• Christine Lee, VP, Marketing Operations & Analytics
• Viola Hempel, Director, Marketing Analytics
• Jerome Ahye, Staff Data Analyst, Data Analytics
• Robert Kohnke, Senior Analytics Engineer
• David Egan, Staff Data Analyst
• Djordje Micovic, Staff Data Analyst
• Dennis Charukulvanich, Senior Data Analyst
• Ankit Kanwar, Senior Data Analyst

How to Communicate with Us

Slack channels

We can be reached via our own #mktg-analytics channel, although we also monitor the general #marketing channel and #mktgops. We attempt to avoid direct messages where possible as it discourages collaboration.

How to Get Help

Our Work

As part of our work, we publish self-service dashboards for team members to understand campaign performance and key marketing KPIs. Our dashboard page lists our currently supported dashboards and our framework for publishing a new dashboard.

How We Work

We use milestones to create 2 week sprints. Below are links to our project within GitLab.com and our a view of our current and upcoming milestones.

Issues

The team works from issues and issue boards. If you are needing our assistance with any project, please open an issue and use the ~MktgSandP::0 - To Be Triaged label anywhere within the GitLab repo. Prior to opening a new issue, feel free to reach out to one of us to see if there is already a related issue that you can add your comments to.

With Agile Delivery being one of the solutions that GitLab (as a product) addresses, the Marketing Analytics team aims to follow many of the agile methodologies. To help us in that effort, please create any Marketing Analytics issues in the following format.

Note: This format is the Agile user story format and helps the issue-requester (you) and the Strategy team by clearly stating what as well as why for each request and concern.

Format: As a _____ (role in marketing), I would like to ____________(need), so that ________________(reason).

Marketing Analytics uses a local issue board within the Marketing project.

Issue Weights

Marketing Analytics uses the Fibonnacci sequence when creating issue weights. We start with a weight of 2, smaller is too simple for an issue. Similarly, we break any issue larger than 13 into an epic.

Epics

In order to categorize various related issues, we make use of epics to help each team member organize their work, especially when it crosses multiple milestones. If it is a Marketing Analytics epic, we will add the In Epic label to it, so that we can easily see that it is part of an epic on our kanban board.

Labeling

We use labels for two purposes:

1. Categorize the tool or area that is affected
2. Identify the stage they are in

Milestones

The Marketing Analytics team works in two week sprints/iterations which are tracked as Milestones at the GitLab.com level. We use the same interval dates used by Mktg Ops, Sales Ops and Sales Systems. Each individual contributor (IC) is responsible for adding issues to the milestone that will be completed in the two week time frame. If needed, the IC will separate the main issue into smaller pieces that are workable segments of the larger request.

The Marketing Analytics team generally creates just one milestone beyond the current iteration, so at any given time there will be the current milestone and upcoming milestone. Any other issue that is not included will be added into future milestones &/or added as work is completed in the current milestone.

If there are handbook updates that need to be made as a result of work done in a given milestone, a separate MR should be included in that milestone.

Focus Fridays

The Marketing Analytics team has continued our experiment with MOps on 2020-04-20 to commit to no internal meetings one day of the week. Now the entire Marketing team has moved to Focus Fridays. Please try not to schedule meetings for team members on Fridays, so they can devote time for deep work in milestone-related issues.

Operational Timeline of Changes

Periodically Marketing Analytics becomes aware of significant changes that affect overall data and reporting. To capture these, we have a shared Operational timeline of events with the MktgOps team. They primarily add any process changes to this document as they occur. It has been a great communication tool, especially as we look back at metrics in the past and can track the changes that were made.

Skateholder Alignment

To give each functional marketing team has a single point of contact for marketing analytics, we use the following stakeholder mapping alignment table.

Important Resources

• Marketing Metrics
• Dashboards Page

We are the Bussiness Owners Of the Following Applications

• Bizible
• Allocadia
• Google Analytics

Requesting access to an existing tool

To request access to Bizible or Allocadia, please follow the access request process as outlined in the business operations handbook.

If you are working with a contractor or consultant that requires access to one of these tools, please follow the professional services access request process as outlined in the procurement handbook.

Campaigns and Programs

As is typical of any marketing organization, we often look at our Campaigns to see how they are doing. The Campaigns and Programs Page shows all of the campaign types, their progression statuses and cost tracking.

Initial Source

Similarly, we are interested in theInitial Source of a given prospect. It is the first “known” touch attribution or when a website visitor becomes a known name in our database. The list of currently supported values for initial source can be found on the Mktg Ops page.

Lead and Contact Statuses

The Lead & Contact objects in Salesforce have unified statuses with set definitions.

Touchpoints & Attribution

We use Adobe Marketo Measure (Bizible) for marketing attribution and tracking times when there is engagement with our prospects. The Adobe Marketo Measure handbook page has more details.

Web Traffic Analysis

Google Analytics data is used to gain insights about the visitors and their behavior on our websites. The web traffic analysis data catalog provides details about how to leverage GitLab specific web data (key terms, definitions, KPIs, caveats, data structure)

View page source - Edit this page - please contribute.