> ## Documentation Index
> Fetch the complete documentation index at: https://docs.embeddables.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Glossary

> Key terms that we use here at Embeddables

#### Contact

See: [End-User](#end-user)

***

#### Embeddable and Embeddables

Embeddables (capital E) is the name of our company and product. We always capitalize the E in Embeddable or Embeddables when referring to the things you ***build*** in our platform.

So you build, embed and push live an Embeddable. And you do so using the product Embeddables.

Enjoy building Embeddables in Embeddables!

***

#### End-User

*Note: Also known as a [Contact](#contact).*

This is a real life person who is currently viewing/completing, or has previously viewed/completed, one of your Embeddables.

This is distinct from an Embeddables User, which is someone who builds Embeddables in our builder - like you!

***

#### Entry

See: [User Data](#user-data)

***

#### Group

A Group corresponds to a billing account with Embeddables.

If you are a customer of Embeddables that you would typically have a single Group in our system.

Groups can contain multiple [Projects](#project).

***

#### JSON-Only Feature

These are new features in the Builder, which are available for use but don't yet have
buttons/inputs in the Builder cards to be able to add/modify them.

**Advanced users only:** If you want to use these features in the meantime, you can
edit the JSON of the component/page/Embeddable to add/update the feature manually.

***

#### Project

Each project is a collection of Embeddables, to help you organize them into different... well, projects!

Your various Projects are all associated with your [Group](#group).

If an [End-User](#end-user) who visits multiple Embeddables that are all within the same Project, they will have multiple Entries grouped within a single Contact.

On the other hand, if an End User visits multiple Embeddables that span several Projects (even if they are in the same Group), this will create multiple Contacts.

***

#### User Data

*Note: Also known as an [Entry](#entry).*

This is the set of data that an [end-user](#end-user) of an Embeddable has at any time, for example their email address or the answer they gave to a question.

It is stored in `JSON` format and the schema is dependent on the Embeddable that they are using.

A user that has taken multiple Embeddables will have a different User Data for each one. In our database, this is known as one [Contact](#contact) corresponding to multiple [Entries](#entry).

<Note>
  This page is incomplete, and will be expanded soon - watch this space!
</Note>
