vmartinez

During the campaign setup process, Campaign Manager 360 automatically generates a default ad. What’s the critical operational purpose of this specific ad type?

• It functions as a vehicle for high-priority audience segments and re-engagement lists.
• It acts as a technical safety net, making sure a creative is always available to serve when no specific delivery constraints are met.
• It serves as a non-rendering ghost ad used strictly for tracking impressions on external sites.
• It establishes the global CSS and HTML5 templates that all other campaign creatives must inherit.

Explanation

A default ad is assigned so a placement can serve an eligible creative when no other assigned ad can serve. It protects delivery when targeting, status, scheduling, or other ad-serving conditions prevent regular ads from being selected. In Campaign Manager 360, this prevents blank or unintended delivery behavior for live tags. The operational role is fallback delivery, not tracking, templating, or audience prioritization.

Why the other options are incorrect

Non-rendering ghost ad describes tracking-only behavior, which belongs to a tracking ad, not a default delivery fallback.

Global CSS and HTML5 templates are creative-development assets, not an ad-serving role in Campaign Manager 360.

High-priority audience segments relate to targeting strategy, not the purpose of a default ad.

Source for verification

https://support.google.com/campaignmanager/answer/2826145?hl=en

https://support.google.com/campaignmanager/answer/2828553?hl=en

A publisher notifies a brand that their video player environment is strictly non-VPAID compliant and will reject any tags containing JavaScript wrappers. To make sure the VAST XML remains clean and successfully delivers the video, what action must the brand take regarding Active View?

• Switch the placement compatibility to Display to allow the VPAID asset to serve as a standard out-stream banner.
• Increase the ad priority to 1 to make sure the VPAID wrapper is prioritized by the publisher’s player.
• Toggle the VPAID-only creative setting within the advertiser’s global properties to force a VAST fallback.
• Turn off the setting at the site or placement level to remove the VPAID-dependent measurement wrapper.

Explanation

Active View for in-stream video can add a VPAID measurement adapter to the VAST tag. A non-VPAID publisher player may reject the tag when that JavaScript wrapper is included. Setting the adapter to off at the site or placement level removes the VPAID wrapper from the exported tag. This preserves standard VAST video delivery while avoiding an unsupported measurement layer.

Why the other options are incorrect

Display compatibility changes the placement type and does not solve in-stream VPAID wrapper rejection.

VPAID-only creative setting does not force a clean VAST fallback for a non-VPAID player.

Ad priority affects serving order and cannot remove a VPAID measurement wrapper.

Source for verification

https://support.google.com/campaignmanager/answer/7173678?hl=en

https://support.google.com/campaignmanager/answer/3311603?hl=en

A retailer needs to track the total revenue and the number of items sold for every purchase event. Which Floodlight activity type and counting method should they implement?

• Sales activity using the unique counting method
•  Sales activity using the items sold counting method
• Counter activity using the per session counting method
• Counter activity using the standard counting method

Explanation

A  sales activity is used for revenue-generating conversion events such as purchases. The items sold counting method records the number of items included in each transaction. This setup also supports reporting purchase revenue through the sales tag values. It is the correct Floodlight configuration when both revenue and item quantity need to be measured.

Why the other options are incorrect

Counter activity measures non-revenue actions and does not capture purchase revenue.

Sales activity using the unique counting method is not the correct method for counting item quantity sold.

Counter activity using the standard counting method counts non-revenue conversions and does not measure sales value.

Source for verification

https://support.google.com/campaignmanager/answer/2823400?hl=en

An advertiser wants to measure how many people bought a product after seeing a Facebook ad, even if they never clicked the ad. What must be in place to capture this data?

• A standard click tracker URL used as the main destination link.
• A Search Ads 360 engine account linked to the social media platform’s ads manager.
• An impression tracking pixel (1×1) implemented in the social platform’s tracking field.
• A tracking creative assigned to a standard ad instead of a tracking ad.

Explanation

View-through measurement requires Campaign Manager 360 to record an impression before a later Floodlight conversion occurs. For paid social inventory that is not directly served by Campaign Manager 360, an impression-tracking setup records the ad exposure without requiring a click. That exposure can then be matched to a purchase within the configured conversion window. A click-only setup would exclude users who viewed the ad but never clicked.

Why the other options are incorrect

Search Ads 360 is for search management and does not record paid social impressions for Campaign Manager 360 attribution.

Tracking creative must be used with the correct tracking structure and does not replace impression tracking in the social platform.

Click tracker URL records clicks only and cannot capture view-through activity.

Source for verification

https://support.google.com/campaignmanager/answer/2826133?hl=en

https://support.google.com/campaignmanager/answer/3040965?hl=en

An advertiser is experiencing conversion discrepancies due to modern browser limitations on third-party cookies. Why does transitioning to the Google tag (gtag.js) improve their measurement accuracy compared to legacy IFRAME or pixel tags?

• It sets first-party cookies on the advertiser’s domain, providing a more robust foundation for unified conversion tracking.
• It’s the only tag format that allows for the tracking of 1×1 impressions on external social media platforms.
• It automatically generates new counter activities every time a user visits a high-traffic page on the site.
• It eliminates the requirement for a Floodlight configuration at the advertiser level within Campaign Manager 360.

Explanation

The Google tag is the recommended format for Floodlight measurement in Campaign Manager 360. It supports more durable conversion measurement because it operates from the advertiser’s site and can use first-party cookie behavior instead of relying only on legacy third-party tag formats. This improves continuity for attribution, reporting, and optimization when browser restrictions limit third-party cookie availability. The Floodlight configuration still remains the container for conversion tracking settings.

Why the other options are incorrect

1×1 impressions track ad exposures, not site-side conversion measurement through the Google tag.

Counter activities are created manually in Campaign Manager 360, not automatically from page traffic.

Floodlight configuration is still required because it contains the advertiser’s conversion measurement setup.

Source for verification

https://support.google.com/campaignmanager/answer/7554821?hl=en

https://support.google.com/campaignmanager/answer/12131703?hl=en

A brand is launching a high-budget video campaign across 10 different streaming publishers. How can the advertiser make sure the video ads, tracking pixels, and companion banners are delivered to all publishers in a standardized format?

• Package all assets and tracking into a single Video Ad Serving Template (VAST).
• Use only in-banner video formats to avoid the need for external video players.
• Email the raw MP4 files and separate tracking pixels to each publisher’s ad ops team.
• Create a separate rich-media banner for every publisher using a JavaScript tag.

Explanation

VAST is the standardized video tag format used to communicate between ad servers and publisher video players. In Campaign Manager 360, VAST tags package video serving files, companion creatives, and tracking pixels for delivery into a publisher’s compliant player. This lets multiple publishers receive a consistent video ad structure while still allowing the player to render the assets. It is the correct format for standardized in-stream video delivery across streaming publishers.

Why the other options are incorrect

Rich-media banner is not the correct format for in-stream video delivery through publisher video players.

Raw MP4 files do not provide standardized ad serving, companion delivery, or tracking instructions.

In-banner video avoids the in-stream player workflow and does not meet standardized streaming publisher delivery needs.

Source for verification

https://support.google.com/campaignmanager/answer/3311603?hl=en