Sitecore Acronyms

If you are working with Sitecore technology, then you must be aware of some common Sitecore acronyms. So here is the list of some of the heavily used Sitecore acronyms:

1. A/B Testing

With A/B testing, you can test and validate your assumptions on a small group of your customers before you send the final email campaign to the rest. This ensures that you always send the most appealing and relevant email campaigns to your customers.

2. CD – Content delivery

The Content Delivery (CD) role handles requests from visitors across channels, determines which content to serve, and renders output in the relevant format for the channel.

3. CM – Content Management (CM)

The Content Management (CM) role enables authors to create, manage, and publish content.

4. CMS – Content Management System

A content management system is a software application that can be used to manage the creation and modification of digital content. CMSs are typically used for enterprise content management and web content management.

5. CTA – Call To Action

CTA’s allow you to create a clear and prominent link to other relevant sections within Sitecore, PDFs, and other useful sources of information

6. CXM – customer experience management

Customer experience management is all about getting better results by adapting to changes in how your customers are interacting, and where they are interacting with you.

7. DEF – Data Exchange Framework

You can Sitecore Data Exchange Framework to model processes that synchronize data between multiple systems. It is designed to facilitate the transfer of data between systems. It allows you to define the logic needed to read data from a source system, transform that data into a format that is compatible with a target system, and write the transformed data into a target system.

8. DMS – Sitecore’s Digital Marketing System

Sitecore DMS is a module within Sitecore CMS which is designed to improve digital marketing strategies and boost website conversions

9. EXM – Email Experience Manager

Email Experience Manager (EXM) to create highly customizable email campaigns and make them both personal and relevant to your customers.

10. FXM – Federated Experience Manager

Federated Experience Manager (FXM) is a module that you use with the Sitecore® Experience Platform™ (XP) to both serve web content as well as capture visitor behavior on non-Sitecore sites

11. JSS – Sitecore JavaScript Services

JSS is a complete SDK for JavaScript developers allowing to build full-fledged solutions using Sitecore and modern JavaScript UI libraries and frameworks (React.js and Angular)

12. PaaS – Platform as a Service

PaaS, is a category of cloud computing that provides a platform and environment to allow developers to build applications and services over the internet

 

13. PXM – Print experience manager

PXM is a platform that provides a bridge (various bridges, in fact) between Adobe InDesign and Sitecore.

14. SBOS – Sitecore Business Optimization Strategies

Supports Sitecore customers and implementation partners through their transformation from marketing with a brand-centric, static web presence to marketing with a personalized, contextual, omnichannel digital platform that creates great customer experiences and builds loyal customers

15. SIF – Sitecore Installation Framework

The Sitecore Installation Framework is a Microsoft PowerShell module that supports local and remote installations of Sitecore, and it is fully extensible

16. SIM – (Sitecore Instance Manager)

SIM is an open source tool for managing the local park of Sitecore instances. You can install, locate, maintain, reinstall or delete Sitecore products. It has API and plugin engine so you can extend it for any your need

17. SPE – Sitecore PowerShell Extensions

SPE Module is a Sitecore development accelerator which can drastically increase your productivity and curtail the amount of time it takes to deliver a Sitecore solution.

18. Speak – Sitecore Process Enablement & Accelerator Kit

Speak  is a framework for developing Sitecore applications with a consistent interface quickly and easily.

19. SXA – Sitecore Experience Accelerator

SXA separates structure from design, so front-end designers, creative designers, content authors, and developers can work in parallel and you can deploy and maintain multiple sites quickly and cost effectively

20. WFFM – Web Forms for Marketers

It aids marketers to create simple forms, without additional help from the developer. One just needs to add basic input fields (text boxes, checkboxes), save actions and validators, and voila, you’re done within a few clicks! This module is a great tool to help marketers create and published their own forms.

21. xConnect

xConnect is the service layer that sits in between the xDB Collection database and xDB index, and any trusted client or device that wants to read, write, or search contact and interaction data. No other system has direct access to the xDB Collection database or the xDB index.

22. XC – Sitecore Experience Commerce

XC deliver personalized shopping experiences by integrating commerce and digital marketing

23. xDB – Experience Database

The Sitecore Experience Database (xDB) is a big data marketing repository that collects and connects customer interactions to create a comprehensive, unified view of each individual customer

24. XM – Sitecore Experience Manager

Sitecore Experience Manager (XM) empowers you to deliver the right content, to the right person, exactly at the right time

 

25. XP – Sitecore Experience platform

World-class content management combined with deep data insights deliver omnichannel, personalized interactions in real time

Sitecore xDB Troubleshooting

Below are the some of the useful xDB troubleshooting reference:

1. Determine the interactions for each facet by month, run against your xDB shards:

select facetKey,
DATEPART(year,lastmodified) as ‘Year’,
DATEPART(month,lastmodified) as ‘Month’,
count(distinct interactionId) as ‘NumberOfInteractions’
from [xdb_collection].[InteractionFacets]
group by facetKey, DATEPART(year,lastmodified), DATEPART(month,lastmodified)
order by facetKey, DATEPART(year,lastmodified), DATEPART(month,lastmodified)

2. Determine the number of visits by language and month, run against your reporting database:

select SiteNameId,
DimensionKey,
DATEPART(year,[Date]) as ‘Year’,
DATEPART(month,[Date]) as ‘Month’,
sum(visits) as ‘NumberOfInteractions’
from [dbo].[Fact_LanguageMetrics] lm
inner join [dbo].[DimensionKeys] dk on lm.DimensionKeyId = dk.DimensionKeyId
group by SiteNameId,
DimensionKey,
DATEPART(year,[Date]),
DATEPART(month,[Date])
order by SiteNameId,
DimensionKey,
DATEPART(year,[Date]),
DATEPART(month,[Date])

3. Extract Email addresses from xDB shards:

select c.contactid, c.created, c.LastModified, cf.FacetData, JSON_VALUE(cf.FacetData, ‘$.PreferredEmail.SmtpAddress’) AS Email
from [db-shard0db].[xdb_collection].[ContactFacets] cf
inner join [db-shard0db].[xdb_collection].[Contacts] c on c.ContactId = cf.ContactId
where cf.FacetKey = ‘Emails’

4. Determine xDB data flow and pinpoint/analyze issues:

• To check what user you are within xDB you will need to have the value of your SC_ANALYTICS_GLOBAL_COOKIE. Copy the value without ‘| False’.
• To force a Session_End you can upload the following .aspx file to a location on your website: “here– Now browse through your website(s), and end the session by hitting the sessionkill.aspx. This should trigger the the xDB data to be send towards your SQL shards.
• Connect to your SQL server and execute the query below on every shard:

SELECT *
FROM [xdb_collection].[DeviceProfiles]
where DeviceProfileId like ‘%VALUEFROMCOOKIE%‘
order by LastModified desc

• The ID that is found in column “LastKnownContactId” – will map a new “ContactId” – “XXX” – This ID will be used for identification, for example in the Interaction table.
• To check whether page events are written to the “interaction” tables

SELECT * from

SELECT * from [xdb_collection] .[Interactions]
where ContactId = ‘XXX’

• In case you are missing interactions, you might want to check Application Insights whether there are Session_End submits that are failing [KQL] :

traces
| where timestamp > ago(30d)
| where operation_Name contains “GET /SESSION END”

For more detailed information related to xDB troubleshooting refer the below document:

Troubleshooting xDB data issues

Troubleshooting xDB Cloud