Introduction
Overview
This guide provides overview and procedural information for Sugar Market features. Please refer to the Sugar Market Integration Guide for guidance on configuring your CRM integration. Troubleshooting, use cases, best practices, and legacy tools are documented in Sugar Market Help Articles, which are also linked from their relevant topics in this user guide.
Please also refer to the Welcome to Sugar Market page, which provides an overview of the Sugar Market team and learning resources.
Topics
This page covers how to access your Sugar Market instance, set your display language, and get support if your run into any questions or issues.
This documentation covers the basics of Sugar Market's user interface.
There are several options you can configure for your entire Sugar Market account and your own user preferences. With the exception of user preferences, you will need the Admin Navigation role to make changes to the settings described on this page.
Sugar Market users with the Admin Navigation role can create and manage roles and user accounts, including security permissions.
GDPR regulations state that proper context must be provided to customers around how cookies are used on your site and how they are being used on them as a user. This means that new visitors who reside in the EU need to be given a choice of whether they want to accept or decline cookies being dropped on them. In addition, contacts need to have the ability to change their cookie settings at any point after they have initially made a decision.
A cookie, also known as an HTTP cookie, web cookie, or browser cookie, is a small piece of data sent from a website and stored in a user's web browser while the user is browsing a website. Sugar Market's cookie server will cookie every visitor using the domain msgapp.com. When a visitor hits your website or submits a form, Sugar Market captures a unique ID that represents the email address from the msgapp domain. This ID is compared to a primary table that contains all the unique IDs and relates them to the email address. If the visitor exists in your contact/lead table, then Sugar Market can show the email address in the web activity since the person was cookied previously.