Fluency lets you recreate an existing non-Blueprint campaign in a Blueprint. The Blueprint “inherits” the non Blueprint campaign’s configurations. Launching the campaign in the Blueprint pauses the existing non-Blueprint campaign.
🛑 Caution: This is an advanced feature. Reversing changes may not be possible. Always check with a Fluency team member to verify that configured settings are appropriate for your use case and needs.
How it works
The Inherit From feature ensures a smooth transition to new Blueprint campaigns by inheriting key configurations. It prevents redundancy, maintains consistency, and pauses the original campaigns after transferring their settings, avoiding duplicates.
Note: Existing campaigns are paused only after the defined configurations are successfully carried forward.
Configuring interactions
Go to Automate (rocket icon) in the left menu.
Select Blueprint Editor.
Click on a Blueprint, and then a campaign.
Toggle on Show Advanced Fields (near the top, under the Blueprint’s metrics row).
Open the Interactions with Existing Campaigns section.
Configure the relevant fields (detailed below).
Review the matches in the Inherit from Campaigns tab in Launch Review to verify for accuracy before launch.
Configuration details
Existing Campaign Matching Strategy
Uses the Blueprint and template's "formula" to identify existing campaigns. This ensures that only one campaign is generated from the formula.
Use the literal Blueprint campaign name to define the match when finding non-Blueprint managed campaigns.
Use the Blueprint and template’s formula of tags within a Blueprint campaign name to find and match the correct non-Blueprint managed campaigns.
Note: Carefully review these settings to prevent errors in campaign matching.
Non-Blueprint Name Collision Handling
Defines how to resolve conflicts when existing non-Blueprint campaigns have names that don’t match Blueprint campaigns.
Renames the existing non-Blueprint campaigns with a suffix [NBP {date}] and changes no other settings. The new Blueprint campaign inherits from a non-Blueprint managed campaign based on the "Inherit From" settings.
Ensures the non-Blueprint campaign is paused after renaming. The non-Blueprint-managed campaigns become Blueprint-managed.
Note: Google ads within the Blueprint will launch as new ads alongside any existing ads in the ad groups that were taken over. Meta ads replace existing ones at launch.
"Inherit From" Name Patterns
Define patterns (e.g., "New Ford*") to match campaigns that should be inherited. Use wildcards for flexible matching.
"Inherit From" Status
Specify how the inherited campaigns update their status. Inherited campaigns are paused after their settings are transferred.
"Inherit From" Existing Spend
Determine how the platform handles spend from the existing non-Blueprint campaigns for a smooth transition. It ensures that the appropriate budget is carried forward into the new Blueprint campaigns.
"Inherit From" Geo Strategy
Use the geo-targeting from matched campaigns or override it with the geo strategy in the new campaign. Lock these settings as needed.
"Inherit From" Extension Strategy
Combine or replace extensions (e.g., callouts, structured snippets) from matched non-Blueprint campaigns with extensions defined in the Blueprint.