How they found you, and your own records on them
The UTM tags and referrer kept from a visitor’s first page, and your own records — a subscription, a policy, a vehicle — attached to a contact.
EmailHow they found you. When somebody first arrives on a page with the widget on it, the UTM tags on that page and the site that linked them are kept on the session, and copied onto their contact the first time they write. It is first touch, not last: a fact about the beginning, kept once and never overwritten, because the last click is already in the conversation. A click id from Google or Meta counts even when the tags were forgotten. A direct visit records nothing at all rather than an empty row that makes “unknown” look like “typed the address”. It shows on their record, and segments can be built on the source, the campaign or the referring site.
Your own records. A business keeps things we have never heard of — a subscription, a policy, a vehicle, a membership, a class. Push them with one call (Settings → Developers → dotaskAPI: POST /v1/api/objects) with a type, your own id for it, a label and any flat fields you like. The same id pushed again updates rather than duplicates, and `delete: true` removes it. Deliberately schemaless: a tool that made every business describe its records in our words would be used by none of them.
What they are for. They show on the contact’s record; segments can filter on them (“your own record… subscription.plan is gold”); and an email can use them as merge tags — {{object.subscription.plan}}, {{object.vehicle.label}} — resolved per recipient at send time, and only looked up when the copy actually asks for one.
Flat values only: text, numbers and true/false. A nested object would have no sensible merge tag and no sensible segment rule, so it is dropped rather than half-supported.