Mapped
By default, Fusion creates all the GAM units it needs (one unit per publisher config). This is important as it ensures reporting connects up, especially for experiments where one config competes against another, requiring two GAM units. In Fusion “Pro” we use the GAM API to create units when you set up a config. This ensure that everything needed for ad serving and reporting is perfectly in place. In “Mapped”, you must manually map each config to a unit that is already set up in GAM. This adds an extra manual step, which must be done correctly, as we do not verify the unit setup in your GAM when using this approach.Hybrid
The choice between “Pro” and “Mapped” doesn’t have to be all or nothing. There is a hybrid option where any units you map will be “mapped”, while any you leave unmapped will default to auto-created units. The major benefit here is that all your key units can remain in place, but if you want to quickly spin up an experiment, then you can do so while leaving Fusion to create the necessary units. Hybrid is actually the default option. You can map any unit in Fusion, and once mapped, it will prevent the system from auto-creating that unit. However, if left blank, it will default to its normal behaviour.Feature Table
| Fusion “Pro” | Fusion “Mapped” | |
|---|---|---|
| Header Bidding Wrapper | ✅ | ✅ |
| Dynamic Floor Technology | ✅ | ✅ |
| Unified Reporting | ✅ | ✅ |
| Contextual | ✅ | ✅ |
| Dynamic Placements | ✅ | ⚠️ via hybrid |
| Experiments | ✅ | ⚠️ via hybrid |
| Ad Refresh | ✅ | ✅ |
| Ad Products | ✅ | ✅ |
| Insights hub | ✅ | ✅ |
| Ad Tech (ad block, CMPs) and Fallback integrations | ✅ | ✅ |
| Site health + Alerts (inc Ads.txt checks) | ✅ | ✅ |
| Managed ID Solutions | ✅ | ✅ |
| In-view tech | ✅ | ✅ |
| Mobile App | ✅ | ✅ |
| Audience Builder | ✅ | ✅ |
| One-to-many unit config relationship | ✅ | ❌ |
| Keep your GAM unit structure | ❌ | ✅ |
| Keep your existing Google Publisher Tag setup | ❌ | ❌ |