Multi-brand configuration
Setup Northbeam for multiple brands.
Northbeam can be implemented to track different brands separately, if your setup meets the following requirements.
Requirements
| Ad Data | Domains | Orders |
|---|---|---|
| Brand-specific ad accounts, or campaigns, or adsets | Brand-specific top-level domains, or subdomains, or page paths | Brand-specific stores, or currencies, or shipping country, or other order metadata |
- Brand-specific ad data. At either the account, campaign, or adset level, ad data must be brand-specific / follow some naming convention. If single ad accounts are used to serve ads across multiple brands, campaigns/adsets must follow a naming convention.
- Unique accounts (e.g. Brand A Meta Ads Account, Brand B Meta Ads Account, Brand C Meta Ads Account)
- Campaign Naming Convention (e.g. Names begins with
Brand-A_,Brand-B_,Brand-C_) - Adset Naming Convention (e.g. Names begins with
Brand-A_,Brand-B_,Brand-C_)
- Brand-specific domains. Each brand has must have a unique subdomain or top-level domain, including the entire checkout experience.
- Unique domains (e.g.
brand-a.com,brand-b.com,brand-c.com) - Unique subdomains (e.g.
brand-a.mystore.com,brand-b.mystore.com,brand-c.mystore.com) - Unique page paths (e.g.
mystore.com/brand-a,mystore.com/brand-b,mystore.com/brand-c)
- Unique domains (e.g.
- Brand metadata for orders. Orders need to be able to be grouped by brand so that they can be matched with corresponding ad and visits datasets.
- Brand-specific dashboards. In order to accommodate this configuration, Northbeam dashboards will be made for each brand, as opposed to a single dashboard with brand breakdowns.
FAQ
Can we consolidate all brands into a single dashboard?
- If you only have 1 domain, you could analyze traffic across all brands in a single dashboard.
- If you have multiple domains, you cannot send all data to a single dashboard.
- Why?
- Northbeam dashboards map 1:1 to domains to enable 1st party tracking. Each dashboard has a unique domain, connected to the A Record within the DNS settings.
- If multiple domains pointed to 1 Northbeam dashboard, only 1 brands would have 1st party tracking, and the others would use 3rd party tracking.
- Why?
- You can combine multiple dashboards into a single rollup dashboard.
Examples
Scenario 1
| Brand | Ads | Domain | Orders |
|---|---|---|---|
| A | Brand A Meta Ads Account | brand-a.mystore.com | brand-a.myshopify.com |
| B | Brand B Meta Ads Account | brand-b.mystore.com | brand-b.myshopify.com |
| C | Brand C Meta Ads Account | brand-c.mystore.com | brand-c.myshopify.com |
Multi-dashboard configuration is supported!
This setup has unique ad accounts, domains, and orders which allows dashboards to be created for each brand.
Scenario 2
| Brand | Ads | Domain | Orders |
|---|---|---|---|
| A | Campaign names begin with Brand-A_ | mystore.com/brand-a | brand-a.myshopify.com |
| B | Campaign names begin with Brand-B_ | mystore.com/brand-b | brand-b.myshopify.com |
| C | Campaign names begin with Brand-C_ | mystore.com/brand-c | brand-c.myshopify.com |
Multi-dashboard configuration is supported!
This setup has brand-specific campaign names, page paths, and Shopify stores, which allows dashboards to be created for each brand.
Scenario 3
| Brand | Ads | Domain | Orders |
|---|---|---|---|
| A | 1 ad account, no naming convention | mystore.com/brand-a | brand-a.myshopify.com |
| B | 1 ad account, no naming convention | mystore.com/brand-b | brand-b.myshopify.com |
| C | 1 ad account, no naming convention | mystore.com/brand-c | brand-c.myshopify.com |
Multi-dashboard configuration is not supported.
This setup has no way to split out ad data by brand, so it is impossible to attribute spend and impressions to specific brands.
One blended dashboard is supported.
All the visits occur on the same top-level domain, so visit data can be collected from all brands via 1st party tracking.
Updated 7 months ago