Contacts
Properties, events, and tags
Proposed vs confirmed schema, tags, and mailing lists.
Audryo does not treat every JSON key you ever sent as a first-class field. Data lists what was detected, how common it is, and whether you have reviewed it.
Fields (contact properties)
Each property has:
- A stable key (what merge tags and audience rules use)
- A display name
- Coverage (% of contacts that actually have it)
- Sample values
- Status: proposed or confirmed
You do not have to confirm a field for ingestion or merge to work. Confirming means “we trust this for segmentation and AI suggestions.” Delete unused proposed noise so the audience builder stays small (max 25 top-level conditions per audience group).
History on a definition shows who changed type or name.
Events
Events are named occurrences (book_created, login) with optional properties and occurredAt. Definitions work like fields: proposed when first seen, confirm when the name is the one you want journeys to use.
Send events with contactExternalId and a unique externalId per occurrence so retries do not double-count conversions.
Tags
Tags are labels Journeys apply (set_tag), not ingested properties. Use them for “completed the advanced series,” then segment with Tag rules in Audiences. Rename or remove tags under Data → Tags — removing a tag does not delete the contacts.
Mailing lists
Mailing lists are subscription groups (public/private) for preference centers, distinct from audiences (live rule segments). A list is who asked for a topic; an audience is who currently matches a query. See Consent & suppressions.