Attributes
Used for content types/asset content
Used for pdf assets in the DAM; possibly some types of images
- Tagging has not been done for assets but will start being done through the MediaValet integration in February 2024
Content Type
- Identifies the content type (Article, Blog Post, Brochure, Datasheet, Demo, Ebook, Infographic, Podcast, Report, Solution Brief, Success Story, White Paper)
- May appear as a Card Label on the card used in Card Perspectives and/or in Card Carousels
- In roadmap: Videos (go live still TBD)
- Used for Page Labels that appear in search results
- Used for Content Type facet on these pages:
Language
- Web pages:
- Not applicable; this data can be acquired from the page URL
- Assets:
- Documents: Should be applied to items hosted under /documents, especially the translated pdfs
(Does AVEVA want English tag to be used or apply only to the translated language pdf? - Images: Could also be applied to /images if a valid use case - maybe language-specific logos)
- Used for assets in MediaValet that are synced with AEM Assets
- Documents: Should be applied to items hosted under /documents, especially the translated pdfs
Region
- Should be applied to Press Releases (although facet is not currently displayed on the front end)
Country
- Should be applied to Press Releases for the Country facet
- Should be applied within the OfficeLocation.xlsx file used to generate the Country dropdown on the Office Locations page
- Do not use for Distributors or System Integrators; separate Country lists are used for those page types under the APIs tag
Office Type
- Should be applied within the OfficeLocation.xlsx file used to generate the Card Label(s) on each office card on the Office Locations page
Year
- Should be applied to these types of pages: Blog Posts, Podcasts, and Press Releases (Blog Posts are not yet being tagged consistently, but they should be); derive Year from the Start Date Card Properties field
- Should be applied to these types of pages based on the Copyright Year of pdf linked from AEM page or Marketo form: Article, Brochure, Datasheet, Report, Success Stories, White Papers (These content types are not yet being tagged)
- Applied to AVEVA Operations Control blog posts for an isolated web page experience (Year tag to be applied to all blog posts moving forward)
City
- Should be applied within the OfficeLocation.xlsx file used to generate the alphabetical order within a Country grouping on the Office Locations page
Topics
Used for Page Types facet on Global Search page
Used for Page Labels that appear in search results (effective in September 2022)
Industry (and its Industry Subsector tags)
- Used for pages with /industries in their URL
- Used for Page Label to identify page type
- Used to identify industry and industry subsector content
- Should apply industry subtags to Industry/Solution/Product pages and Perspectives pages
- Powers facets on Global Search, Products, and Perspectives search pages
- Can be used in Card Carousel for Dynamic Tags option
- Tags and subtags should match the flyout navigation in the Header
- Do not use for System Integrators Industry tag list; the System Integrator Industry tag list lives under APIs > System Integrators > Industry
Solution (and its Solution Subcategory tags)
- Used for pages with /solutions in their URL
- Used for Page Label to identify page type
- Used to identify solution and solution subcategory content
- Should apply solution subtags to Industry/Solution/Product pages and Perspectives pages
- Powers facets on Global Search, Products, and Perspectives search pages
- Can be used in Card Carousel for Dynamic Tags option
- Tags and subtags should match the flyout navigation in the Header
Product
- Used for pages with /products in their URL
- Used for Page Label to identify page type
- Used to identify product content
- Product Name:
- Each product page must be tagged for its respective product name; this is required for Marketo and its lead gen routing rules
- Any page that relates to the product can be tagged with the product name (used for Card Carousel with dynamic tag option and for future personalization activities)
- For Marketo: Limit Tag Title, including spaces, to 55-60 characters so Product Name will fit the width of the product dropdown in the form overlay modal; otherwise, the Product Name will be truncated after 55 characters
- Future enhancement: Create 3 subtags under Product Name tag for AVEVA, AVEVA DX, and Partner DX to segment each product type and to make picklists more usable for CMS Authors in the backend
- Product Availability:
- Apply one or more options per product page
- This facet is displayed on the Products and Global Search pages of all language sites
- Product Owner:
- AVEVA and AVEVA DX products get tagged for "AVEVA"
- Partner DX pages get tagged for "Partner"
- This facet is displayed on the Products and Global Search pages of the EN site only; not applicable for international sites because they do not feature DX products
- Offer Type:
- Apply one or more options per product page
- This facet is displayed on the Products and Global Search pages of the EN site only; not applicable for international sites because they do not feature DX products
- Vendor Name:
- AVEVA products and AVEVA DX products get tagged for "AVEVA Group plc"
- Partner DX products get tagged for their respective vendor name
- This facet is displayed on the Products and Global Search pages of the EN site only; not applicable for international sites because they do not feature DX products
- Product Name:
Partner
- Used for pages with /about/partners in their URL
- Used for Page Label to identify page type
- Has subtags for Global Alliances pages
Careers
- Used for pages with /about/careers in their URL
- Used for Page Label to identify page type
Sustainability
- Used for pages with /about/sustainability in their URL
- Used for Page Label to identify page type
About AVEVA
- Used for pages with /about/about-aveva in their URL (exceptions: /about/careers; /about/partners; /about/sustainability - these pages have their own tag)
- Used for Page Label to identify page type
Legal
- Used for pages with /legal in their URL
- Used for Page Label to identify page type
Support
- Used for pages with /support-and-success in their URL
- Used for Page Label to identify page type
Training
- Used for pages with /training in their URL
- Used for Page Label to identify page type
Academia
- Used for pages with /academia in their URL
- Used for Page Label to identify page type
Press Release
- Used for pages with /about/news/press-releases/yyyy in their URL
- Used for Page Label to identify page type
Contact
- Used for the Contact Us page
Product Resource
- Used for product-oriented pages that use the /info/ taxonomy
Personalization
Used for personalization in Target
Persona
- Not currently being used, but in place for future Target goals/activities
Customer Journey
- Not currently being used, but in place for future Target goals/activities
Interest
- Identifies high-level topics of interest to users
- Not currently in use for any front-end facets, but can be used for topical card carousels or for future Target goals/activities
- Could be used when a new tag does not meet rest of tag governance and needs a place to reside even through it has no function within AEM
Target Audience
- Used for assets in MediaValet that are synced to AEM Assets
Locale
Locale tags are used in the hreflang implementation. Do not delete them.
So that there would be at least 1 reference for each Locale subtag, this tag has been applied to the home page of each site, but it is not serving a functional purpose for the home pages.
APIs
Used for the dropdowns on the Distributors and System Integrators pages in the Partners site section; no AEM web pages should use these tags
System Integrators
- Used for the dropdowns on the System Integrators page
Distributors
- Used for the Country dropdown filter on the Distributors page