# Glossary (/getting-started/glossary) ## Overview [#overview] This page lists the terms that the LettrLabs help pages use. Each row gives one term, what it means, and its old name in the earlier LettrLabs app. You can use the glossary to: * Find what a term on a help page means. * Find the new name of a term from the earlier app or an older support article. * Tell two close terms apart, such as Influenced and Generated. ## Campaigns and sends [#campaigns-and-sends] The table lists the LettrLabs terms for campaigns and the ways a campaign sends. | Term | Meaning | Old name | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ | | Campaign | A LettrLabs campaign holds every automated and every one-time send in one model. Each run of a campaign becomes orders in production. | Automation, order, Smart Automation | | Send type | The send type of a LettrLabs campaign is One-time campaign or Automated campaign. A one-time campaign mails one list or one area, one time. An automated campaign mails each new home that matches your rules, until you turn it off. | Order or one-off (one-time), automation (automated) | | Source | The source of a LettrLabs campaign is where its people come from. The sources are Area Mail, Radius Mail, Weather, Outages, Property Signals, New Movers, My integration, LeadReveal, A list and Webhook. | None | | Campaign path | A LettrLabs campaign path is four values: the source, the sub-source, the send type and the event basis. The path decides which features a campaign can use. | None | | What builds the audience | "What Builds the Audience?" is the Send Mail question that picks the kind of source: My Data and Integrations, Map-Based Search, or Buying Signals. | None | | Playbook | A LettrLabs playbook is a ready-made campaign. You pick one, change what you need, and turn it on. A partner program can also package a playbook, and a dealer launches it as its own campaign. | Play | | Legacy automation | A legacy automation is an older type of LettrLabs automation. Some campaign paths still make one at launch, and it keeps its own tools and plan gates. | Smart Automation. Its statuses included Testing and Enabled. | ## Design [#design] The table lists the LettrLabs terms for the design of the mail. | Term | Meaning | Old name | | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------- | | Template | A LettrLabs template is a saved card design for one product. You make a template in the design editor. | None | | Touch and cadence | A touch is one mailing of a LettrLabs campaign, with its own design, postage and wait. The cadence is the set of touches of a campaign. | Multi-touch | | Merge field | A LettrLabs merge field is a `{{FIELD}}` token in a design. It prints each recipient's value, or a fallback value when the recipient's value is empty. | None | | Brand field | A LettrLabs brand field prints each sending account's own logo, phone and artwork into one shared design. | None | ## Audiences [#audiences] The table lists the LettrLabs terms for the people and the places that a campaign mails. | Term | Meaning | Old name | | ------------ | -------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | | Service area | A LettrLabs service area is a named set of shapes on the map. A campaign can mail the homes inside it. | None | | Suppression | A LettrLabs suppression list tells LettrLabs not to mail a set of addresses. | Do-Not-Mail | | Integration | A LettrLabs integration is a connection to one of your tools, such as a CRM. It reads from the tool once a day and never writes to it. | Manage Integrations | ## Automation and approvals [#automation-and-approvals] The table lists the LettrLabs terms for how an automated campaign runs and waits for you. | Term | Meaning | Old name | | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | | Run | A run is one firing of a LettrLabs automated campaign. A run pays before LettrLabs writes any order. | None | | Approval | A LettrLabs approval setting decides when a run mails. "Approve each run" holds each batch until you approve it. "Auto-approve" mails the batch when it is ready. | None | | Held run | A LettrLabs held run waits for a person even without an approval setting. It waits when the run finds far more homes than the campaign usually mails. It also waits when its price is above the most that the campaign pays. | None | | Event limit | A LettrLabs event limit is the most recipients that one weather event or one outage can mail. | None | ## Measurement [#measurement] The table lists the LettrLabs terms for the results of your mail. For each figure with its formula, see [Attribution metrics](/measurement/attribution-metrics). | Term | Meaning | Old name | | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | | Holdout | A LettrLabs holdout keeps a share of each batch unmailed. The results then show the lift that the mail caused. | Holdout group | | Attribution | LettrLabs attribution counts the records that your mail earned. Influenced counts every record that the mail reached. Generated counts a record only when it started after the mail arrived, inside the window. | None | | Attribution window | The LettrLabs attribution window is how long after delivery a job or a lead can start and still count for the mail. | None | | iRevenue | The LettrLabs iRevenue is the revenue that the mail caused: the revenue of the mailed homes, less what the holdout predicts. | Incremental revenue | | iROAS | The LettrLabs iROAS is the iRevenue divided by the spend. It needs a holdout. See [Read the incremental figures](/measurement/attribution#read-the-incremental-figures). | Incremental ROAS | ## Account and billing [#account-and-billing] The table lists the LettrLabs terms for your account, your team and how LettrLabs charges you. | Term | Meaning | Old name | | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | -------- | | Balance and charging | LettrLabs uses your balance first on every charge. Only the rest goes to your payment method. | None | | Auto-billing | LettrLabs auto-billing decides what happens when the balance is short at a charge that nobody watches, such as an automated run. | None | | Plan tier | The LettrLabs plans are Starter, Core, Premium and Enterprise. A feature outside your plan opens an upgrade prompt. | None | | Role | A LettrLabs account user has the role Admin or User. | None | | Organization | A LettrLabs organization groups Enterprise accounts under one balance, one set of members and one set of reports. | None | | Partner program | A LettrLabs partner program invites accounts. Each account that joins agrees to share its attribution and transaction reports with the program. | None | ## Old names in the earlier app [#old-names-in-the-earlier-app] The earlier LettrLabs app and some older support articles use other names. "Automations", "Orders" and "Smart Automations" are now all campaigns. You find them on the **Campaigns** page, on the **Automations** and **One-time** tabs. ## Influenced and Generated [#influenced-and-generated] The LettrLabs dashboards let you pick the basis of the figures. Influenced gives the larger number, because it counts every record that the mail reached. Generated gives the stricter number. The [How attribution works](/measurement/attribution) page explains the two. ## FAQ [#faq] The earlier app used those names. Both are now campaigns. Open **Campaigns**, then the **Automations** tab or the **One-time** tab. Influenced counts every record that the mail reached. Generated counts a record only when it started after the mail arrived, inside the attribution window. ## Related [#related]