These are the terms you will meet in Studio and across this documentation. Where a term appears as a label in the product, it is shown here exactly as it appears.
| Term | What it means |
|---|
| Datahash Studio | The platform. Signals, Segments, Single View and the other Datahash products all sit inside Studio. |
| Account | Your organization in Studio. An account contains one or many projects. Billing sits at the account level. |
| Project | The tenancy unit. Connections, mappings and data live inside a project. A plan is chosen when a project is created, and that determines what the project is billed for. |
| Signal | One event travelling from one source to one destination. The same event sent to two platforms is two signals. |
| Term | What it means |
|---|
| Source | Where data comes from. Grouped by category in the Sources list. |
| Destination | Where data goes. Grouped by purpose in the Destination list. |
| Connector tile | How an integration appears before you configure it. Once configured it appears as a connector widget, or connected instance. |
| Connection | A configured link to a source or destination. Status is either Pending or Completed. |
| Instance | A single configured use of a connector. One connector can have several instances, for example two FTP folders. |
| Integration Type | The payload type selector on a source. It determines which destinations the connection can feed. |
| Field Mapping | The screen where you match your columns to the fields a destination expects. |
| Gateway | A separate section for gateway style integrations. It lists the Conversions API Gateway and the Signals Gateway as separate entries. |
If you leave setup before finishing, the connection stays Pending. Select the connection name to pick up where you left off.
Each use case corresponds to a pipeline type, and most of them are selected on the source as an Integration Type.
| Pipeline | Use case |
|---|
| Online CAPI | Web conversions |
| Offline CAPI | Offline conversions |
| Custom Audience | Custom audience |
| Meta Conversions API for CRM, also called Meta CLO | Lead and CRM conversions to Meta |
| Google Enhanced Conversions for Leads | Lead conversions to Google |
| Snapchat Leads CAPI, TikTok CRM Events CAPI, LinkedIn Leads CAPI | Lead conversions to those platforms |
| Google Store Sales | Store sales conversions |
| Google Product Catalog, Google Local Product Inventory | Product catalog |
| Messaging Ads, also called CTX Ads | Messaging conversions |
| Lead Ads and Google Forms | Lead generation |
| Analytics | Web analytics |
| Term | What it means |
|---|
| Normalization | Putting an identifier into a consistent shape before hashing, for example lowercasing an email address or putting a phone number into E.164. |
| Hashing | One way conversion of an identifier to a fixed length string using SHA-256. It cannot be reversed. How to apply it. |
| Deduplication | Recognizing that a browser copy and a server copy of the same event are one conversion, so it is counted once. |
| Event Quality | A destination platform’s own measure of how likely the customer information on your events is to match to one of its users. Each platform names and calculates it differently: Meta reports Event Match Quality (EMQ) from 0 to 10 on web events from the last 48 hours, and Pinterest reports an Event Quality Score. The advice is the same everywhere, which is to send every identifier you hold, correctly normalized. |
| Term | What it means |
|---|
| NeoTag | One Datahash tag that serves multiple platforms from a single implementation. |
| dhPixel | A Datahash tag that replaces a single platform’s base pixel. |
| Subdomain | A subdomain of your own site that the tag loads from and reports to, which is what makes collection first-party. One per project. See Subdomain setup. |
| Conversions API Gateway | Meta’s server-to-server conversions product, hosted by Datahash. It sends events Meta already has through a connected dataset rather than collecting them itself. |
| Signals Gateway | Meta’s first-party data platform, hosted by Datahash. It collects website interactions through its own pixel and forwards them to Meta. |
