Company Information
Email Format
Technology Stack
Competitors

Bostonsofa Technology Stack

View Bostonsofa's Technology Stack

Bostonsofa uses 8 technologies like ASP.NET, CallPage, and Google Analytics. View Bostonsofa's complete Tech Stack.

Bostonsofa Programming Languages And Frameworks Technology

ASP.NET

ASP.net is an open source framework for building web applications and services with .NET and C#.

HTML

Hypertext Markup Language (HTML) is the standard markup language for documents designed to be displayed in a web browser. It can be assisted by technologies such as Cascading Style Sheets (CSS) and scripting languages such as JavaScript.

JavaScript

JavaScript is the programming language of HTML and the Web.

jQuery

jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML. It is free, open-source software using the permissive MIT License. Web analysis indicates that it is the most widely deployed JavaScript library by a large margin.

PHP

PHP: Hypertext Preprocessor is a server-side scripting language designed for Web development, but also used as a general-purpose programming language. PHP code may be embedded into HTML code, or it can be used in combination with various web template systems, web content management systems, and web frameworks.

Bostonsofa Customer Management Technology

CallPage

CallPage helps convert web-visitors into sales calls by providing immediate responses from company reps through a customizable button and widget.

Bostonsofa Business Intelligence And Analytics Technology

Google Analytics

Google Analytics allows users to measure sales & conversions, plus gain fresh insights into how visitors use sites, & how they arrived on site.

Smartlook

Smartlook helps business owners to track user activity and identify problems on their website using heatmaps, visitor screen recordings, and analytics. Smartlook is a qualitative analytics solution for web and mobile helping over 200,000 businesses of all sizes and industries answer the whys behind users actions why do users churn, or why arent they using a feature, or why are they skipping onboarding? Now user can eliminate the guesswork.