Mobile trafficking guidelines
The basic trafficking process in Campaign Manager is the same for all types of devices, including mobile: assign creatives to ads, assign ads to placements, and send tags to publishers. There is no special mobile
placement, mobile ad, or mobile tag type.
There are, however, three important areas to consider:
Placement tags: All placement tags include the additional dc_rdid= parameter, which your publisher will need to populate with resettable device IDs, and the optional tag_for_child_directed_treatment= and dc_lat= parameters. You’ll need to make sure that your publisher can populate all of these parameters correctly if your placement will serve in an app. This is necessary to enable many important features. See below for more details.
Ad and creative setup: Consider mobile targeting options if you want to limit which devices receive your ads. See below for more details.
Mobile reporting and in-app Floodlight: There are extra steps to ensure proper Floodlight tracking on in-app inventory, and to view mobile reporting dimensions. See below for more details.
App and App ID reporting:
Publishers must pass an app ID into the dc_msid= parameter to enable App and App ID reporting dimensions. For example: dc_msid=com.android.chrome for Google Play Store or dc_msid=535886823 for iOS App Store.
Monday, August 24, 2020
How do you traffick for Mobile devices?
Subscribe to:
Post Comments (Atom)
What to do when you have click discrepancies
Verify the discrepancy by pulling a CM Report from report builder. Do the publisher and CM report dates match? Are the reports for the same...
-
If you are trying to implement the Floodlight tag in email body. Please read this article completely before proceed. I'm afraid that ...
-
DCM Engineers are investing heavily in advanced spam filtering in DCM. Spam is an issue that Google has taken very seriously since the earl...
-
Track and report impressions & clicks generated by site-served creatives, text link, email, or hard-coded creatives. 1x1 Pixels track ...
No comments:
Post a Comment