> ## Documentation Index > Fetch the complete documentation index at: https://docs.hamla.io/llms.txt > Use this file to discover all available pages before exploring further. # Glossary > What Hamla means by each word. Most of these are ordinary words used precisely — the precision is what matters. ## People — contact, capture, consent, journey stage **Contact** — one person Hamla knows about. They arrive from a popup, a form, an import, a connected platform, or an Instagram reply. A contact with no way to reach them is still a contact; they just cannot be messaged. **Capture** — the moment a stranger became a contact. "Captured by" records which door they came through, and you can build an audience on it. **Consent** — your record that this person agreed to hear from you, held separately per channel. Without it, a contact can be seen but not messaged, and campaigns pointed at them return nothing rather than an error. Hamla will never grant it on a guess. **Journey stage** — where someone is with you: aware of you, considering, decided, returning, gone quiet, or actively recommending you. Hamla moves people between stages on its own as they act. ## Groups of people — segment, list, tag **Segment** — an audience defined by a *rule*: "bought twice, nothing in sixty days". Membership is live. People join and leave by themselves as the answer changes, so you build one once and it stays right. **List** — an audience defined by *who is in it*. Someone put each person there by hand, and they stay until someone removes them. Both are audiences you can send to. The difference is the one to remember: **a segment keeps up, a list does not.** Use a list for a fixed set — the twelve people going to an event. Use a segment for everything else. **Tag** — a label on a contact. Unlike a segment, a tag says nothing about why; it is just a mark you or a form put there. Tags are the bridge between form answers and audiences, since you can segment on a tag but not on a raw form answer. ## Things that happen — event, trait, custom field, transaction **Event** — something a customer did, at a moment in time. Some events Hamla sees itself, on your site. Some arrive from a connected platform. The rest you send from your own system. **Trait** — something that is *true about* a person rather than something they did: their plan, their branch, their renewal date. Traits become fields you can filter on. **Custom field** — a piece of information you track that Hamla did not think of. Created once, then filled in by you, by Hamla, or automatically the first time your system sends it as a trait. **Transaction** — money changing hands, whatever that means for you: an order, an invoice, a paid booking, a subscription renewal. Hamla holds the amount and the date; the meaning is yours. ## Campaigns — trigger, step, channel, draft **Campaign** — one automation: something that starts it, and one or more messages that follow. It is not a single send. Most campaigns sit and wait, firing for each person as they qualify. **Trigger** — what starts a campaign. Five kinds: something someone does on your site, a schedule, a server-side event, something from a connected app, or you pressing send. **Step** — one message inside a campaign, with a delay before it. Delays are counted from the moment that person entered the campaign, not from a fixed date. **Channel** — how a message reaches someone: email, push, WhatsApp, an on-site popup or notification, a social post. Each has its own requirements and its own plan. **Draft** — a campaign that exists but is not live. Everything Hamla builds starts here, and only your click moves it out. ## Your setup — connection, Hamla Events, the script, Business Brief **Connection** — a tool of yours that Hamla is plugged into: a store, a booking tool, an ad account, a social account. **Hamla Events** — the general-purpose door for everything with no connection. You send what happens in your system and Hamla treats it exactly as it treats a built-in connection. **The script** — one line on your website that lets Hamla see visitors at all. Without it, nothing on-site works; with it, popups and browsing-based campaigns do. **Business Brief** — the short profile Hamla keeps of your business: what you sell, who for, how you sound, what you are not. It goes into every conversation, which is why a correction made once never has to be made again. ## Things Hamla makes — plan, report, deck, credit **Plan** *(the document)* — a saved strategy you can refer back to in any later conversation, and execute a piece at a time. Not the same as your billing plan. **Report** — a saved analysis, in words you can read and edit. **Deck** — slides, which can be exported as a PDF you can actually send someone. Reports are documents; decks are the thing that becomes a file. **Credit** — what one AI request costs against your monthly allowance. ## Ads — mirror, lookalike **Mirror** — a Hamla audience copied into your ad account and kept in step with it, hourly. People who join start seeing your ads; people who leave stop. **Lookalike** — an audience Meta builds by finding people who resemble one of yours. The only thing here that reaches strangers, which is why the audience you seed it with decides everything. ## Related Short answers to the usual first-week questions. Segments in practice. Every way a campaign can start. Every channel and what it needs.