Custom Objects: Your Data, In Your MAP

Custom Objects let you define your own data tables in Paminga — many-to-one relationships with Contacts and Accounts, ready to drive Segments, Workflows, list membership, lead scores, and CRM actions.

This is the kind of feature most MAPs pretend they don't need.

A Contact has a first name and an email address — those go in Custom Fields. But what about the seven tours that contact has registered for? The fourteen orders? The three product subscriptions? Many-to-one data has historically been a "send it to your CRM and segment over there" problem. Not anymore.

What Custom Objects Are

Think of a Custom Object as a custom data table tied to your Contacts or Accounts:

• Define the object once (e.g., "Tour", "Order", "Subscription")
• Add Custom Fields that describe each instance (departure date, duration, value, etc.)
• Each Contact or Account can have many instances of the object related to them
• Use any field on any instance as a Segment condition

The docs walk through a tour-company example end to end. The same model applies to orders, course enrollments, vehicle service records — any "list of stuff" that belongs to a Contact or Account.

Defining a Custom Object

The setup is short:

1. Settings → Custom Object Definitions → Create Custom Object
2. Give it a Singular Label (e.g., "Tour"). Paminga auto-fills the related fields.
3. Add Custom Fields — Date, Date & Time, Number, Text, Website, Pick List, or a Lookup to another Paminga object
4. Define Relationships to Contacts or Accounts — One-to-One, One-to-Many, Many-to-One, or Many-to-Many

Most B2B use cases land on Many-to-One: many Tours to one Contact, many Orders to one Account.

Standard Fields You Get for Free

Paminga adds a handful of metadata fields to every Custom Object automatically — Created By, Created Date, Last Modified By, Last Modified Date, Owner, Object ID, plus an Object Name field whose label adapts to your object ("Tour Name", "Order Name", etc.).

You don't have to model these. They're just there.

Layouts You Control

Once an object is defined, Paminga creates:

• A List Layout — the "My Tours" / "My Orders" page that shows every instance
• A Record Layout — the detail view for any single instance

You pick which fields appear on each, and you can adjust whenever you want.

Loading Data

Two ways:

• Manually — create instances one at a time from the Contacts & Accounts menu
• Via the API — CustomObjectRecord::setOne for individuals, CustomObjectRecord::setMultiple for bulk

Most real-world deployments use the API to keep instances in sync with the system of record.

The Whole Point: Segmentation

Once you've defined a Custom Object and loaded data into it, you can segment on any field on any instance.

In Paminga, anything you can put in a Segment can drive anything else:

• Add to / remove from Marketing or Subscription Lists
• Adjust lead scores
• Send into Workflows or Drip Series
• Trigger CRM actions
• Drive content via Experiences and Conditional Sections

That's the unlock. Custom Objects don't just store your data — they make it fully native to the entire Paminga automation surface.

❌ Don't keep custom data in your CRM and bounce out of Paminga every time you need to segment on it.
✅ Do model it once as a Custom Object and use it everywhere Segments do work.

Get Started

1. Decide what's missing from your Contact and Account models — orders, tours, subscriptions, anything many-to-one
2. Define a Custom Object at Settings → Custom Object Definitions
3. Add Custom Fields and define the Relationship to Contacts or Accounts
4. Load data (manually to start, then via API)
5. Build your first Segment on a Custom Object field — and watch the rest of the platform light up

Read the Custom Objects docs to dig in.