<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Best Naming Convention Practices in Tips, Tricks &amp; Best Practices</title>
    <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/265462#M848</link>
    <description>&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;Hi &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/76717"&gt;@qturner1&lt;/a&gt;.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;Although keeping all the assets organized is very difficult, there are some practices that we implement for our portal and our clients' portals. Most of our assets have the following naming convention:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;EM&gt;&lt;FONT size="3" face="helvetica"&gt;Type of asset | Campaign | Buyer's Journey stage | Title&lt;/FONT&gt;&lt;/EM&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;For example, a workflow email could be:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;&lt;EM&gt;WF | Inbound Marketing | Consideration | What is Inbound Marketing.&lt;/EM&gt;&lt;/FONT&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;You can use "WF" for workflows, "FU" for followup emails, "LP" for landing pages, "TP" for Thank you pages, and so on...&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;As some have pointed out, maybe adding the date would also be a good idea. For example:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;EM&gt;&lt;FONT size="3" face="helvetica"&gt;WF | 2019Q1 | Inbound Marketing | Consideration | What is Inbound Marketing?&lt;/FONT&gt;&lt;/EM&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;As for the file manager we have a folder structure that we took from this blog post:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;&lt;A href="https://www.zenpilot.com/blog/an-awesomely-organized-hubspot-file-manager" target="_self"&gt;https://www.zenpilot.com/blog/an-awesomely-organized-hubspot-file-manager&lt;/A&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;Basically our folder structure is the one mentioned in the post:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;*Free Stock Photos&amp;nbsp;&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;cta&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;email&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;identity&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;images&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;offers&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;resources&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;scripts&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;social&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;video&amp;nbsp;&lt;/FONT&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;And we try to follow the following file naming best practices:&lt;/FONT&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;All text in lowercase&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;Use hyphens instead of spaces&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;Don't use accents (we're in México :)) or any special character.&lt;/FONT&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;It's really hard work but it really pays out to have everything organized. Good luck!&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;&lt;STRONG&gt;Rafa CM.&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT size="3" face="helvetica"&gt;&lt;EM&gt;Inbound Métrica - Director&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT size="3" face="helvetica"&gt;&lt;A href="https://inboundmetrica.com" target="_blank" rel="noopener"&gt;inboundmetrica.com&lt;/A&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 01 Jun 2019 13:19:46 GMT</pubDate>
    <dc:creator>Rafa_CM</dc:creator>
    <dc:date>2019-06-01T13:19:46Z</dc:date>
    <item>
      <title>Best Naming Convention Practices</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/246768#M781</link>
      <description>&lt;P&gt;Hi HubSpot Community,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've worked in several marketing automation platforms and I notice that all of the naming convention structures are different. I've narrowed down best practices according to our organization for the following items:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;File Manager&lt;/P&gt;&lt;P&gt;Emails&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But I'm having trouble with the best way to do naming conventions for:&lt;/P&gt;&lt;P&gt;Campaigns (we all know this is important since we can't change once created)&lt;/P&gt;&lt;P&gt;Lists&lt;/P&gt;&lt;P&gt;Forms&lt;/P&gt;&lt;P&gt;Workflows&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What has worked for your teams? I've looked into every article and haven't found anything helpful.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 20 Jan 2019 14:55:26 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/246768#M781</guid>
      <dc:creator>qturner1</dc:creator>
      <dc:date>2019-01-20T14:55:26Z</dc:date>
    </item>
    <item>
      <title>Re: Best Naming Convention Practices</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/246774#M782</link>
      <description>&lt;P&gt;Hi Elle, agreed. Information on this is sparse (to say the least).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This post about&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://community.hubspot.com/t5/GDPR/Optimal-workflow-design-for-multiple-buyer-personas-and/m-p/187808/highlight/true#M303" target="_blank" rel="noopener"&gt;the use of HubSpot campaigns to 'manage' HubSpot workflows&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;isn't about naming conventions per se, but it may be helpful. We typically begin our naming with &amp;lt;company_name&amp;gt; while in development, then re-name to whatever standard the client prefers. [&lt;FONT color="#808080"&gt;&lt;EM&gt;Of course, this doesn't apply to HubSpot campaigns (for reasons you originally noted)&lt;/EM&gt;&lt;/FONT&gt;.] If the client has no standards, we give them some!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Other than that, it's more difficult to organize HubSpot lists since removal of the left folder pane (see&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://community.hubspot.com/t5/HubSpot-Ideas/New-List-Tool-fixes-needed/idi-p/214745" target="_blank" rel="noopener"&gt;this post&lt;/A&gt;). - see image&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-right"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="hubspot-smart-lists-old-view.png" style="width: 400px;"&gt;&lt;img src="https://community.hubspot.com/t5/image/serverpage/image-id/14264i1A6BE76329C27B4C/image-size/medium?v=v2&amp;amp;px=400" role="button" title="hubspot-smart-lists-old-view.png" alt="hubspot-smart-lists-old-view.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Now the names have to include and additional identifier just to help locate them in large portals. And, of course, this applies to workflows, forms, and CTAs as well.&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jun 2021 11:21:00 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/246774#M782</guid>
      <dc:creator>MFrankJohnson</dc:creator>
      <dc:date>2021-06-17T11:21:00Z</dc:date>
    </item>
    <item>
      <title>Re: Best Naming Convention Practices</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/247245#M783</link>
      <description>&lt;P&gt;Hi Frank,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your response.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jan 2019 14:07:13 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/247245#M783</guid>
      <dc:creator>qturner1</dc:creator>
      <dc:date>2019-01-23T14:07:13Z</dc:date>
    </item>
    <item>
      <title>Re: Best Naming Convention Practices</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/252913#M797</link>
      <description>&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 03 Feb 2022 22:10:55 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/252913#M797</guid>
      <dc:creator>MFrankJohnson</dc:creator>
      <dc:date>2022-02-03T22:10:55Z</dc:date>
    </item>
    <item>
      <title>Re: Best Naming Convention Practices</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/253147#M798</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/1402"&gt;@MFrankJohnson&lt;/a&gt;&amp;nbsp;although you answered to this post, it still did not solve my question. So I won't be marking this as resolved. Thanks!&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Feb 2019 17:38:38 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/253147#M798</guid>
      <dc:creator>qturner1</dc:creator>
      <dc:date>2019-02-14T17:38:38Z</dc:date>
    </item>
    <item>
      <title>Re: Best Naming Convention Practices</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/254787#M812</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/76717"&gt;@qturner1&lt;/a&gt;&amp;nbsp;- I'm working with a company who is using Hubspot having come from working with many different automation solutions in the past. Personally speaking, folders while nice to have, can become very disorganized over time especially as employees come in and out of marketing. With the past few automation instances I've worked with I've tried to rely less on folders and more on naming conventions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I have tried to do in recent implementations is keep naming conventions the same across all assets within the platform. So for instance, emails and landing pages will look similar. And Hubspot does a lot to help out. If you use the search bar at the top right of the navigation it actually searches all assets like emails, landing pages and workflows. It doesn't seem to search forms yet, but maybe this is a bug that is being worked out.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Without seeing what your business structure looks like, at a high level I would try to track the following in your naming convention:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- Date the asset is first used/or the campaign launches. For naming standardization I would recommend YYYYMM, YYMM, YYQ# (19Q1) because this will keep your campaigns in order.&lt;/P&gt;&lt;P&gt;- Give the asset an identifier so you know what type of asset it is: EM for Email, LP for Landing Page, etc.&lt;/P&gt;&lt;P&gt;- If you have products or groupings within your product consider an identifier for that&lt;/P&gt;&lt;P&gt;- Consider an identifier for the stage of the CX journey that a contact is to help you fill in voids in a journey mapping.&lt;/P&gt;&lt;P&gt;- Allow for a freeform description to make things easily human readible, identifiable, or even show campaign relation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;By having these types of fields it can be as useful, if not more useful than folders so long as you know how to search for things. Also, because the searches have become so smart, it's easier to use for this then to dive through level after level of folders.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Feb 2019 23:54:15 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/254787#M812</guid>
      <dc:creator>Ben_M</dc:creator>
      <dc:date>2019-02-21T23:54:15Z</dc:date>
    </item>
    <item>
      <title>Re: Best Naming Convention Practices</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/261331#M835</link>
      <description>&lt;P&gt;What I have tried to do in recent implementations is keep naming conventions the same across all assets within the platform. So for instance, emails and landing pages will look similar. And Hubspot does a lot to help out. If you use the search bar at the top right of the navigation it actually searches all assets like emails, landing pages and workflows. It doesn't seem to search forms yet, but maybe this is a bug that is being worked out.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Mar 2019 05:17:20 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/261331#M835</guid>
      <dc:creator>john3211</dc:creator>
      <dc:date>2019-03-26T05:17:20Z</dc:date>
    </item>
    <item>
      <title>Re: Best Naming Convention Practices</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/265462#M848</link>
      <description>&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;Hi &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/76717"&gt;@qturner1&lt;/a&gt;.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;Although keeping all the assets organized is very difficult, there are some practices that we implement for our portal and our clients' portals. Most of our assets have the following naming convention:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;EM&gt;&lt;FONT size="3" face="helvetica"&gt;Type of asset | Campaign | Buyer's Journey stage | Title&lt;/FONT&gt;&lt;/EM&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;For example, a workflow email could be:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;&lt;EM&gt;WF | Inbound Marketing | Consideration | What is Inbound Marketing.&lt;/EM&gt;&lt;/FONT&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;You can use "WF" for workflows, "FU" for followup emails, "LP" for landing pages, "TP" for Thank you pages, and so on...&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;As some have pointed out, maybe adding the date would also be a good idea. For example:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;EM&gt;&lt;FONT size="3" face="helvetica"&gt;WF | 2019Q1 | Inbound Marketing | Consideration | What is Inbound Marketing?&lt;/FONT&gt;&lt;/EM&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;As for the file manager we have a folder structure that we took from this blog post:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;&lt;A href="https://www.zenpilot.com/blog/an-awesomely-organized-hubspot-file-manager" target="_self"&gt;https://www.zenpilot.com/blog/an-awesomely-organized-hubspot-file-manager&lt;/A&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;Basically our folder structure is the one mentioned in the post:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;*Free Stock Photos&amp;nbsp;&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;cta&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;email&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;identity&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;images&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;offers&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;resources&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;scripts&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;social&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;video&amp;nbsp;&lt;/FONT&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;And we try to follow the following file naming best practices:&lt;/FONT&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;All text in lowercase&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;Use hyphens instead of spaces&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT size="3" face="helvetica"&gt;Don't use accents (we're in México :)) or any special character.&lt;/FONT&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;It's really hard work but it really pays out to have everything organized. Good luck!&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3" face="helvetica"&gt;&lt;STRONG&gt;Rafa CM.&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT size="3" face="helvetica"&gt;&lt;EM&gt;Inbound Métrica - Director&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT size="3" face="helvetica"&gt;&lt;A href="https://inboundmetrica.com" target="_blank" rel="noopener"&gt;inboundmetrica.com&lt;/A&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 01 Jun 2019 13:19:46 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/265462#M848</guid>
      <dc:creator>Rafa_CM</dc:creator>
      <dc:date>2019-06-01T13:19:46Z</dc:date>
    </item>
    <item>
      <title>Re: Best Naming Convention Practices</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/358932#M1133</link>
      <description>&lt;P&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/76717"&gt;@qturner1&lt;/a&gt;&amp;nbsp;He asks everyone to do that anytime he gives a response&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 31 Jul 2020 21:07:15 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/358932#M1133</guid>
      <dc:creator>jjb868</dc:creator>
      <dc:date>2020-07-31T21:07:15Z</dc:date>
    </item>
    <item>
      <title>Re: Best Naming Convention Practices</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/568879#M1923</link>
      <description>&lt;P&gt;I found this very helpful:&amp;nbsp;&lt;A href="https://www.synx.com.au/en/knowledgebase/naming-conventions-for-hubspot" target="_blank"&gt;https://www.synx.com.au/en/knowledgebase/naming-conventions-for-hubspot&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 03 Feb 2022 20:23:09 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/568879#M1923</guid>
      <dc:creator>TracyG</dc:creator>
      <dc:date>2022-02-03T20:23:09Z</dc:date>
    </item>
    <item>
      <title>Re: Best Naming Convention Practices</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/568909#M1924</link>
      <description>&lt;P&gt;Cool!&lt;/P&gt;</description>
      <pubDate>Thu, 03 Feb 2022 20:55:31 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/568909#M1924</guid>
      <dc:creator>EChronik</dc:creator>
      <dc:date>2022-02-03T20:55:31Z</dc:date>
    </item>
    <item>
      <title>Re: Best Naming Convention Practices</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/745839#M3127</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I just submitted a request relating to naming conventions: &lt;A href="https://community.hubspot.com/t5/HubSpot-Ideas/Enforce-naming-convention-for-new-assets/idi-p/745831#M133390" target="_blank" rel="noopener"&gt;https://community.hubspot.com/t5/HubSpot-Ideas/Enforce-naming-convention-for-new-assets/idi-p/745831...&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you would find this useful, feel free to upvote!&lt;/P&gt;</description>
      <pubDate>Tue, 24 Jan 2023 08:08:30 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Best-Naming-Convention-Practices/m-p/745839#M3127</guid>
      <dc:creator>karstenkoehler</dc:creator>
      <dc:date>2023-01-24T08:08:30Z</dc:date>
    </item>
  </channel>
</rss>

