# Register your placements on the Hierarchical Grid

![Placements in Brand Control Center (BCC): each row is a node on the Hierarchical Grid with its style, status, and analytics.](https://cdn.sanity.io/images/lnrtvsvr/development/c5215d9c5873f0153740144edb6334071918b76f-1200x753.jpg)
*Screen. Placements in Brand Control Center (BCC): each row is a node on the Hierarchical Grid with its style, status, and analytics.*

When you finish, every place your video will appear has an address on one map that inventory, feed layout, and reporting all share, so a placement you create today reports correctly forever. Your part takes about 10 minutes for a typical site; retailers with many templates can import a sheet.

## Before you begin

- Properties verified in [Connect your website, app, and podcast feed](https://begenuin.com/developers/get-started/any-business/connect-properties).
- A rough list of page types where video should appear (homepage, category, article, product, checkout confirmation, app home, and so on).

## How the grid works

The Hierarchical Grid has four levels: **Network → Property → Page type → Placement**. A placement is a named slot with a size, an allowed set of player experiences, and a context (the topics, categories, or products that page type is about). Everything else in Genuin, from [Maya](https://begenuin.com/developers/get-started/any-business/supervised-intelligence-what-it-does-and-where-to-start#maya-genuin-s-orchestrator)'s ranking to the revenue report, reads from this grid rather than keeping its own list.

![Diagram: the Hierarchical Grid builds node by node as Octo reads the crawl. It has four levels: Network, Property, Page type, Placement. Your network contains properties such as your website and your app. Your website has page types named the way your site names them, such as PDP, with two placements, and Category, with one; your app has an App home page type with one placement. A placement has a size from the IAB list, the player experiences it allows, and a context: the topics, categories, or products its page type is about. Everything else reads from this one grid: Maya’s ranking, inventory, feed layout, the embed snippets, and the revenue report.](https://cdn.sanity.io/images/lnrtvsvr/development/8f21f2a0df77a78892f51da06f4a56e34dc436b7-720x638.svg)
*Every placement sits on one four-level map, and everything in Genuin reads from that map.*

## What Octo does

![Diagram: who does what, in five steps across two lanes. Octo: 1, builds the grid from the crawl, with page types named the way your site names them and placements for each, each with a size, its allowed experiences, and a context. 2, for large sites and aggregators, imports the grid from your ad server’s ad units or your inventory map instead and reconciles the two. 3, shows the grid as a tree, with the placements it recommends launching first marked. You: 4, rename, merge, or remove page types and placements, add a placement Octo missed, or change a context. 5, choose Approve and publish grid; every placement gets its placementId. Result: every placement has an address on one map, with placement IDs for your embed snippet. Your part takes about 10 minutes.](https://cdn.sanity.io/images/lnrtvsvr/development/0d6521aaa9b9133904bdb48555388a474e426dd7-720x731.svg)
*Octo drafts the grid from your site; you tidy the tree and publish it.*

1. Octo, Genuin's Supervised Intelligence interface, builds the grid from the crawl: for each verified property it proposes page types named the way your site already names them (PDP, Category, Episode page, Support) and one or more placements per page type, each with a size from the IAB list (see [Player card sizes and IAB footprint spec](https://begenuin.com/developers/get-started/any-business/player-card-sizes-and-iab-footprint-spec)), the allowed experiences, and the context (category tree, product taxonomy, or topics) it read off the pages.
2. For large sites and aggregators Octo imports the grid from your ad server's ad units or your inventory map instead of the crawl, one row per placement, and reconciles the two.
3. Octo shows the grid as a tree with the placements it recommends launching first marked.
   ![Untitled placements are added for every page type found on your site; you rename, approve, and publish.](https://cdn.sanity.io/images/lnrtvsvr/development/7776478c785f82a2883049215c5b104bc9e44bcc-1194x747.jpg)
   *Screen. Untitled placements are added for every page type found on your site; you rename, approve, and publish.*

## What you approve

- The tree. Rename, merge, or remove page types and placements; add a placement Octo missed; change a context.
- Choose **Approve and publish grid**. Every placement gets its `placementId`, which Octo uses in the embed snippets and reports from here on.

## Make Octo smarter

- Connect your ad server or CMS (Network → Grid → Sources); Octo keeps the grid in sync as templates change, and proposes new placements when it sees a new page type in the crawl.

**Need help?** Octo is available 24/7 in Brand Control Center (BCC) and on every page of these docs. Ask it in plain language; when the answer needs a person, Octo brings the right account manager, developer, or Ops engineer into the same thread and stays on it until it is solved. Every Business Account owner has this, on every plan (see [24/7 Octo support: how Octo brings in account managers, developers, and Ops](https://begenuin.com/developers/get-started/any-business/24-7-octo-support-how-octo-brings-in-account-managers-developers-and-ops)).

## What you get

- Placement IDs you will paste into the embed snippet in [Launch your first community: your owned-and-operated space](https://begenuin.com/developers/get-started/any-business/launch-first-community).
- A context map that Maya uses to decide which video belongs on which page.
- The exact rows your revenue and margin reports (see [Margin reporting: revenue per impression and net margin on ad spend](https://begenuin.com/developers/get-started/any-business/margin-reporting-revenue-per-impression-and-net-margin-on-ad-spend)) will be broken down by.