Note: We strongly recommend using dc_rdid to pass device identifiers instead of dc_muid. It's the publisher's responsibility to apply MD5 hashing to device identifiers. Campaign Manager 360 won't recognize MD5-hashed values of lowercase IDs. The identifiers must use all capital letters before they are hashed. The uppercase IDFA, Android ID, or AdID, run through an MD5-hash algorithm. You’ll still see this parameter when you export tags for old in-app placements. This parameter was used to distinguish in-app placements from in-page placements before the launch of the display compatibility. However, you may see some extra parameters(but only if your tags are secure). Your tags will generally look the same whether they serve to mobile or non-mobile inventory. kw= sz= widthxheight ord= dc_lat=0 dc_rdid=38400000-8cf0-11bd-b23e-10b96e4ddddd tag_for_child_directed_treatment=0 dcmt=text/xml dc_sdk_apis= dc_omid_p= dc_vast=4Ī sample tracking ad image tag for impressions: kw= sz= widthxheight ord= dc_lat=0 dc_rdid=38400000-8cf0-11bd-b23e-10b96e4ddddd tag_for_child_directed_treatment=0 dcmt=text/xml dc_sdk_apis= dc_omid_p= dc_vast=3 kw= sz= widthxheight ord= dc_lat=0 dc_rdid=38400000-8cf0-11bd-b23e-10b96e4ddddd tag_for_child_directed_treatment=0 dcmt=text/xml dc_sdk_apis= dc_omid_p= The beginning of a sample JavaScript tag (typically used for HTML5 or rich media banners):Ī sample pre-fetch tag (used for in-stream video and audio ads): The beginning of a sample ins tag (the preferred option for mobile environments):Ī sample standard tag (used for image banners): All these parameters must be populated by the publisher, so make sure your publisher has agreed to pass the necessary values. Here are some sample tags that include the parameters discussed above. If "Limit Ad Tracking" is off, the value is 0. A value of 1 means that the user has enabled the “Limit Ad Tracking” option for IDFA or AdID in order to opt out of interest-based ads and remarketing. ![]() A value of 1 indicates that this particular request may come from a user under the age of 13, under COPPA compliance.ĭc_lat=: Accepts a value of 0 or 1. Tag_for_child_directed_treatment=: Accepts a value of 0 or 1. ![]() SSAID is available for non-Play Android devices in China. Note: We strongly recommend using the dc_rdid parameter for device IDs instead of the legacy parameter dc_muid, which accepts uppercase MD5-hashed IDFA, Android ID, and AdID values. We will only accept values passed securely over SSL-enabled tags. The values should be the unhashed, raw value. The publisher must pass a value into this parameter in order to enable in-app conversion tracking. Your tags will not be be enabled for Floodlight conversion tracking, reach/frequency reporting, frequency capping, creative rotation, or audience lists (remarketing) without values in these parameters Parameter definitionsĭc_rdid=: User resettable device identifiers in the form of IDFA for iOS or advertising ID (AdID) for Android. Why you need to ensure publishers pass values to these parameters Note that if your placements are publisher-paid, you will not be able to download them before you send them to the publisher for approval. These parameters are all automatically included in all display placements since any display placement could potentially serve inside an app (but only if your tags are secure). These parameters are dc_rdid= and tag_for_child_directed_treatment= and dc_lat=. Placement tags serving inside apps require extra parameters for many important features. ![]() 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.Īd and creative setup: Consider mobile targeting options if you want to limit which devices receive your ads. This is necessary to enable many important features. You’ll need to make sure that your publisher can populate all of these parameters correctly if your placement will serve in an app. 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. There are, however, three important areas to consider: There is no special mobile placement, mobile ad, or mobile tag type. ![]() The basic trafficking process in Campaign Manager 360 is the same for all types of devices, including mobile: assign creatives to ads, assign ads to placements, and send tags to publishers. The ins tag is the preferred option for a mobile environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |