Skip to main content

Reviewing a Blueprint's campaign configuration before launch

Launch Review ensures campaign readiness by identifying and resolving issues before launch.

Reviewing a Blueprint before launching campaigns on a Blueprint is essential for verifying campaign details and preventing errors. Launch Review has been set up specifically for this purpose.


Navigating to Launch Review

  1. Hover over Automate (rocket icon) in the left menu, and select Launch.

  2. Hover over an account that is staged for launch and click the eyeball icon. The new window contains detailed campaign information for a specific account (including any errors and campaigns within that account).


Resolving alerts and info

Alerts and info in Launch Review point to issues you should resolve prior to launch. They are organized into five categories, depending on the severity of the issue:

  1. Info (blue)

    • The Domain is not set for this account

    • Account Vertical XXXXX and Template Vertical YYYYY Do Not Match

    • Account Name (XXXXX) differs from name used for Ads (YYYYY)

  2. Warnings (yellow)

    • Business Hours are not currently set

    • Site Crawler has not been run for this account

    • Partners (e.g., Google/Facebook) are not configured properly

  3. Errors (red)

    • THIS ACCOUNT IS MARKED AS READ ONLY, launches will not publish externally

    • Address 1 is not set

    • City is not set

    • State/Province is not set

    • Postal Code is not set

    • Time Zone is not properly set

  4. Campaign Exclusions: Campaigns that are being excluded from the launch. E.g., If you turned off a feature flag for a campaign, that campaign will be excluded from the launch and will show under Campaign Exclusions.

Other common errors

  • No Ads Generated. Does your account have a very long name? Is the make or model name very long? This generally happens when ad text length is too long. Make sure that within a Blueprint, you have lots of values to choose from. Fall Throughs and ad copy line breaks are items that you can add to a Blueprint to help ensure issues like these don't happen.

  • URLs Are Incorrect. Check that you have the correct domain listed for the account. Fluency will check the account's listed domain for URLs with a successful response when loading. If a successful response is not given, Fluency will revert URLs to the domain page entered into the system. URLs are selected by the settings within a Blueprint. If the URLs are going to an incorrect page for an advertisement, this is often due to settings within your Blueprint that need to be adjusted.


Reviewing campaign structure

Campaign Structure provides the details of the campaign you are about to launch. Click a campaign name to review details pertaining to targeting settings, ad schedules, ad extensions, ad groups, creatives, keywords, and negative keywords.


Downloading preview data

You can download preview data within Launch Review. This option exports information about the campaigns you want to launch as a CSV file so you can see all the information at a glance. Use this to audit large or complex launches in a quicker format.

To download preview data:

  1. On the Blueprint launch page, hover over an account that is staged for launch and click the eyeball icon.

  2. Click the View Options dropdown and select Download Preview Data.


Switching to creative audit view

Switching to creative audit view allows you to hone in on the creative elements associated with a launch. This enables you to ensure all text and images display properly and without issue. It can be helpful for launches where a user is already confident in the structure and the targeting of the advertising, but wants to do a final check on how the creatives look.

To switch to creative audit view:

  1. On the Blueprint launch page, hover over an account that is staged for launch and click the eyeball icon.

  2. Click the View Options dropdown and select Creative Audit View.

  3. To switch back to the default view, click the View Options dropdown and select Default View.

Did this answer your question?