A marketer wants to track more than just sales and visits; they need to capture specific promo codes used during a transaction. Which feature of Floodlight should they use?
- Enhanced attribution
- Custom variables
- Consent mode
- Counter tags
Explanation
Custom Floodlight variables are designed to capture information beyond standard conversion details such as visits and revenue. Google states that they let advertisers pass additional contextual values with Floodlight tags, using keys like u1, u2, and so on. That makes them the correct feature for recording transaction-specific data such as a promo code used during checkout. Those values can then be used in reporting, which is why this feature fits a need for richer conversion detail instead of basic sales counting alone. Google Help+2
Why the other options are incorrect
Counter tags count conversion activity, but they do not by themselves provide the extra transaction-detail fields used to pass promo code values. Google Help+1
Enhanced attribution improves attribution signals, not the capture of custom transaction attributes like promo codes. Google Help+1
Consent mode manages consent signals for Google tags, not custom conversion metadata collected in Floodlight. Google Help
Source for verification
Custom Floodlight variables — Campaign Manager 360 Help Google Help
About Floodlight and Floodlight activities — Campaign Manager 360 Help Google Help