Final answer:
For Floodlight tags to properly attribute in-app conversions, the Device ID must be passed into the dc_rdid parameter for accurate tracking.
Step-by-step explanation:
For Floodlight tags to properly attribute in-app conversions, the Device ID needs to be passed into the dc_rdid parameter. This allows the Floodlight tracking system to accurately record and associate user interactions within the app to conversions. It's essential that the dc_rdid parameter is properly implemented within the app's codebase for the conversion data to be reliable. Furthermore, the Floodlight tag might also need to be set as an INS tag with mobile capacity or assigned an app ID to ensure proper functioning within mobile environments. Therefore, developers and marketers should work closely to ensure that these parameters are correctly integrated as part of the in-app conversion tracking setup.
In order for Floodlight tags to properly attribute in-app conversions, there are a few steps that need to be taken within the app:
The device ID needs to be passed into the dc_rdid parameter. This allows the Floodlight tag to identify and track the specific device.
The tag needs to be set as an INS tag with mobile capacity. This ensures that the tag is properly configured for tracking in-app conversions.
A global site tag must be used. This tag is responsible for collecting data from the app and sending it to the Floodlight tag for attribution.
The tag needs to be assigned an app ID. This app ID uniquely identifies the app and assigns the conversion credit to it.