What is a custom network?
A custom network is a network that doesn't have an API integration with Bunker: instead of connecting automatically, its data is uploaded from a file or spreadsheet. This is typically the case for Taboola, Outbrain, internal DSPs, TV, OOH, and generally any source that isn't natively integrated.
Custom networks have their own space within Connections, with a guided step-by-step wizard, ADA-assisted metric mapping, and automatic totaling. Once connected, the network behaves just like any other native channel.
How to connect a custom network
To connect a custom network:
Go to the Connections module within Bunker.
Scroll down to the Custom Networks section.
There you'll find two options: Connect custom network (to create a new one) or edit an existing network. Created custom networks are displayed with their name, creation date, and file source.
Step 1 — Data source
Select where you'll bring the data from:
Google Sheets: data syncs automatically.
CSV or XLSX file: imported directly. The file can be replaced at any time after it's been uploaded.
In this same step, you'll need to configure:
The date granularity of the data: daily, monthly, or yearly.
It's important to include a date column with daily granularity in the file so that Bunker can automatically assign the periods for your network(s).
Whether the file has headers and, if so, which row they're located in.
The row where the content starts.
Whether the file includes a totals row.
Step 2 — Network creation
Define the network's name and an icon color. You can configure a single network or multiple networks:
Single network: all rows in the file will belong to that same network. However, it's possible to configure more than one account within the same network if you set up an account column with different values in the file you're linking to Bunker.
Multiple networks: select a network identifier column (for example, a column called "NETWORK"). Bunker will group the rows according to that column's value, creating a distinct network for each unique value found.
Step 3 — Data structure
Choose whether the data will be displayed at the account level only or across multiple levels. If you opt for the multi-level structure, you can configure the data by account, campaign, ad group, and ads, and add additional levels if needed.
Step 4 — Metric mapping
Through ADA, Bunker automatically suggests which metric each column in the file corresponds to. It's recommended to review the proposed mapping to confirm it's correct before continuing.
Step 5 — Summary
A complete summary of the configuration will be displayed. Once confirmed, the network is connected. For now, the network is available in the Paid Media module (support for other modules is coming soon).
What you can do once the network is connected
Once the custom network is connected, it behaves like any native channel:
KPIs: can be created based on the network's data.
Bunker Campaigns: can be built using the same taxonomy rules applied to native channels, with no additional configuration.
Cross-connection: available without needing to map metrics manually, since that mapping is resolved when the network is created.
Reports and dashboards: the network's data is integrated just like any other channel.
Dynamic charts: can also include data from the custom network.