Glossary
Last updated November 18, 2026
Dash Glossary
Use this glossary to understand the terms used throughout Dash. Related terms are grouped together so you can see how customer records, parking activity, marketing, and reporting connect.
Parking Activity and Customer Profiles
Transactions
Records of parking purchases or payments imported or recorded in Dash. Transaction types include Transient, Monthly, Flex, and Reservation.
A transaction can include the amount, date, location, payment provider, and associated customer or vehicle information. Available details depend on the source data.
Parkers
Customer profiles used to bring together parking activity associated with a person or vehicle. Dash distinguishes between known parkers and unknown parkers based on whether the profile is linked to a contact record.
Known Parkers
Parker profiles linked to a contact record in Dash. The contact can contain identifying information such as a name, email address, or phone number.
Known parkers relate to the contact records used for Dash’s contact-based billing. Your organization’s Dash charges vary with its billable contact volume under its plan.
The number of transactions a parker makes is separate from the number of contact records. A known parker with several transactions does not represent a new contact for each transaction.
Unknown Parkers
Parker profiles that are not linked to a contact record. Dash may recognize their parking activity through a vehicle identifier, such as a license plate, without having contact information for the person.
An unknown parker can still contribute parking activity and revenue to reporting.
Persona
A category describing when a parker typically parks. Personas help you understand parking patterns and build relevant audiences.
For example, Commuter describes a pattern of long weekday morning stays. It does not confirm the person’s occupation or reason for parking.
| Persona | Parking pattern |
|---|---|
| Commuter | Weekday sessions starting between 4:00 AM and 10:00 AM and lasting at least 6 hours. |
| Weekday Morning | Weekday morning sessions starting between 4:00 AM and 10:00 AM, generally lasting less than 6 hours. |
| Weekday Midday | Weekday sessions starting between 10:00 AM and 4:00 PM. |
| Weekday Evening | Weekday evening and overnight parking. |
| Weekend Morning | Saturday and Sunday daytime sessions starting between 4:00 AM and 4:00 PM. |
| Weekend Evening | Friday evening and weekend evening or overnight parking. |
Dash uses the location’s local time when classifying activity. A parker’s persona reflects their predominant recorded pattern; individual visits may fall into different categories.
Frequency
A category describing how often a parker returns, based on the activity counted in the relevant view.
The default customer-profile frequency groups are:
| Frequency | Default count |
|---|---|
| Single use | 1 |
| Occasional | 2–4 |
| Moderate | 5–9 |
| Frequent | 10–19 |
| Habitual | 20 or more |
Your organization can use different frequency labels or thresholds. Some dashboards also use broader groupings, so check the count range displayed beside the label.
Persona describes when someone tends to park. Frequency describes how often they park.
Leads and Data Collection
Leads
Records of potential customers’ inquiries or expressions of interest. Leads can come from forms, websites, integrations, or manual entry.
A lead represents an inquiry. One person can have several lead records, such as separate inquiries for different locations. Sharing an email address does not automatically combine those inquiries.
See What Is a Lead?.
Lead Source
The broad channel or origin recorded for a lead, such as Website, QR Code, Referral, or Dash Form.
Lead Source helps you understand where inquiries come from and can be used in reporting, audience selection, and conversion rules.
For leads created by Dash Forms, the source is set in the form configuration. It is not automatically changed based on how the visitor reached the form.
Lead Source Details
Additional information that makes a lead’s source more specific.
For example:
| Lead Source | Lead Source Details |
|---|---|
| QR Code | Lobby signage |
| Website | Monthly parking inquiry |
| Partner Page | Property management website |
Use Lead Source for the broad channel and Lead Source Details for the particular placement, partner, or activity within that channel.
Pages
Customer-facing landing pages built and managed in DashPages. A page can present parking information, promote an offer, and include a form that collects inquiries.
A page provides the content and experience a visitor sees. A form collects the information they submit.
Forms
Collections of fields used to capture information, such as parking inquiries, sign-ups, feedback, or check-ins.
A Dash Form can have its own public URL or be embedded in a Dash Page.
A form submission is the response someone sends through a form. It creates a lead only when lead creation is enabled and the submission meets the lead requirements. Not every form submission is a lead.
See Setting Up a Form.
Audiences, Campaigns, and Triggers
Audience
A group of parkers or leads selected using criteria such as location, parking activity, frequency, spending, or lead information.
Audience Builder lets you define and save these criteria for use in marketing.
For example, an audience could include occasional parkers at a particular location who parked within the last 90 days.
An audience estimate is not a guarantee that every matching person will receive an email. Recipient eligibility and delivery restrictions can affect the final send.
Campaign
A planned communication to a selected audience, such as a parking promotion, customer reactivation message, or location notice.
A campaign brings together the audience, message, timing, and any results you want to measure.
A single-send campaign goes out once. A triggered communication runs automatically when its configured event and conditions are met.
Trigger
An automated rule that responds to an event in Dash and performs a configured action, such as sending an email.
Examples include responding to a form submission, following up on a new lead, or sending a message after a customer’s first qualifying transaction.
The event starts the evaluation. The trigger’s filters and delivery rules determine whether an action occurs and who receives it.
See Triggers.
Send Type
The meaning of Send Type depends on where it appears.
On the Triggers page, it identifies the purpose of the email:
| Send Type | Meaning |
|---|---|
| Promotional | Marketing communication intended to encourage an action or purchase. Promotional triggers can measure conversions and respect marketing opt-outs. |
| Operational | Service-related communication, such as information someone needs about an inquiry or service. Operational triggers do not measure conversions. |
During campaign setup, Send type describes when the communication sends:
| Send type | Meaning |
|---|---|
| Triggered | Sends automatically when the configured event and conditions are met. |
| Single send & Scheduled | Sends once at the selected time. |
| Recurring | A repeated sending schedule. This option is marked Coming soon and is not currently selectable. |
Trigger Results and Revenue
Trigger Revenue
Revenue attributed to qualifying activity after a promotional trigger emails someone.
The Revenue card combines transient revenue and monthly revenue. For an attributed monthly permit, Dash counts its rate for each month it has been active so far.
Revenue depends on the trigger’s measurement rules, conversion window, location filters, and Count conversions for selection. It does not include every purchase made by everyone who received an email.
Qualified Customers
The distinct people emailed by triggers that measure conversions.
Each person counts once, even if they receive several emails. Bounced emails do not count.
In this metric, “qualified” means included in the measured email audience. It does not mean the person has already purchased parking.
Trigger Influence Rate
The percentage of qualified customers who subsequently make a qualifying purchase or conversion attributed to a trigger.
Influence rate = Customers with a qualifying conversion ÷ Qualified customers × 100
For example, if 100 qualified customers receive trigger emails and 12 subsequently have a qualifying conversion, the influence rate is 12%.
The result changes with Count conversions for.
Influence rate measures what happened after an email. It does not establish that the email caused the purchase, because it does not compare recipients with a group who received no email.
Conversion Window
The period after a trigger email is sent during which an action can qualify for attribution to that trigger.
The action might be a parking purchase, a new monthly permit, or a lead conversion, depending on what the trigger measures.
Count Conversions For
A reporting control that changes the evidence required to include a conversion.
| Selection | What it counts |
|---|---|
| Anyone emailed | Qualifying conversions after someone receives the email, without requiring a tracked open or click. |
| Opened it | Qualifying conversions where the recipient opened or clicked the email first. |
| Clicked it | Qualifying conversions where the recipient clicked the email first. |
| Promo usage | Purchases using the trigger’s promo code. A trigger without a code shows No promo code. |
A redeemed trigger promo code counts at every selection.
Open and click tracking have limitations. A person may act without clicking, and some email applications load messages automatically.
Trigger Sends
The number of emails sent by triggers. The chart separates promotional and operational sends when both are present.
Test sends are excluded. A person who receives several emails can contribute several sends.
Customer LTV Growth
On the Triggers page, attributed revenue divided by the number of customers who converted.
Customer LTV growth = Trigger revenue ÷ Customers with a qualifying conversion
This includes the activity counted under the trigger’s measurement rules and the accumulated monthly revenue from attributed permits. It does not represent the customer’s entire lifetime spending or a proven increase caused by the email.
Revenue per Send
Attributed revenue divided by the emails sent by triggers that measure conversions.
Revenue per send = Trigger revenue ÷ Measured trigger sends
Test sends are excluded. Operational sends are not included in this denominator.
MRR Won
The monthly recurring revenue associated with monthly permits attributed to a trigger.
For example, two qualifying permits with monthly rates of $100 each represent $200 MRR won. This expresses a monthly rate rather than the total revenue accumulated over several months.
Still Paying
The portion of attributed monthly recurring revenue associated with permits that are still paying.
This helps distinguish the monthly revenue originally won from the amount retained.
Reading Trigger Results Over Time
The date range on the Triggers page selects the emails being measured. Qualifying results can occur after those emails were sent, so recent results may continue to grow.
Location and city filters also affect the figures: revenue follows purchases at the selected locations, while send counts follow emails sent for those locations.
Email and Campaign Performance
Total Reach
On the Campaigns summary, the sum of the latest estimated audience sizes across campaigns.
This is an estimate of audience volume. It is not a count of confirmed deliveries or distinct people across all campaigns. The same person can be included in several campaign estimates, and campaigns that have not sent can contribute to the total.
Open Rate
The percentage of delivered emails with a recorded open.
Open rate = Unique opens ÷ Delivered emails × 100
“Unique” means repeated opens of the same email do not increase its unique-open count.
Some email applications load messages automatically, while others block tracking images. A recorded open does not necessarily mean someone read the message.
Click Rate
The percentage of delivered emails with a recorded link click.
Click rate = Unique clicks ÷ Delivered emails × 100
Repeated clicks on the same email do not increase its unique-click count. Unsubscribe clicks are excluded from the trigger click-rate metric.
Click-to-Open Rate
The percentage of opened emails that also received a link click.
Click-to-open rate = Unique clicks ÷ Unique opens × 100
This uses opened emails as the denominator. Click rate uses delivered emails.
Total Clicks
The total number of recorded click events. Repeat clicks can increase this count.
For example, one recipient clicking three times can contribute 3 total clicks but only 1 unique click for that email.
Check the label and reporting context: some campaign lists display unique clicks, while detailed results distinguish unique clicks from total clicks.
The Total Clicks card on the Campaigns summary is not currently populated.
Average Open Rate
A campaign-summary measure intended to summarize open performance across campaigns.
The Average open rate card on the Campaigns summary is not currently populated. A dash means the summary value is unavailable, not that no one opened the emails.
Average Click Rate
A campaign-summary measure intended to summarize click performance across campaigns.
The Average click rate card on the Campaigns summary is not currently populated. A dash means the summary value is unavailable, not that no one clicked.
Delivered / Delivery Rate
Delivered emails are messages accepted by the recipient’s email service. Delivery does not guarantee placement in the inbox or that the message was read.
Delivery rate = Delivered emails ÷ Sends × 100
Bounced / Bounce Rate
Bounced emails are messages that could not be delivered.
Bounce rate = Bounced emails ÷ Sends × 100
Unsubscribed / Unsubscribe Rate
Recipients who opted out through the email.
Unsubscribe rate = Unsubscribes ÷ Delivered emails × 100
Marked Spam / Spam Complaint Rate
Emails reported as spam by recipients.
Spam complaint rate = Spam complaints ÷ Delivered emails × 100
Unavailable Results
A dash can indicate that a metric is unavailable or cannot be calculated because there is no denominator.
For example, an open rate cannot be calculated when no emails have been delivered. This is different from a measured rate of 0%.
Was this page helpful?
