Skip to content
WeZend
A contact is rarely alone. Model the company, account or subscription they belong to.

Objects and relationships

Store companies, accounts, subscriptions or courses with their own attributes, relate many contacts to many objects, and target, personalise and trigger on them.

An object is anything a contact belongs to that has data of its own: a company, an account, a subscription, a course. You pick the type (company) and use the id from your own system, so saving the same object again updates it. A contact can belong to many objects and an object can hold many contacts, with an optional role such as owner or member.

Once it exists, it is usable everywhere:

  • In messages: {{ objects.company.name }} prints the contact's company, and a loop covers all of them.
  • In segments: "belongs to a company", or a condition on a company's attributes. The segment builder lists every object type your account has.
  • In journeys: a change to an object is recorded as an event for the people in it, so a journey can start when a company is updated or a person is linked.

If you already send Segment-style events, a group call creates the company and links the person for you.

Benefits

Why it matters

B2B and account-based sending

Target everyone at companies where an attribute matches — a plan, a renewal state, a number — instead of building the list by hand.

Your ids, your data

Objects are keyed by the id from your own system, so syncing is an upsert. Attributes are simple values; nested data is refused rather than silently dropped.

Erasure follows the person

Erasing a contact removes their links to objects. The company record itself stays, because it is your record of a company, not that person's data.

Capabilities

What you can do

REST API

Create or update with PUT /v1/objects/:type/:externalId, merge or replace attributes, link and unlink contacts with a role, and look up the objects a contact belongs to.

Segments on object attributes

A condition matches when some object of that type the contact belongs to matches, so a person in two companies qualifies if either does.

Journey triggers

Object updates, links and unlinks become events for each person in the object. An update reports which attribute names changed, never their values.

API example

Build it in minutes

Upsert a company and link a contact
curl -X PUT https://api.wezend.com/v1/objects/company/acme-123 \
-H "Authorization: Bearer $WEZEND_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "attributes": { "name": "Acme A/S", "plan": "pro" } }'
 
curl -X POST https://api.wezend.com/v1/objects/company/acme-123/contacts \
-H "Authorization: Bearer $WEZEND_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "email": "ann@acme.example", "role": "owner" }'

Frequently asked questions

How is an object different from a custom field?

A custom field belongs to one contact. An object has data of its own that many contacts share, so you update the company once instead of every person in it.

One platform. Every customer interaction.

Replace your patchwork of messaging APIs, CDP and automation tools with a single engagement platform built for scale.

No credit card required · EU data residency · 99.99% uptime SLA