To ensure that transformed information from Bidding signals is properly consumed by the specified targets, certain settings need to be configured on those targets
1. When your target is Google Analytics 4 (GTAG and Firebase)
1.1. If you are using the 'purchase' event and a dedicated Google Analytics 4 property, make sure to configure it as needed. For example:
currency
referral exclusions
data filters
data retention
Google signals
link to Google Ads or other products
etc.
Ensure that the property is configured according to your specific needs.
1.2. If you are using the 'precis_ecomm' event type with an existing Google Analytics 4 property:
Enable the following event-level custom dimensions:
transaction_id (be aware of high cardinality custom dimensions)
market (not needed if operating in a single market)
Mark 'precis_ecomm' as a conversion.
2. When your target is Google Ads
You need to set up a conversion action for click conversions in Google Ads to properly receive information from Alvie. Follow this documentation (Part 1) to set up an import for the click conversion action.
3. When your target is Facebook Ads
If you have selected an existing event that you already track elsewhere when setting up the Facebook target for Bidding signals in Alvie, make sure to pause that event when going live with Bidding signals to prevent duplicate event tracking.
4. When your target is Google Tag Manager: Server-side
In this case:
Download the GTM container JSON file.
Create a new workspace in your Server GTM container.
Click on 'Admin' in the main menu.
Click on 'Import container'.
Click 'Choose container file' and select the JSON file you’ve downloaded.
Under 'Choose workspace', click 'Existing' and select the workspace you’ve created.
Choose 'Merge' as the import option.
Select 'Rename conflicting tags, triggers, and variables'.
Click 'Confirm'.
Modify the variable 'Bidding signals - bearer token' and add the value related to your Bidding signals configuration.