On this page

Jump to any section using the links below

Hubhus allows you to connect campaigns using parent/child relationships, define how leads should be linked across campaigns, and automatically copy shared field values.
This is essential when one customer journey spans multiple campaigns — for example:

• Lead → Newsletter campaign

• Lead → Quotation campaign

• Lead → Service case

• Lead → Invoice campaign

This guide explains how to configure related campaigns, set equivalent fields, and control how new leads inherit data.

1. Understanding parent and child campaigns

A parent campaign is the primary campaign where a customer first exists.
A child campaign contains downstream or secondary records related to the same person or customer.

Examples:

• Parent: Leads → Child: Newsletter

• Parent: Leads → Child: Quotations

• Parent: Quotations → Child: Orders

• Parent: Orders → Child: Installations

This structure allows you to track the same customer across multiple business steps.

How to configure it

Go to:

Campaign → Settings → Related campaigns

Here you choose:

• Parent campaign

• Child campaign

• Whether the relation should appear on the lead profile

2. Automatically finding related leads using equivalent fields

To automatically link leads across campaigns, Hubhus can compare values between fields in each campaign.

This is configured under:

Equivalent fields when looking for relations

You define:

• Which fields in the parent campaign correspond to fields in the child campaign
  (e.g. Email = Email, Phone = Telefon)

• Match criteria:

  • At least one field must match

  • All fields must match

Example from your screenshot

Leads.Phone no.  =  Newsletter.Phone

If the phone number matches, the system can automatically relate the two leads.

3. Auto-relating new leads/customers

You can enable:

Auto relate new leads/customers: Yes

When enabled:

• Every new lead created in the child campaign

• Automatically searches for a matching parent lead

• Using the equivalent fields defined above

This is useful when:

• Newsletter subscribers should link to existing customers

• Quotation requests should link to existing leads

• Order records should link back to the original inquiry

Hubhus will auto-relate them without manual work.

4. Auto-creation of parent leads (optional)

If a matching parent lead does not exist, you can tell Hubhus to create one automatically.

From your screenshot:

Automatically create parent lead in [Campaign] if none is found

Options:

• Yes

• No

How it works

1. A child lead is created

2. System searches for a matching parent

3. If none exists:
   → Hubhus creates a new parent lead and links it

This is useful for:

• Newsletter → Leads

• Orders → Leads

• Bookings → Leads

It ensures every downstream lead has a main parent record.

5. Automatically copying missing fields to the child lead

When a relation is created, you can copy values from the parent lead into the child lead.

Settings:

Inherit field values from parent: Yes / No

When enabled:

• Equivalent fields are copied

• Only empty fields in the child are filled

• Child values that already exist are not overwritten

Example from your screenshot:

Leads.Kontaktperson  →  Nyhedsbrev.Navn  
Leads.E-mail         →  Nyhedsbrev.Email  
Leads.Telefon nr.    →  Nyhedsbrev.Telefon  

This ensures consistent customer information without manual entry.

6. Auto-inserting equivalent field values when manually creating leads

When manually creating a new related lead from a parent record, you can enable:

Auto insert equivalent field values in form: Yes

This fills in the child form automatically with values from the parent.

Example:
If you create a quotation from a lead, the quotation form can auto-fill:

• Name

• Email

• Phone

• Address

• Customer identifiers

This speeds up workflow and reduces errors.

7. What happens during manual relation creation?

When you create a lead in a child campaign via a relation, Hubhus:

1. Prefills fields (if enabled)

2. Copies matching equivalent fields (if enabled)

3. Links the created child lead to the parent lead

4. Shows the relation on both profiles if configured

This gives a smooth “create next step” workflow.

Best practices

• Use phone or email as equivalent fields (highest reliability)

• Always map the same field types (e.g. email → email, phone → phone)

• Enable auto-relation if campaigns should stay in sync

• Use parent auto-creation when downstream leads must always have a root customer

• Enable value inheritance only when parent data is authoritative

• Show relations on profile pages for workflow visibility

Important: Choosing the right equivalent fields (Email/Phone vs Unique ID)

Email and phone numbers are convenient equivalent fields because most leads contain them — but they can create many-to-one or many-to-many relations unintentionally.

Why this happens

• A customer may use multiple emails

• Several people at the same company may share the same main phone number

• Newsletter signups often reuse the same email across different campaigns

• Historic data may include outdated emails or secondary numbers

This means multiple unrelated leads may suddenly appear “related”, even though they represent different business processes.

When this becomes a problem

If your workflow depends on a strict step-by-step chain, such as:

Lead → Quotation → Order → Invoice

…then using email/phone for auto-relation can make it impossible to track the exact conversion path, because:

• more than one quotation might link to the same lead

• unrelated orders may attach themselves to the same root

• child leads may connect to the wrong parent

• invoice tracking becomes inaccurate

Recommended: Use a unique ID for strict business flows

For controlled multi-step campaigns, always use a unique identifier as the equivalent field — for example:

• ERP order ID

• Invoice number

• Customer ID

• Offer ID

• Product request ID

If no ERP integration is used

You can use:

hubhus_id
(or another custom unique field)

…and pass it along as you create the next lead in the chain:

• Assign hubhus_id to the quotation

• Carry the same ID to the order

• Carry the same ID to the invoice

• Use this field as the equivalent field for relations

This ensures a perfect one-to-one relationship through the entire chain.

Best practice summary

Learning outcome

After reading this, you can:

• Configure related campaigns

• Define equivalent fields

• Enable auto-relating of new leads

• Auto-create parent leads when needed

• Copy field values from parent to child

• Streamline manual relation-based creation

? Common searches

custom fields • field setup • data fields • field configuration

? Also known as

project • workspace • pipeline • data field

Related articles

Configuring search settings
How do I filter leads by specific criteria?
How do I give API access to a specific campaign?
How do I set up a new campaign?
How do I share a direct link for customer self-registration?