A large eCommerce brand is launching a summer sale and needs to track three distinct conversion points: newsletter signups, add-to-carts, and completed purchases. What’s the functional reason for creating a summer sale Floodlight activity group before generating the specific tags for these three actions?
- To provide a structural container that organizes the individual activities and allows aggregated reporting at the group level.
- To automatically map the newsletter signup tags to the high-priority ad placements within the campaign.
- To establish a unique, 30-day lookback window that overrides all other campaign-level attribution settings.
- To bypass the technical requirement of deploying the Google tag (gtag.js) on the brand’s global checkout pages.
Explanation
A Floodlight activity group is required because every Floodlight activity must belong to one. It groups related conversion actions so reporting can show each activity separately or summarize performance across the group. The group also defines whether the contained activities use counter activities or sales activities. This structure keeps signup, cart, and purchase tracking organized under the same campaign measurement framework.
Why the other options are incorrect
Newsletter signup mapping is not controlled by a Floodlight activity group.
Google tag bypass is incorrect because Floodlight tags still need proper site implementation.
30-day lookback window is controlled by conversion window settings, not by the activity group itself.
Source for verification
https://support.google.com/campaignmanager/answer/6100588?hl=en
https://support.google.com/campaignmanager/answer/2823234?hl=en