Custom Fields let you capture additional information on a campaign that isn't part of Realhub's standard property details — and, if needed, automatically pull that value in from your CRM feed or push it out to your connected portals.
Who can set these up: Brand Administrators can create and manage Custom Fields for their own brand directly — no need to raise a support request.
What is a Custom Field?
A Custom Field is an extra data point attached to a campaign. It can be:
A simple text entry (with sub-types for email, URL, number, date, or plain text)
A dropdown/select list with a fixed set of options
A longer text area
It can also be marked as required, given a default value, and set to a specific display width on the page.
When should I use one?
Reach for a Custom Field when:
Your office or franchise needs to track something Realhub doesn't have a standard field for (an internal reference number, a compliance flag, a franchise-specific ID).
The value already exists somewhere in the XML your CRM sends to Realhub when a campaign is created or updated — any tag or attribute in that feed can be pulled into Realhub automatically via a Custom Field. This isn't limited to IDs — it can be an email address, a website/URL, a number, a date, or any other value your CRM includes.
The value needs to be sent back out in the data feed Realhub sends to your connected portals.
If a standard Realhub field already covers what you need, use that instead.
Where do Custom Fields display?
Once created, a Custom Field appears on every campaign for your brand, under:
Campaign → Property Details → Details tab → Custom Fields section
It behaves like any other field on that page — fill it in (if it isn't already populated automatically from your CRM feed) and hit Save Details.
Setting up a Custom Field — step by step
Go to Brand → Edit → Custom Fields.
Under Campaign Fields, click + Add Field.
Fill in the form:
Field | What it does |
Field Label | The name shown to users on the campaign, e.g. "Box+Dice Listing ID". |
Field Key | An internal machine-readable identifier — auto-generated from the label, but editable. Must be unique per brand. |
Hint | Optional helper text shown alongside the field. |
Placeholder | Optional greyed-out example text shown in an empty field. |
Required | If Yes, a campaign can't be saved until this field has a value. |
Field Type |
|
Input Type (Input fields only) | Constrains the input: Date, Email, Number, Text, or Url. |
Option Values (Select fields only) | Add each dropdown option as a Label + Key pair (Key is auto-generated from the Label, editable). |
Default Value | Pre-fills the field on new campaigns if nothing else sets a value. |
Field Width | 100%, 75%, 50%, or 25% — controls how wide the field renders on the page. |
REAXML Import → Import Path Type | Currently only |
REAXML Import → Import Path | The location of the value inside the XML your CRM sends. For a simple tag, this is just the tag name (see worked example below). |
REAXML Export → Export Path | Where this value should appear in the XML feed sent out to your portals. |
Click Create Field.
Worked example: pulling a value in from your CRM, and sending it out to a portal
Say your CRM's XML feed includes a tag like this for every listing:
<residential> <uniqueID>1234567890</uniqueID> <webReference>999000999</webReference> ... </residential>
You want the webReference value captured on the campaign, and included in your portal export feed as its own field.
Import Path: webReference
— This tells Realhub "look for a tag called webReference directly inside each listing, and store whatever text is inside it." Realhub will read this automatically every time a campaign is created or updated from that feed — no manual entry needed.
Export Path: extraFields[@name='bdlisting_id']={{value}}
— This tells Realhub "when building the outgoing feed, create a tag called extraFields with a name attribute of bdlisting_id, and put this field's stored value inside it." {{value}} is a placeholder that gets replaced with whatever was captured (or manually entered) on the campaign. The result in your outgoing feed looks like:
<extraFields name="bdlisting_id">999000999</extraFields>
Result:
On the campaign, this value shows up under Custom Fields on the Details tab, populated automatically from the CRM feed.
In your outgoing portal feed, it's included as its own
extraFieldsentry, without affecting any of your existing fields.
A few things worth knowing
Not every Custom Field needs both an Import Path and an Export Path. Set only the one(s) you need — a field can be import-only, export-only, both, or neither (e.g. a purely manual, internal-use field).
If a value looks wrong or missing on a campaign, check the Details tab first — if it's blank there, it won't be in the export either.
Adding a new Custom Field never changes or affects fields you already have set up — it only adds new information alongside them.