Skip to main content
A schema mapping tells Reach how to interpret your schema definitions in terms of its three canonical concepts — contact, transaction, and location. It’s the step that says “the email field on this schema is the contact’s email,” “this schema is a transactions_schema and transactionTotal is the amount,” and so on.
Definition vs. mapping is the distinction partners most often trip on — read this before you map.
  • A definition is the shape of your data (your field names, your structure).
  • A mapping is how Reach reads that shape as its concepts.
Two steps, two parts of the UI. Start here:
Define your schemas first, then map them. A mapping references a schema definition by ID, so the definition must exist before you can map it.