<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Josh Morse on Medium]]></title>
        <description><![CDATA[Stories by Josh Morse on Medium]]></description>
        <link>https://medium.com/@joshua.morse?source=rss-bcbaeb91d974------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*m6h06BWePPd2A-mNk0BK8w.jpeg</url>
            <title>Stories by Josh Morse on Medium</title>
            <link>https://medium.com/@joshua.morse?source=rss-bcbaeb91d974------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 06:10:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@joshua.morse/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[4 important tips for design job seekers]]></title>
            <link>https://medium.com/design-bootcamp/4-important-tips-for-design-job-seekers-99ed008fefdd?source=rss-bcbaeb91d974------2</link>
            <guid isPermaLink="false">https://medium.com/p/99ed008fefdd</guid>
            <category><![CDATA[job-search]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[resume]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Josh Morse]]></dc:creator>
            <pubDate>Tue, 23 Mar 2021 08:03:21 GMT</pubDate>
            <atom:updated>2021-03-23T08:03:21.968Z</atom:updated>
            <content:encoded><![CDATA[<p>As industries that were hit hard by the COVID-19 pandemic resume hiring, many design candidates will spend the spring and summer polishing their resumes and hunting for new jobs. I’ve been a hiring manager for over 8 years, and during the past year I have myself interviewed for several jobs, one of which I accepted. With the experiences of being both an interviewer and an interviewee fresh in my mind, I wanted to share some learnings from my own experience as well as common mistakes that I’ve seen design candidates make. I’ve organized these recommendations into four key categories:</p><h3>1. Craft a well-organized and easily scanned resume</h3><p>Your resume is your first opportunity to demonstrate your design talents, and you want to leave a good first impression. I have seen prospective candidates make two critical errors in their resumes that make them much less likely to make the interview stage.</p><p>The first is to give their resumes minimal design attention. I have reviewed hundreds of resumes for design positions that look like they were made with a basic text editor. Key features include a single column, lots of bullet points, and no color or borders. Many use the exact same font style throughout the resume, creating a distinct lack of hierarchy throughout the document. As a design candidate, you should treat your resume like your first and most important design project on the path to getting a job.</p><p>I have also seen many resumes that go the opposite direction, including so many design flourishes and packing in so much information that it is difficult for a prospective reviewer to know where to start. These resumes are often overly colorful, filled with little bar charts and other visualizations meant to showcase a candidates level of skill in particular areas. Some continue on for pages, describing projects in exhaustive detail, even though the candidate should already have a web portfolio to accomplish this task.</p><p>A good rule of thumb is to try to keep your resume to a single page, possibly adding a second page if you have significant experience (10+ years). Your resume is one of your most important information architecture projects, where you have limited space and time to make your best sales pitch to users who can quickly move on to the next option. Resist the urge to list every job or project you’ve completed, particularly when they aren’t relevant to the jobs to which you are applying. Resist using Microsoft Word to design your resume, as it will limit your ability to organize information. A well designed resume will allow a recruiter to find and understand the following within 10 seconds of reading.</p><ul><li>Candidate’s name</li><li>Candidate’s previous positions (company, years employed, title) and key achievements that are relevant to the position</li><li>Candidate’s education (institution(s), degree(s), and years attended)</li><li>Candidate’s most important skills, which should match the job requirements as much as possible</li><li>Candidate’s contact information, including email address, portfolio, and social media links, if present, all which should have embedded hyperlinks</li></ul><figure><img alt="Sample resume." src="https://cdn-images-1.medium.com/max/1024/1*Dzq1lsf8MrqH6bhQq9XZJw.png" /><figcaption>Sample resume template from <a href="https://www.hloom.com/">https://www.hloom.com/</a>resumes. Creative Commons license.</figcaption></figure><p>Additional information, such as personal achievements, interests, and a summary of goals, can be present in a succinct form to add additional flavor and personalization, but should not overshadow the above information. I even had one candidate list “<a href="https://bit.ly/33m1vQr">2006 Time Person of the Year</a>” under a short achievements section, which added a little humor without crowding out otherwise important information. Recruiters often have to read through hundreds of resumes every day, and they do not have time to read a small essay on your final school project. Help them do their job, and they may move you on to the next stage of the process.</p><h3>2. Focus on the most promising positions</h3><p>As the years pass, more and more of the hiring process has gone digital. It is easier than ever to fire a resume off to hundreds of positions, and many candidates opt for this path. These candidates are often poor matches to the job description, don’t stand out from the dozens of applicants with basic design skills and generic or blank cover letters, and rarely move forward to the next step in the hiring process. Even if it only takes a few minutes to submit an online application, you are wasting everyone’s time if you aren’t a good match.</p><p>There are several things that a prospective candidate can do to stand out in crowd of resumes. The first is to ensure that the skills and experience highlighted in your resume match the job description. This may mean tweaking your resume for a particular position to emphasize certain aspects of your background and experience. If you lack a significant amount of skills or experience listed in the job description, you should consider not applying. If you do decide to apply despite these apparent deficiencies, you need to clearly articulate why you believe you are still a strong candidate for the role.</p><p>The next step is to write an engaging cover letter. If your cover letter could apply to any position by changing one or two sentences, or simply restates your resume, it is likely too generic and won’t aid your attempt to secure a job offer. On the other hand, a cover letter that is written from the heart by a passionate applicant who has clearly read about the company and the position and highlighted exactly why they are a good fit is more likely to catch a recruiter or hiring manager’s eye. This is also your best opportunity to explain why any gaps between your resume and the job description should not be a deal breaker. Unfortunately many recruiters ignore cover letters, but if you are focusing on the jobs to which you are a good fit, it’s worth taking an extra 20 minutes to write an informed cover letter. Remember to respect your recruiter’s time by keeping your cover letter brief (~300 words) and proofread carefully.</p><figure><img alt="Sample cover letter." src="https://cdn-images-1.medium.com/max/1024/1*dIAKGj6h3s3fJecY-yR-PQ.png" /><figcaption>Your cover letter should focus on what makes you a good fit for the particular role.</figcaption></figure><p>Focusing on the most promising positions also means engaging with the company and team to which you are applying. If the job is local, see if any design team members attend local meetups, professional groups, or are part of local Slack groups. Whether it is local or remote, you should look for connections on LinkedIn or other social media platforms. This is where prior networking comes into play, so if you are not engaged with the professional design community, now is the time to start.</p><p>Once you have opened a channel for dialog, engage with your contact(s) about the company, role, and team. Don’t oversell yourself; instead, focus on forming relationships and learning about the position. You will have ample opportunity to highlight your skills and experiences during the interview process, and your initial contact may be enough to get an internal referral, which usually leads to a phone screen. You may even learn that the role is not the best fit for you before you apply, which can save you and everyone else considerable time.</p><p>While the focused approach does require a higher initial investment of time and energy, it not only makes it more likely that you will eventually land a job, but it makes it much more likely that you find a job and culture that you enjoy. Nothing wastes more time then starting your job hunt all over again after 6 months.</p><h3>3. Prepare to discuss the right projects</h3><p>During interviews, I frequently ask a candidate to tell me about a particular situation, only to wait through an agonizing 10–20 of “let me think” and “hmm, that’s a tough one”, and then listen to a jumbled explanation that isn’t even a good fit for the situation I presented. Other candidates will spend the entire interview speaking in hypotheticals, as if they have never done similar work before. The best way for interviewers to understand your skills, capabilities, and experience is to ask about your previous work, and any candidate who wants to perform well should be prepared for these questions.</p><p>Many junior candidates struggle due to a limited number of projects, while experienced candidates often get stuck choosing one project from many years of work. However, most interview questions can be handled with just a handful of examples, as long as they cover some common themes:</p><ul><li>A situation where you overcame a significant challenge.</li><li>A situation where you succeeded and measured the success.</li><li>A situation where you failed at some level but learned from the failure.</li><li>A situation where you took on a leadership role.</li><li>Situations where you faced interpersonal conflict with teammates and stakeholders.</li><li>For people managers, situations that demonstrate your leadership style and how you deal with problems from your reports.</li></ul><p>Many projects encompass multiple situations outlined above, but before entering any interview, you should be prepared with at examples that address the above points. If possible, spend 5–10 minutes immediately before the interview reviewing project notes and deliverables and mentally preparing yourself to go into depth on them to answer questions that may arise. Your ability to respond quickly and with confidence will position you well against other candidates who stumble through project details, no matter how impressive or interesting the projects themselves may be.</p><p>Finally, make sure that these projects are represented in your online portfolio. Even if you are restricted in sharing details of your deliverables publicly by terms of your previous employment, you can often still give an outline of the project, the role you played, and the outcome. Interviewers may refer to your portfolio before, during, and after the interview, and continuity will help them in shaping a positive view of your experience.</p><h3>4. Tailor your responses to your audience</h3><p>I have already discussed the importance of tailoring your application, particularly your resume and cover letter, to the needs of the particular position to which you are applying. As you move through the interview process, it is also important to craft your interview responses for the audience with which you will be speaking.</p><p>Early on in the process, you are most likely to speak with a recruiter, or possibly a hiring manager at a smaller company. Recruiters are rarely experts in design or user experience, and often have only a basic knowledge of many roles out of necessity. They know the checklist of skills, experiences, and design tools requested by the hiring manager, and they generally have a good understanding of general qualities that make a good employee (hard-working, open to new ideas, accepting of criticism, etc.). Internal recruiters in particular will be interested in how well you fit into the culture of the company. If you’ve done your research ahead of time, you should be able to demonstrate how you will be a good fit for both the requirements of the position and the culture of the organization.</p><p>Most hiring managers will themselves be designers, so it is particularly important to be honest but positive about your own skills and experience. Make sure you have reviewed current design trends and advice from professional publishing communities like UX Collective, but resist the urge to fall into constant name-dropping. If a particular book or author is relevant to the conversation, feel free to mention it in your conversation, but bringing up big names in the design community too often will overshadow your own achievements.</p><p>At some point during the interview process you are likely to speak with team members beyond the hiring manager and recruiter. These interviewers often include software developers, product managers, other designers, analysts, researchers, members of the support team, marketers, and more. At smaller companies that have yet to build a design team, the hiring manager may themselves be in one of these roles. If you are given names ahead of time, I recommend that reviewing their profiles online to understand a little of their professional background and interests.</p><p>Even if this is not possible, you should always prepare to recount situations in your past when you successfully interacted with teammates in a similar role. Ultimately, most prospective teammates are most interested in two things: whether they will enjoy working with you, and whether you can help them and their team succeed. Your answers to their questions should aim to satisfy both of these questions, and are likely to vary based on who you are speaking with. For example, if a product manager asks a question about overcoming a challenge, you could talk about finding a solution to a particularly vexing customer problem which led to an increase in overall customer approval. If the question comes from a developer, you might focus on a technical problem which your worked closely with an engineering team to find an elegant and usable solution that didn’t add technical debt.</p><figure><img alt="Diagram illustrating the different focuses of telling a story to different team members." src="https://cdn-images-1.medium.com/max/538/1*FxMex2AZLv-w9XC7E4x1og.png" /><figcaption>Tailor your experiences to your audience.</figcaption></figure><p>While your answers should consider your audience, it is important to ask questions yourself when given a chance. Use the opportunity to try to understand each interviewer’s day-to-day work and needs. Not only will it help you give more appealing answers, but you will find yourself in a more comfortable position as you gain familiarity with your interviewer and their environment. Most people enjoy talking about their work and passions, and interviewers move more quickly and smoothly if they transition into a more natural conversational flow. In addition, if you do get an offer, learning more about the team will help you decide if it is a company where you would be comfortable working.</p><p>Finally, make sure to be friendly and courteous in all your interactions. You may be working with these colleagues for years, and it is important that you feel comfortable with each other. Most interviewers would rather take a chance on a bright, friendly team-player who may need a little extra mentoring than an unfriendly or aloof rock star. Send an individually-tailored thank-you email to each of your interviewers after each interview, or ask the recruiter or hiring manager to pass it on if you don’t have their contact information. Even if you don’t end up working with them now, you may encounter them in the future, and it never hurts to build professional relationships.</p><h3>Conclusion</h3><p>The tips above will not guarantee you a design job, but they will position you well against the competition. Remember that even the best designers in the industry have faced challenges in getting a job offer. As the exact needs of the hiring manager and the skills and background of the competition are beyond your control, you should focus on the aspects you can control by putting forth the best possible application and interviews.</p><p>Be ready to accept some degree of failure during the process as a learning experience, and don’t be afraid to reach out to the recruiter or hiring manger if you have questions about the process. Continue to apply, interview, and network, and good luck on the job hunt!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99ed008fefdd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/4-important-tips-for-design-job-seekers-99ed008fefdd">4 important tips for design job seekers</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Engaging your company with customer interview data]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://uxdesign.cc/engaging-your-company-with-customer-interview-data-91f07ecafc57?source=rss-bcbaeb91d974------2"><img src="https://cdn-images-1.medium.com/max/826/1*LtDI1o29LEY2661QAH40dw.png" width="826"></a></p><p class="medium-feed-snippet">The fields of user experience and product management have long recognized the value of regular customer communication. Whether conducting&#x2026;</p><p class="medium-feed-link"><a href="https://uxdesign.cc/engaging-your-company-with-customer-interview-data-91f07ecafc57?source=rss-bcbaeb91d974------2">Continue reading on UX Collective »</a></p></div>]]></description>
            <link>https://uxdesign.cc/engaging-your-company-with-customer-interview-data-91f07ecafc57?source=rss-bcbaeb91d974------2</link>
            <guid isPermaLink="false">https://medium.com/p/91f07ecafc57</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Josh Morse]]></dc:creator>
            <pubDate>Thu, 28 May 2020 23:45:20 GMT</pubDate>
            <atom:updated>2020-05-29T22:42:18.725Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Maximizing UX bandwidth]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://uxdesign.cc/maximizing-ux-bandwidth-4b50c628f337?source=rss-bcbaeb91d974------2"><img src="https://cdn-images-1.medium.com/max/887/1*o3b4FineGf8zQvPRu4fo0g.png" width="887"></a></p><p class="medium-feed-snippet">Bandwidth constraints are a common problem at any software company, and are particularly prevalent for user experience teams, which are&#x2026;</p><p class="medium-feed-link"><a href="https://uxdesign.cc/maximizing-ux-bandwidth-4b50c628f337?source=rss-bcbaeb91d974------2">Continue reading on UX Collective »</a></p></div>]]></description>
            <link>https://uxdesign.cc/maximizing-ux-bandwidth-4b50c628f337?source=rss-bcbaeb91d974------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b50c628f337</guid>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[designops]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Josh Morse]]></dc:creator>
            <pubDate>Tue, 28 Apr 2020 13:14:47 GMT</pubDate>
            <atom:updated>2022-08-16T14:08:26.281Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Expanding Google Analytics Data With Google Tag Manager Variables]]></title>
            <link>https://medium.com/@joshua.morse/expanding-google-analytics-data-with-google-tag-manager-variables-a5ff308c555c?source=rss-bcbaeb91d974------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5ff308c555c</guid>
            <category><![CDATA[google-tag-manager]]></category>
            <category><![CDATA[web-analytics]]></category>
            <category><![CDATA[google-analytics]]></category>
            <category><![CDATA[mixpanel]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Josh Morse]]></dc:creator>
            <pubDate>Tue, 14 Apr 2020 14:21:10 GMT</pubDate>
            <atom:updated>2020-04-14T14:21:10.927Z</atom:updated>
            <content:encoded><![CDATA[<p>Good product and design teams understand the value of data. Data from analytics tools can help drive improvements to existing products, as well as measure the success of new features. I have been managing web analytics with Google Tag Manager (GTM) for almost 10 years, and during that time I have needed to track information beyond what many analytics products like Google Analytics, Heap Analytics, Pendo, and Mixpanel provide natively. In order to do this, I create custom variables that feed information to the aforementioned analytics products.</p><p>This article assumes a basic knowledge of Google Tag Manager. If you are unfamiliar with it, Google Tag Manager is a web-based tool that manages 3rd party JavaScript products on your website or application. With Google Tag Manager, you can embed a single JavaScript snippet into your product’s code, then use Google’s UI to add ‘tags’ for all of your 3rd-party integrations. For more information on setting up your own tags, check out the <a href="https://bit.ly/3eamdqq">Google Tag Manager Overview</a>.</p><p>Once you’ve set up your tags, you can begin collecting information. By default, Google Analytics (and other analytics tools) will record a wide array of useful data about your users, including operating system, web browser, screen dimensions, location, and much more. If you want more information that Google provides, you can pass this information to Google Analytics using Google Tag Manager variables. Below I’ve outlined some of the variables I’ve found most useful, including:</p><ul><li>Window dimensions</li><li>Pixel ratio</li><li>Current time (UNIX time and readable timestamps)</li><li>Full URL (including hash values)</li><li>Generic URL (normalizing numeric identifiers)</li><li>Custom values using localStorage (user ID, account ID, etc.)</li></ul><h3>Setting up your variables</h3><p>Below, I have provided a number of useful variables to augment Google Analytics, as well as other analytics tools. In order to store this information in Google Analytics, you will need to set up a <a href="https://bit.ly/3c8M5kI">custom dimension</a> for each variable. For the non-custom variables below, make sure you set the scope to “Hit”. Once you have set up your custom dimensions in Google Analytics, create a variable of type ‘Constant’ with the index for your custom dimension from the Google Analytics Setting Custom Dimension page in Google Tag Manager. While this is not strictly necessary, it makes your Google Tag Manager workspaces much more readable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SYhzRZHdzYzOazEdmiecLg.png" /><figcaption>Constant variable for a custom dimension</figcaption></figure><p>Once you have set up your custom dimension index variables as well as the informational variables below, you can add them to a Google Analytics Settings variable. This settings variable should be used in all of your Google Analytics tags in order to consistently pass information for any time of event, from clicks to page loads. For other web analytics tools such as Heap, Mixpanel, and Pendo, you will need to pass the variables directly in the Custom HTML tags that load those scripts; for more information, refer to the documentation for your specific web analytics product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aJrzzZU2eOZARb3_wvIvBA.png" /><figcaption>Google Analytics Settings variable with custom dimensions</figcaption></figure><p>Now that your Google Tag Manager environment is properly configured, lets look at the extra informational variables that we can pass to your web analytics tool.</p><p><strong>A note on custom JavaScript<br></strong>Using custom JavaScript in Google Tag Manager has the potential to trigger errors. If your code causes an error, it might be visible to the end user. While all the custom JavaScript below has been tested, all variables that use custom JavaScript should wrap the code in <em>try </em>and <em>catch </em>blocks as a precaution. In the unlikely event that an error occurs, it will be caught and passed to your analytics tool; you can see them by filtering for “GTM Error” results.</p><h3>Window Dimensions</h3><p>By default, Google Analytics will record the dimensions of the user’s screen. Many users, particularly those with larger monitors, use only a portion of their screen to display web pages. In order to understand what sizes your designs need to support, you really need to know are the dimensions of the user’s web browser window; luckily, we can get those ourselves with a little JavaScript.</p><p><strong>Variable Type:</strong> Custom JavaScript<br><strong>Custom JavaScript:</strong></p><pre>function() {</pre><pre>  try {<br>    var width = document.documentElement.clientWidth;<br>    var height = document.documentElement.clientHeight;</pre><pre>    return width + &quot;x&quot; + height;</pre><pre>  }</pre><pre>  catch(e) {<br>    return &quot;GTM Error: &quot; + e.toString();<br>  }<br>}</pre><h3>Pixel Ratio</h3><p>While window dimensions will tell you the size of the browser window, they will not tell you whether the user is using a high-density (sometimes called retina) display. Knowing the density of pixels on your users’ screen is important when designing high-resolution icons and otherwise supporting high-resolution screens. A screen with normal pixel density will return a value of <em>1</em>, while a ‘retina’ Macbook will return a value of <em>2</em> if there is no scaling. For more information, check out <a href="https://bit.ly/2K5NMDy">Wikipedia’s entry on pixel density</a>.</p><p><strong>Variable Type:</strong> JavaScript Variable<br><strong>Global Variable Name: </strong>window.devicePixelRatio</p><h3>Current Time</h3><p>A curious omission in Google Analytics is the current timestamp; while Google clearly stores this information, they do not make it available as a dimension throughout Google Analytics. Google only makes this information available in some reports such as the user explorer, and even then, it is only precise down to the minute. Luckily, you can get the current timestamp down to the millisecond. I recommend using two variables to store this time: first, store one as the number of milliseconds since January 1, 1970, and second store a human-readable timestamp. The first variable, or UNIX time, is useful if you need to compare two timestamps using greater than or less than in an analytics report.</p><p><strong>Variable Type:</strong> Custom JavaScript<br><strong>Custom JavaScript:</strong></p><pre>function() {</pre><pre>  try {<br>    return Date.now();<br>  }</pre><pre>  catch(e) {<br>    return &quot;GTM Error: &quot; + e.toString();<br>  }<br>}</pre><p>For a more human-readable timestamp, use the following custom JavaScript. You can format it further using the <a href="https://mzl.la/3a9Utiz">JavaScript Date object</a>.</p><pre>function() {</pre><pre>  try {<br>    var gtm_timestamp = new Date();<br>    return gtm_timestamp;<br>  }</pre><pre>  catch(e) {<br>    return &quot;GTM Error: &quot; + e.toString();<br>  }<br>}</pre><h3>Full URL including parameter and hash</h3><p>By default, Google Analytics ignores certain aspects of a URL, particularly the hashtag at the end. For many web applications, this is important data that needs to be tracked. This variable will return the entire URL, including the hash. Note that, in order to track changes to the URL’s hash changes within a page, such as a user clicking an anchor tag, you will need to create a new History Fragment Change trigger in Google Tag Manager.</p><p><strong>Variable Type:</strong> JavaScript Variable<br><strong>Custom JavaScript: </strong>window.location.href</p><p>If you want to store just the content of the URL hash, use the following variable.</p><p><strong>Variable Type:</strong> JavaScript Variable<br><strong>Custom JavaScript: </strong>window.location.hash</p><h3>Generic URL</h3><p>Many websites embed identifiers into their URLs, such as user or account ID. While these can be filtered using regular expressions and/or wildcards, there are times when it is easier to have all of those numeric identifiers normalized so that you can report on URLs regardless of an account or user ID. The following variable will convert any numeric substring in a URL to three zeros, so <a href="http://www.mysite.com/account/1234/start.html"><em>www.mysite.com/account/1234/start.html</em></a><em> </em>becomes <em>www.mysite.com/account/000/start.html</em>. Note that mixed alpha and numeric identifiers will not be properly converted.</p><p><strong>Variable Type:</strong> Custom JavaScript<br><strong>Custom JavaScript:</strong></p><pre>function() {<br>  try {<br>    var url = window.location.href;<br>    var numbers = url.match(/[0-9]{1,}/g);<br>    if(numbers) {<br>      for (var i=0;i&lt;numbers.length;i++){<br>        url = url.replace(numbers[i],&quot;000&quot;);<br>      }<br>    }<br>    return url;<br>  }<br>  catch(e){<br>    return &quot;GTM Error: &quot; + e.toString();<br>  }<br>}</pre><h3>Custom local storage values</h3><p>The above variables are all applicable to any application, but you undoubtedly will want to store additional information specific to your own website or application, such as anonymized user, account, and session identifiers. To pass these values to your analytics too, I recommend storing them in localStorage, which persists across pages and sessions, unlike regular JavaScript variables.</p><p>While Google makes it very simple to return normal JavaScript variables, it takes a little more work to access localStorage. To do so, use the custom JavaScript variable below, swapping out ‘myvalue’ with the name of the localStorage value that you wish to use (e.g. ‘userID’). If you are using Google Analytics, remember that storing personally identifiable information such as email violates <a href="https://bit.ly/3epuib0">their policies on PII</a>. In addition, you should check with your legal team about complying with data privacy laws like the <a href="https://bit.ly/2z0LOC9">EU General Data Protection Regulation (GDPR)</a>.</p><p><strong>Variable Type:</strong> Custom JavaScript<br><strong>Custom JavaScript:</strong></p><pre>function () {<br> <br>  try {<br>    if (window.localStorage) {<br>      return window.localStorage.getItem(&quot;myvalue&quot;);<br>    }<br>    else {<br>      return undefined;<br>    }<br>  }<br>  catch (e) {<br>    return &quot;GTM Error: &quot; + e.toString();<br>  }<br>}</pre><h3>Conclusion</h3><p>I hope you found this article helpful. If you have any questions or want to see more articles about using Google Tag Manager, Google Analytics, or other web analytics tools, please post a comment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5ff308c555c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>