You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Account-audiences article
* Debugger
* ID Res eComm example
* Audiences Overview
* Computed Traits
* Identity Resolution Overview
* Identity Resolution Onboarding
* Profiles Space Setup
* ID Resolution Settings
* Journeys Key Terms
* Engage GDPR
* ID Res use cases
* Nav stubs
* Build a Journey
* Audiences and space setup updates
* Journeys FAQ Best Practices
* Update computed traits location
* Send Data
* product limits
* Sql traits
* add example csv files
* Using Engage Data
* Engage and Warehouses
* Profile API
* Audiene Organization
* Quickstart
* FAQs
* Journeys use cases
* Remove Personas screenshot
* Journeys Logic
* Journeys Overview and Warehouses update
* Profiles External IDs
* Space setup nav update
* use standard layout
* Use standard search, refactor overview
* Profile API fixes
* Fixing profiles nav
* Match user_id value with screenshot
* Use Cases cleanup
* CSV Uploader updates
* Deep clean
* move CSV upload
* Engage Intro and Identity Warehouse
* Link and nav fixes
* forgot to save this one
* Remove Essentials limits
* Update nav
* More nav updates
* More nav updates
* Plan Grid work to support Engage SKUs
* Add Profile API Limits to nav
* replacing instances
* Add plan details as metadata
* Personas replacements
* Personas replacements
* Add recent externalID updates to Engage branch
* Move journey analytics
* and add it to the nav
* remove old layout
* hide empty docs from nav
* Minor email and SMS template edits
* CSV upload navigation updates
* file and nav cleanup
* Hide internal logo
* RIP Personas
* link fixes
* Hide empty articles
* quickstart in the nav
* Update Engage icon and blurb link
* Profiles Overview
* Update Engage blurb
* Update Engage blurb
* get onboard
* FAQs split
* Add Onboarding Redirect
* Add Channels product limit
* Profiles GDPR
* Profiles Quickstart split
* Add Engage Settings Content
* Add split content to sidenav
* fixed broken links
* Beta check and unpublish contact page
* Quickstart updates
* Remove Engage Support References
* Hide Engage Settings Pages
* Update instance of Engage Pro to Premier and link fixes
* Relink images
* additional link fixes
* Add Journeys Step Types Page [DOC-587] (#589)
* Add Journeys Step Types Page DOC-587
* Vale Sentence Case Fixes DOC-587
* Update Journey Re-entry FAQ
Co-authored-by: rchinn-segment <[email protected]>
Co-authored-by: pwseg <[email protected]>
Co-authored-by: pwseg <[email protected]>
Copy file name to clipboardExpand all lines: src/_data/glossary.yml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@ Analytics.js: |
2
2
The Segment Javascript library wrapper, which makes it simple to send your data to any tool without having to learn, test or implement the new API for each tool every time.
3
3
4
4
API: |
5
-
Application Programming Interface. In software, this term describes a way of interacting with software in an automated fashion, without the use of a user-interface designed for humans. In Segment, we call the standard calls (`track`, `page` and `screen`, `identify` and `group`) our API. We also provide the [Public API](/docs/api/), which you can use to configure sources and destinations, and perform other functions in your workspace, without logging in using a web browser.
5
+
Application Programming Interface. In software, this term describes a way of interacting with software in an automated fashion, without the use of a user-interface designed for humans. In Segment, we call the standard calls (`track`, `page` and `screen`, `identify` and `group`) our API. We also provide the [Public API](/docs/api/public-api), which you can use to configure sources and destinations, and perform other functions in your workspace, without logging in using a web browser.
6
6
7
7
App: |
8
8
The app is what we call the main Segment web application, the part you log in to, and where you configure sources and destinations, see events in the debugger, manage your tracking plan, and so on.
@@ -42,7 +42,7 @@ Computed trait: |
42
42
[Computed traits](/docs/personas/computed-traits/) are per-user, or per-account [traits](#traits) that you create or “compute” in [Personas](/docs/personas/). When you build a Computed Trait, Personas adds it to relevant user profiles.
43
43
44
44
Custom trait: |
45
-
[Custom Traits](/docs/personas/audiences/#custom-traits) are user or account properties collected from all the events you send to Personas. For example, you can add any properties that you send as a part of your track calls or identify calls (`email`, `first_name`, `last_name`) as custom traits. You can then view them in the profile explorer, and use them in your audiences, computed traits and SQL traits.
45
+
[Custom Traits](/docs/engage/audiences/#custom-traits) are user or account properties collected from all the events you send to Personas. For example, you can add any properties that you send as a part of your track calls or identify calls (`email`, `first_name`, `last_name`) as custom traits. You can then view them in the profile explorer, and use them in your audiences, computed traits and SQL traits.
46
46
47
47
Debugger: |
48
48
This is the place in the app where you can see your events flowing through Segment
0 commit comments