General

Export Your Data from Universal Analytics before you lose it

Published May 23, 2024

Updated May 23, 2024

3 min read

Introduction

In 2023, Google announced the retirement of Universal Analytics and told everyone to migrate to Google Analytics 4, commonly known as GA4. Google Analytics has long been a staple for businesses and website owners seeking insights into their audience and performance metrics. However, with the introduction of Google Analytics 4, there comes a pivotal moment for users of the older Universal Analytics (UA) platform.

Difference between UA and GA4

What data will you lose?

You will lose ALL of the historical data! By July 1, 2024, Google will delete all UA data, and you will no longer have access to it after that. Also, Universal Analytics will no longer track new conversions, affecting ad campaign performance that relies on these conversions for Smart Bidding. Audience lists from Universal Analytics will also disappear, potentially impacting media activation and performance. API requests tied to Universal Analytics properties will fail, preventing data deletion requests and causing Looker Studio to stop displaying Universal Analytics data. Additionally, Attribution Projects (beta) in Google Analytics will be deleted.

How to Export Your Data

There are multiple ways to export your data from Google Analytics, such as using the Google Analytics add-on for Google Sheets or using BigQuery integration to export historical data from your Universal Analytics 360 property.

This article will discuss the easiest way to export your data using the Google Analytics add-on from Google Workspace Marketplace.

From “Extensions” > “Google Analytics” > “Create new report”

The Google Analytics extension will display a Wizard that requires the following steps:

Set a name for your report
Then, you select the Google Analytics account
Then, the property you want to export
Also, there are some optional configuration that helps you filter the data you want to export

Then click on “Create Report,” and it will export the report for you

Here is an example of the template https://docs.google.com/spreadsheets/d/1zXEBEQQk6TPeGb7-Wm2J0uM0q0XnTdJqrfikCTmYs8c/copy

Running the Report

After setting up the report template with the necessary configurations, users can run the report to extract their UA data into Google Sheets. Depending on the size of the dataset, the report may take some time to generate, especially for larger datasets spanning multiple years. In such cases, splitting the data into smaller chunks may be necessary to ensure efficient processing.

Conclusion

As Google transitions from Universal Analytics to Google Analytics 4, businesses and website owners must proactively preserve their valuable historical data. With the impending deletion of all Universal Analytics data by July 1, 2024, failing to export your data in time could result in significant data loss, affecting ad campaign performance and analytics capabilities. By following the outlined methods to export data using tools like the Google Analytics add-on for Google Sheets, you can ensure that your historical data is safely archived and accessible for future analysis.

This Dot is a consultancy dedicated to guiding companies through their modernization and digital transformation journeys. Specializing in replatforming, modernizing, and launching new initiatives, we stand out by taking true ownership of your engineering projects.

We love helping teams with projects that have missed their deadlines or helping keep your strategic digital initiatives on course. Check out our case studies and our clients that trust us with their engineering.

About the author(s)

Mark Shenouda
@MarkSShenouda @markshenouda

Double Click: Jump on the waitlist for Fig.io's new autocomplete terminal add-on!

Welcome to the Double Click! This is the weekly blog series that shines a spotlight on emerging technologies, technological concepts, and community projects that enrich the JavaScript Ecosystem! This week, I’m sharing a really cool, new tool for your existing terminal that I LOVE: Fig! This add-on provides VSCode-style autocomplete, and is currently being made available for free to those who sign up on their website. When using the Fig add-on, you get autocomplete options in your terminal, showing you everything you need, such as lists of available directories, folders, git commands, branches, components, and more without taking you out of your flow. How magical is it to get more time to focus on your code rather than trying to remember shortcuts and commands in terminal? (LIFESAVER!) Fig is also built to integrate with a number of CLI tools, including npm, Heroku, AWS, GCP, Docker, and more, with plans to add further integrations as the technology develops and new users start including Fig in their tool belt. Other features of this add-on include keyboard-first functionality, allowing developers to quickly use the auto completes without having to touch their mouse, open-source completion specs, which ensure that the Fig add-on always remains up to date and relevant for users, and the add-on runs locally, offering speed and security. I’m already using Fig, and am a huge supporter of any tools that work to remove complexities from my development process. I am excited to see this project grow!...

Sep 9, 2021

1 min

ToolingHerokuJavaScriptnpm

Understanding RegEx

RegEx, an abbreviation of "regular expressions", are a set of characters which are used to create patterns that can be used to search, find, replace, or validate text. RegEx is language agnostic, although some features are not available to some languages. You can test out RegEx here before putting it in your code. We will look at some examples: RegEx: /dog/ Text: "The dog is big dog" Regular expressions start with a forward slash / followed by the pattern we want to match, and another forward slash / to end it. In this first example, we want to match a simple pattern: "dog". Our RegEx will highlight the first pattern it matches, which is the bold character in there. Sometimes, we want our RegEx to highlight not only the first pattern, but all the patterns that can be found in the string. This is where expression flags are introduced. Expression flags are always introduced after the last forward slash. We will use the global expression flag to identify all patterns. RegEx: /dog/g Text: "The dog is big dog" With the global flag, our pattern identifies all the characters in this string. Here are some different expression flags that can be used. * g - The global expression flag, identifies all the pattern in the text * i - The case insensitive flag, identifies a pattern regardless of the case (either lower case or upper case) * m - The multi line match, identifies a pattern that spans multiple lines RegEx: /\d/ or /[0-9]/ Text: "1 2343" There are two ways to match numbers: the first one, \d, is a pattern that matches any single decimal number. The d is case sensitive- the backward slash is used to escape the character d, which can be used to identify only decimal numbers. The second one [0-9] also matches any decimal number, but in a different way, it starts and ends with a square bracket. We will touch more on square brackets soon. However, we want to identify a number from 0–9. So, like this indicates, we can also do [4-9], which means it will identify a number from 4–9, so it will have this instead of "12343". If we want to identify a concurrent number, we will have to use some commands. RegEx: /\d+/ or /[0-9]+/ Text: "12343" Adding + to our pattern will highlight all the numbers because it means match 1 or more of the preceding pattern. Commands can help a lot when writing RegEx. I will display a command cheat sheet below. Commands cheat sheat |Command | Description | Pattern | Matches | |-----------|--------------------------------------------------------------------|-------------|------------------------| | . | Matches any character |c.c | cac, cbc, cgc, cdc, cfc| | * | Matches 0 or more of the preceding token |cat\d* | cat, cat24, cat56 | | + | Matches 1 or more of the preceding token |cat\d* | cat24, cat56 | | ? | Matches 0 or 1 of the preceding token |cat\d* | cat, cat5 | | ^ | Matches beginning of the text |^cat | catdaddy, cat mummy | | $ | Matches end of the text |^os | los, lagos | | [...] | Matches any pattern in the brackets |[0-9xyz] | x, y, 1 | | [^...] | Matches any pattern not in the brackets |[^0-9xyz] | a, b, cd | | [a-z] | Matches any character within that range |[0-9] | 0, 1, 2, 3 | | {a} | Matches a preceding pattern a number of (a) times |cat{2} | catcat | | {a,} | Matches a preceding pattern a number of (a) times or more |cat{2,} | catcat, catcatcatcat | | {a,b} | Matches a preceding pattern between a or b |cat{1,2} | cat, catcat | | . | Matches any character |co.l | cool, coal | | | | OR operator |cat|dog | cat or dog | With the commands above, we can create complex Regex: Alphanumeric texts RegEx: /[0-9A-Za-z]+/ Text: "bensoN123" Twitter Handle Twitter handles contain numbers, letters, and underscores, but start with @. RegEx: /^@[0-9A-Za-z_]+/ Text: "@bensoN123" Simple Email Validation RegEx: /^[\w]+@[\w]+.[a-zA-Z]{2,4}$/ Text: "wole@mail.co" RegEx can be complicated at first, but the more you work with it, the easier it gets. You can explore more options, like negative look behind, and positive look ahead. If you have more questions, be free to reach out to me through my Github....

Jun 14, 2021

3 mins

TipsGeneral

Bun v1.0

On September 8, 2023, Bun version 1 was released as the first production-ready version of Bun, a fast, all-in-one toolkit for running, building, testing, and debugging JavaScript and TypeScript. Why a new JS runtime You may ask, we already have Node and Deno, so why would we need another javascript runtime, Well yes we had Node for a very long time, but developers face a lot of problems with it, and maybe the first problem is because it’s there for a very long time, it has been changing a lot between different versions and one of the biggest nightmares for JavaScript developers these days is upgrading the node version. Also, Node lacks support for Typescriptt. Zig programming language One of the main reasons that Bun is faster than Node, is the programming language it has been built with which is Zig. Zig is a very fast programming language, even faster than C) (here is some benchmarks), it focuses on performance and memory control. The reasons it’s faster than C is because of the LLVM optimizations it has, and also the way it handles the undefined behavior under the hood Developer Experience Bun delivers a better developer experience than Node on many levels. First, it’s almost fully compatible with Node so you can use Node packages without any issues. Also, you don’t need to worry about JS Common and ES Modules anymore, you can use both in the same file, yup you read that right, for example: ` Also, it has a built-in test framework similar to Jest or Vitest in the project so no need to install a different test framework with different bundler in the same project like Webpack or Vite ` Also, it supports JSX out-of-the-box ` Also, Bun has the fastest javascript package manager and the most efficient you can find as of the time of this post ` Bun Native APIs Bun supports the Node APIs but also they have fun and easy APIs to work with like * Bun.serve() : to create HTTP server * Bun.file() : to read and write the file system * Bun. password.hash(): to hash passwords * Bun.build(): to bundle files for the browser * Bun.FileSystemRouter(): a file system router And many more features Plugin system Bun also has an amazing plugin system that allows developers to create their own plugins and add them to the Bun ecosystem. ` Conclusion Bun is a very promising project, and it’s still in the early stages, but it has a lot of potential to be the next big thing in the JavaScript world. It’s fast, easy to use, and has a lot of amazing features. I’m very excited to see what the future holds for Bun and I’m sure it will be a very successful project....

Oct 25, 2023

2 mins

BunJavaScriptnpmNodeJS

Fostering a Culture of Optimization and Continuous Improvement with Scott Roehrenbeck

In this episode of The Leadership Exchange, host Rob Ocel, VP of Innovation at This Dot Labs, sits down with Scott Roehrenbeck, CTO of Apptegy, for an in-depth discussion on leadership, process improvement, and the role of people in building effective teams. Scott shares insights from his 20+ years in tech, reflecting on the evolution of his leadership style, the importance of balancing process with flexibility, and how to support team autonomy while maintaining consistency. They also discuss the challenges of navigating turbulent times in tech and strategies for aligning team outputs with business goals. Perfect for anyone interested in tech leadership, process optimization, and fostering a culture of continuous improvement. Chapters - Introduction to the Leadership Exchange (00:00 - 00:23) - Scott’s Journey to CTO (00:23 - 02:15) - Cyclical Trends in Tech (02:15 - 03:27) - The Challenges of Leadership (03:27 - 06:07) - The Purpose of Process (11:43 - 14:09) - Process vs. Output: What Really Matters (14:09 - 17:20) - Building vs. Buying Process Frameworks (17:28 - 20:57) - The Role of Adaptation in Process Improvement (20:57 - 24:08) - Navigating ‘Religious’ Arguments in Process (24:08 - 27:02) - Defining a Team’s Unique Process (27:02 - 29:41) - Wrapping Up and Final Thoughts (29:41 - 30:40) - Thank You to Sponsors (30:40 - End) Follow Scott Roehrenbeck on Social Media Linkedin: https://www.linkedin.com/in/scott-roehrenbeck-5a573431/...

Nov 11, 2024

1 min

Engineering Leadership

Let's innovate together!

We're ready to be your trusted technical partners in your digital innovation journey.

Whether it's modernization or custom software solutions, our team of experts can guide you through best practices and how to build scalable, performant software that lasts.

Export Your Data from Universal Analytics before you lose it

Introduction

Difference between UA and GA4

What data will you lose?

How to Export Your Data

Running the Report

Conclusion

Mark Shenouda

You might also like

Double Click: Jump on the waitlist for Fig.io's new autocomplete terminal add-on!

Understanding RegEx

Bun v1.0

Fostering a Culture of Optimization and Continuous Improvement with Scott Roehrenbeck

Let's innovate together!

You might also like

Double Click: Jump on the waitlist for Fig.io's new autocomplete terminal add-on!

Understanding RegEx

Bun v1.0

Fostering a Culture of Optimization and Continuous Improvement with Scott Roehrenbeck