Imagine that you are making a beautiful and useful data panel for your business and that you want to check which landing pages (that is, where users come from) generate the most conversions. You add a table, because you want to first have an overview of the data and then better structure it in other graphs. With the Google Analytics data source already in your Data Studio project, you go to search for “Landing Page” and you find that there are two . Bah, an insignificant detail.
How to fix the error
You add one, you see that there is data and industry email list you think “this will be a little mistake that doesn’t happen, nah, these people at Google don’t miss serious things.” An insignificant detail that can lead to serious mistakes or headaches. You know why? Well, because, in reality, it is not the same field that has been cast twice but rather they are two different fields . But you don’t discover that until you encounter more serious problems. Duplication is not reflected in the custom field editor Imagine now that what you want is to classify landing pages by groups .
Edit field names
Yes, I’ll tell you. Imagine you have a set of landing B2B Fax Lead pages that contain the word “growth” and another set that contain the word “productivity,” both in the url. The rest of the pages are not relevant to you at this time. Are you getting it? So you decide to create a custom field that, through regular expressions, generates 3 groups of landing pages: Urls related to Productivity. Urls related to Growth Rest of URLS. My friend Luis M. Villanueva would call this “strategic segments.” Hahaha. Well, you go to the Data Studio field editor and, when you start writing the formula, you realize that you don’t see that duplicity that we were talking about before.