Your shop and your campaigns see interest before your team does: an order placed, a cart abandoned, a form filled in. Those events arrive in CRM as signals — one inbox, under CRM Management → Signals.
Every signal carries its provenance: the source it came from (your store, a marketplace, a campaign platform), the reference it holds in that system, when it happened and when it arrived. Open one and you can always answer "why is this here?" — and, where the signal started a lead, "why does this lead exist?" The lead, and any opportunity it later qualifies into, keeps that link.
A signal may also carry a campaign name from the channel that sent it. That name is the channel's own label, kept as provenance — it is never matched against your campaign register, even when the words are identical. A lead a signal starts therefore begins with no campaign attached; if the work belongs to one of your campaigns, a person picks it on the lead or the opportunity, and that recorded pick is what the figures follow.
A signal is matched to a party openly, never silently: an exact external reference first, then the email address, then the phone number — and the match it made is written on the signal itself. No match, and a new party is created from what the signal carried. The same event delivered twice is recognised and filed once.
Signals that arrive by hand — a paper order book, a spreadsheet from a partner — are typed in with Record signal on the inbox. They go through exactly the same rules as signals that arrive on their own.
On a party's record, the Channel history section gathers everything that party has done across the channels: orders placed, carts abandoned, forms sent, and the campaigns associated with them. Associated is the honest word: a campaign running alongside a sale is company it kept, not proof of what caused it — and that is the word the system uses everywhere.