Step 1 — Trigger and filter conditions
"When does this rule fire?"
The trigger does two jobs: it decides which deals the rule looks at, and it decides which period their commission is attributed to.
Pick the period event
Two choices:
| Option | What it means |
|---|---|
| Deal won | "Use a deal won time from Pipedrive as the trigger." The ordinary case |
| Custom event | "Use a custom date field from Pipedrive as the trigger." Pick the date field from the dropdown |
The builder warns you directly: "Changing this affects which period commissions are attributed to." A deal won in March but invoiced in April lands in a different period depending on which event you pick here. Change it on a live plan and last month's numbers can move.
If your date field isn't in the list: "Mark a date field as a period event on the Fields page to use it here." Go to Organization → Data Sources → Fields first.
A field that was removed shows as <field> (missing) — reselect a live one.
Add filter conditions
Underneath the event: "If no filter conditions are added, the trigger fires on all deals matching the event."
That default is the single most common cause of rules paying twice. If this rule should only cover new business, or one product, or deals over a size, say so here.
- Click + Add condition (AND).
- Pick the field.
- Pick the value.
AND narrows: every condition must be true. + Add condition (OR) widens a group — it stays disabled until you have a condition to widen.
Which fields you can pick. The field list is your organisation's own field catalogue — the same fields you see on the Fields page. It does not depend on your Pipedrive connection being live, so you can still edit filters while a connection is reconnecting.
Values: dropdown or free text. If the field you picked has a fixed set of choices (Status, for example, offers Open, Lost, Won, Deleted), the value control becomes a dropdown of exactly those choices. Any other field gives you a free-text box. If you expected a dropdown and got a text box, the field's choices have not synced from Pipedrive yet — resync on the Fields page, then reopen the rule.
Watch for: if the field list is empty and reads "No fields available yet. Sync or add fields on the Fields page first.", set your fields up first — the filter cannot be built until there are fields to filter on. If it errors with "Couldn't load your fields. Refresh the page and try again.", that is exactly what to do.
How this shows up later
The Period Event column in Deal Review shows which event attributed each deal — Won time, Close time, Local close date, Add time, and so on. When a deal is in the wrong month, that column tells you it was this step, not the deal. → Check and exclude deals
Common mistakes
- No filter on a rule meant to be narrow. It fires on everything and stacks with your base rule. Lokom will flag the overlap — read it.
- Changing the event on a live plan without realising history can re-attribute.
- Using a date field nobody fills in. Deals with no value in that field never trigger.