Partnerships & field mapping

Align terms and field maps so Connect deliveries are commercially and structurally correct.

Partnerships & field mapping

A Connect partnership is the agreement and technical connection between one sender and one recipient endpoint.

Review the partnership

Before activation, both parties should confirm:

• sender and recipient organization
• sending buyer and receiving list or channel
• accepted products and lead types
• prices, limits, and delivery policy
• confirmation and Storno rules
• effective date and responsible contacts

Terms are versioned so that later changes can be distinguished from the agreement used for earlier deliveries.

Map fields

Field mapping translates sender data into the recipient’s person, interest, and list or channel fields.

Map in this order:

1. Person identity: name, email, phone, address
2. Consent and capture information
3. Product
4. Product qualification fields
5. Recipient-specific working fields

Agree on required fields and value formats before creating the mapping.

Preview compatibility

Use the compatibility preview to identify:

• missing required recipient fields
• sender fields without a destination
• incompatible product definitions
• unexpected select values or formats

A compatible preview means the structure can be mapped. It does not guarantee that the lead will pass all recipient or buyer rules.

Test the complete path

1. Use a synthetic person and clearly marked test interest.
2. Deliver through the active partnership.
3. Compare sender values with the recipient row and Records.
4. Verify consent, product, and qualification values.
5. Submit one feedback or Storno outcome.
6. Confirm that it appears on the sender’s transaction.

Change a live mapping safely

1. Capture a current sender sample.
2. Preview the proposed mapping.
3. Identify fields removed or renamed by either party.
4. Test without production personal data.
5. Agree on the effective date.
6. Monitor the first production deliveries after publication.

Mapping changes affect new deliveries. They do not automatically repair values already received.

Common questions

Why is Connect successful but a field is empty?

The source may not send it, the mapping may point to the wrong path, the value may be incompatible, or the recipient field may have changed.

Who owns the meaning of a field?

Both parties must agree on the business meaning, while the recipient owns the destination schema. Do not rely on similar labels alone.

Next: Connect overview · Feedback and Storno