Visual Builder

The Visual Builder is the Mapping tab of an integration. It lists the rows of the integration’s blueprint, section by section: Global Parameters (the payload root), Global Event Parameters (every event) and one section per event. Each row takes a value from the event (the source), optionally transforms it, and writes it to a field the vendor expects (the target).

Rules

A row can run only for some events: for example, send hashed email addresses only when the visitor has given marketing consent. That condition is a rule.

A rule is a named condition, such as Marketing consent for context.consent.canonical.marketing = true. Rules are listed on the Rules page of the builder’s sidebar.

• Generate rules creates a rule for every condition your rows already carry, named from the condition. Rename them to suit your team.
• New rule adds one by hand. Insert a field offers the fields your events carry, so you pick paths instead of typing them.
• On a row, the if chip shows the rule’s name. Click it to pick another rule, write a custom condition, or make the row run for every event.
• Editing a rule’s condition changes it on every row that uses it.
• Deleting a rule keeps its rows’ conditions, shown as custom. A custom condition can be saved as a rule from its row.

Groups

Large sections are easier to read in groups such as Page, Consent or Items.

• Group rows sorts a section’s rows by where they read from.
• Add group makes an empty group. To put a row in a group, hover over the row and click the folder icon at its right.
• Click a group’s name to rename it; Remove group leaves its rows in place.

Groups only change how rows are listed, never the order they run in. They are saved as you change them, for everyone who opens the integration, and are not part of the blueprint: grouping rows never creates a new version.

Search and filters

Every section has a search box (source, target, value, transform or rule name) and two quick filters: Has a rule and Required.

Field pickers

The Source picker lists the fields your pipelines’ events actually carry, seen on this event first, then the fields you expect (see Schema Explorer), then the standard Datafly.js fields. Each shows its type and the events it arrives on. You can still type any path.

A small hollow dot beside a source means no event has carried that field in the last 30 days and it is not an expected field. That is fine for an optional field; if you expected it, check the name.

Reading a row

Controls with nothing set (default value, expression, pipeline parameter, required, rule) appear when you hover over a row or move to it with the keyboard. Anything that is set always shows. Hover over any control for a description.