Parent Properties are used when attribution or website tracking should occur at the dealer group level rather than at an individual dealership.
This guide explains when a Parent Property should be created and how it should be configured within the DMUI.
When to Use a Parent Property
A Parent Property should only be created when multiple rooftops share resources that cannot be attributed to an individual dealership.
Common examples include:
- A single website serving multiple dealership locations.
- A shared call tracking source.
- A dealer group website that routes visitors to individual rooftop websites.
- Other shared marketing assets that should be tracked at the group level.
If each dealership has its own independent website and marketing assets, create individual Properties instead.
⚠️ Safety Warning
Creating unnecessary Parent Properties can complicate reporting and attribution. Only create one when there is a legitimate business need for shared tracking.
Naming Standard
The Parent Property should follow the standard naming convention:
Property Name
Client Name – Parent
Example
| Client | Parent Property |
|---|---|
| exampleautogroup | exampleautogroup – Parent |
This naming convention clearly distinguishes the Parent Property from the individual dealership Properties within the same Client.
Parent Property Configuration
Configure the Parent Property using the following standards.
| Field | Standard |
|---|---|
| Property Name | Client Name – Parent |
| Tag Monitor | Enable only when the Parent Property has its own website or all rooftops share a single website. |
| Domain List | Populate only when the Parent Property has its own website. |
| Address | Populate only when the Parent Property has its own physical location. Leave blank if the Parent Property exists within one of the child rooftops. |
Shared Website Example
Use a Parent Property when multiple dealerships share a single website.
Example:
Example Auto Group
├── Example Ford
├── Example Honda
└── Example ToyotaWebsite:
www.exampleautogroup.com
In this scenario:
- The Parent Property represents the shared website.
- Each dealership remains its own Property.
- Website attribution occurs at the Parent Property level.
Independent Website Example
Do not create a Parent Property solely because dealerships belong to the same dealer group.
Example:
Example Ford
exampleford.com
Example Honda
examplehonda.comSince each dealership has its own website, each dealership should simply have its own Property.
Before You Save
Before saving a Parent Property, verify that:
- A Parent Property is actually required.
- The Property Name follows the Client Name – Parent standard.
- Tag Monitor is configured appropriately.
- Domains have only been entered when applicable.
- Address information has been entered only when appropriate.
