Only available to paid customers, not new customers
The following table describes the supported media types and their fields.
The supported media types and reflow fields are affected by media policies and will be updated from time to time.
Media Name | Delivery method | Common points | Delivery description | Backflow mode | Exposure reflow | Click Backflow | Reflow Field | Supports Dual Watch Links |
Beery mile barrage net | Media Direct | Splash screen, information flow | The customer communicates with the media offline to determine the location and delivery time. Targeted conditions are supported. Targeted conditions will affect the unit price. Targeted crowd packages are not supported. Finally, Station B makes the delivery. Whether the backflow ID is supported requires communication between the customer and the media. OpenAPI backflow effect data is not supported. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, AAID, OAID, IP, UserAgent, operating system, timestamp, creative ID, media name, monitoring activity name, city, city level | Yes |
Media Bidding Platform | Information flow | Required advertising platform. Customers can create delivery orders in the background of the platform, support custom crowd packages, support openAPI upload, and support monitoring code backflow. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, AAID, OAID, IP, UserAgent, operating system, timestamp, creative ID, media name, monitoring activity name, city, city level | Yes | |
Programmatic delivery | Information flow | Using interesting media for delivery can support direct return. If other platforms are used, the data is on the third-party DSP platform, and the customer needs business communication to determine whether the deviceID can be retrieved. There are two ways:(1) other monitoring tools have been used to support one party's data uploading to QA; (2) media backflow monitoring can be used to return ID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, MAC, ANDROIDID, OAID, IP, UserAgent, operating system, timestamp, campaign ID, campaign name, order ID, order name, creative ID, creative name, media name, ad slot name, city, city level | Yes | |
TikTok /Headline | Media Direct | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time. Targeted conditions are supported. Targeted conditions will affect the unit price. Targeted crowd packages are not supported. Finally, the delivery is made by trembles /headlines. DeviceID return is not supported. | Monitor the ad delivery | Supported | The migration is supported. | BDID, IP, Useragent, operating system, timestamp, UserAgent, operating system, media name, monitoring activity name, city, city level Note BDID is an ID type specific to byte hopping. | Yes |
Media bidding platform (huge amount of advertisements can return, huge amount of Qianchuan cannot return) | Screen opening and information flow | For a huge amount of advertising platform, customers can create delivery orders in the background of the platform by themselves, support custom crowd upload, support openAPI upload crowd, support openAPI return effect data, and support monitoring code return DeviceID; Two methods:(1) other monitoring tools have been used to support one party's data upload to QA; (2) media return monitoring and ID return can be used. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, operating system, timestamp, ad group ID, ad group name, ad plan ID, ad plan name, creative ID, ad placement | Yes | |
Programmatic delivery | Screen opening and information flow | Using interesting media for delivery can support direct return. If other platforms are used, the data is on the third-party DSP platform, and customer business communication is required to determine whether deviceID can be obtained. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, MAC, AndroidID, OAID, IP, UserAgent, operating system, timestamp, campaign ID, campaign name, order ID, order name, creative ID, creative name, media name, ad slot name, city, city level | Yes | |
Kuaishou | Media Direct | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time, supports targeted conditions, which affect the unit price, does not support targeted crowd packages, and does not support openAPI to return effect data. Finally, the delivery is made by fast hands, and the monitoring code is supported to return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Media Bidding Platform | Screen opening and information flow | On the magnetic engine platform, customers can create delivery orders in the background of the platform by themselves, support custom groups, support openAPI uploads groups, support openAPI backflow effect data, and support monitoring code backflow DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, operating system, timestamp, ad group ID, creative ID, media name, monitoring campaign name, city, city level | Yes | |
Programmatic delivery | Screen opening and information flow | Using interesting media for delivery can support direct return. If other platforms are used, the data is on the third-party DSP platform, and customer business communication is required to determine whether deviceID can be obtained. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, MAC, AndroidID, OAID, IP, UserAgent, operating system, timestamp, campaign ID, campaign name, order ID, order name, creative ID, creative name, media name, ad slot name, city, city level | Yes | |
iQIYI | Media Direct | Patch, Open Screen, Giant Screen, Focus Chart | The customer communicates with the media offline to determine the location and delivery time, supports directional conditions, which will affect the unit price, does not support directional crowd packages, does not support openAPI return effect data, and finally is released by iQiyi, which supports monitoring code return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, OPENUDID, IP, UserAgent, operating system, timestamp, media name, monitoring activity name, city, city level | No |
Media Bidding Platform | Patch, Open Screen, Giant Screen, Focus Chart | Aiqiyi Qilin platform, customers self-help to the platform background to create delivery orders, support custom crowd upload, support openAPI upload crowd, support openAPI return effect data, support monitoring code return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, OPENUDID, IP, UserAgent, operating system, timestamp, media name, monitoring activity name, city, city level | No | |
Programmatic delivery | Patch, Open Screen, Giant Screen, Focus Chart | Using interesting media for delivery can support direct return. If other platforms are used, the data is on the third-party DSP platform, and customer business communication is required to determine whether deviceID can be obtained. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, MAC, AndroidID, OAID, IP, UserAgent, operating system, timestamp, campaign ID, campaign name, order ID, order name, creative ID, creative name, media name, ad slot name, city, city level | No | |
Mango TV | Media Direct | Patch, pause, open screen, information flow | The customer communicates with the media offline to determine the location and delivery time, supports directional conditions, which affect the unit price, does not support directional crowd packages, does not support openAPI to return effect data, and is finally delivered by Mango TV, which supports monitoring code to return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Media Bidding Platform | Patch, pause, open screen, information flow | Mango Qiming delivery management platform, customers self-help to the platform background to create delivery orders, support custom crowd upload, support openAPI upload crowd, support openAPI return effect data, support monitoring code return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes | |
Programmatic delivery | Patch, pause, open screen, information flow | Using interesting media for delivery can support direct return. If other platforms are used, the data is on the third-party DSP platform, and the customer needs business communication to determine whether the deviceID can be retrieved. There are two ways:(1) other monitoring tools have been used to support one party's data uploading to QA; (2) media backflow monitoring can be used to return ID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, MAC, AndroidID, OAID, IP, UserAgent, operating system, timestamp, campaign ID, campaign name, order ID, order name, creative ID, creative name, media name, ad slot name, city, city level | Yes | |
Tencent Department | Media Bidding Platform | Patch, open screen, information flow | Tencent advertising (advertising platform), customers self-help to the platform background to create delivery orders, support custom crowd upload, support openAPI upload crowd, support openAPI return effect data, do not support monitoring code return DeviceID, but can use Feedback URL to return the clicked DeviceID. | Feedback URL | - | Supported | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, operating system, timestamp, promotion plan ID, promotion plan name, ad ID, ad name, creative ID, creative name, ad slot name, city, city level | Yes |
Programmatic delivery | Patch, open screen, information flow | Using interesting media for delivery can support direct return. If other platforms are used, the data is on the third-party DSP platform, and the customer needs business communication to determine whether the deviceID can be retrieved. There are two ways:(1) other monitoring tools have been used to support one party's data uploading to QA; (2) media backflow monitoring can be used to return ID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, MAC, AndroidID, OAID, IP, UserAgent, operating system, timestamp, campaign ID, campaign name, order ID, order name, creative ID, creative name, media name, ad slot name, city, city level | Yes | |
NetEase Cloud | Media Direct | Open screen, focus map, information flow | The customer communicates with the media offline to determine the location and delivery time, supports directional conditions, which will affect the unit price, does not support directional crowd packages, and is finally delivered by Netease, does not support openAPI to return effect data, and supports returning DeviceID through monitoring code. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Media Bidding Platform | Open screen, focus map, information flow | Netease Easy Effect Platform, customers self-help to the platform background to create delivery orders, support custom crowd upload, support openAPI upload crowd, support openAPI return effect data, support monitoring the DeviceID of code return clicks. | Monitor the ad delivery | - | Supported | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes | |
Programmatic delivery | Open screen, focus map, information flow | Using interesting media for delivery can support direct return. If other platforms are used, the data is on the third-party DSP platform, and the customer needs business communication to determine whether the deviceID can be retrieved. There are two ways:(1) other monitoring tools have been used to support one party's data uploading to QA; (2) media backflow monitoring can be used to return ID-. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, MAC, AndroidID, OAID, IP, UserAgent, operating system, timestamp, campaign ID, campaign name, order ID, order name, creative ID, creative name, media name, ad slot name, city, city level | Yes | |
Himalayan | Media Direct | Open screen, patch, information flow | The customer communicates with the media offline to determine the location and delivery time, supports directional conditions, which will affect the unit price, does not support directional crowd packages, does not support return effect data, and is finally released by Himalaya. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Programmatic delivery | Open screen, patch, information flow | Using interesting media for delivery can support direct return. If other platforms are used, the data is on the third-party DSP platform, and the customer needs business communication to determine whether the deviceID can be retrieved. There are two ways:(1) other monitoring tools have been used to support one party's data uploading to QA; (2) media backflow monitoring can be used to return ID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, MAC, AndroidID, OAID, IP, UserAgent, operating system, timestamp, campaign ID, campaign name, order ID, order name, creative ID, creative name, media name, ad slot name, city, city level | Yes | |
Sohu Video | Media Direct | Patch, open screen, focus map, banner | The customer communicates with the media offline to determine the location and delivery time. Targeting conditions are supported. Targeting conditions affect the unit price. Targeting crowd packages are not supported. OpenAPI is not supported to return effect data. The media is finally released by the media. Monitoring code is supported to return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Media Bidding Platform | Patch, open screen, focus map, banner | Sohu remittance, customers self-service to the platform background to create delivery orders, support custom crowd upload, support openAPI upload crowd, support openAPI return effect data, support monitoring code return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes | |
Programmatic delivery | Patch, open screen, focus map, banner | Using interesting media for delivery can support direct return. If other platforms are used, the data is on the third-party DSP platform, and the customer needs business communication to determine whether the deviceID can be retrieved. There are two ways:(1) other monitoring tools have been used to support one party's data uploading to QA; (2) media backflow monitoring can be used to return ID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, MAC, AndroidID, OAID, IP, UserAgent, operating system, timestamp, campaign ID, campaign name, order ID, order name, creative ID, creative name, media name, ad slot name, city, city level | Yes | |
Video of potatoes | Media Direct | Patch, Open Screen, Focus Chart | The customer communicates with the media offline to determine the location and delivery time. Targeting conditions are supported. Targeting conditions affect the unit price. Targeting crowd packages are not supported. OpenAPI is not supported to return effect data. The media is finally released by the media. Monitoring code is supported to return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Media Bidding Platform | Patch, Open Screen, Focus Chart | - | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes | |
Qutoutiao | Media Direct | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time. Targeting conditions are supported. Targeting conditions affect the unit price. Targeting crowd packages are not supported. OpenAPI is not supported to return effect data. The media is finally released by the media. Monitoring code is supported to return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Media Bidding Platform | Screen opening and information flow | - | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes | |
Sina Video | Media Direct | Patch, Open Screen, Focus Chart | The customer communicates with the media offline to determine the location and delivery time. Targeting conditions are supported. Targeting conditions affect the unit price. Targeting crowd packages are not supported. OpenAPI is not supported to return effect data. The media is finally released by the media. Monitoring code is supported to return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Media Bidding Platform | Patch, Open Screen, Focus Chart | - | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes | |
Dou Fish TV | Media Direct | Patch, Open Screen, Focus Chart | The customer communicates with the media offline to determine the location and delivery time. Targeting conditions are supported. Targeting conditions affect the unit price. Targeting crowd packages are not supported. OpenAPI is not supported to return effect data. The media is finally released by the media. Monitoring code is supported to return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Media Bidding Platform | Patch, Open Screen, Focus Chart | - | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes | |
360 Phone Assistant | Media Direct | Patch, Open Screen, Focus Chart | The customer communicates with the media offline to determine the location and delivery time. Targeting conditions are supported. Targeting conditions affect the unit price. Targeting crowd packages are not supported. OpenAPI is not supported to return effect data. The media is finally released by the media. Monitoring code is supported to return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Media Bidding Platform | Patch, Open Screen, Focus Chart | - | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes | |
91 Assistant | Media Direct | Patch, Open Screen, Focus Chart | The customer communicates with the media offline to determine the location and delivery time. Targeting conditions are supported. Targeting conditions affect the unit price. Targeting crowd packages are not supported. OpenAPI is not supported to return effect data. The media is finally released by the media. Monitoring code is supported to return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Media Bidding Platform | Patch, Open Screen, Focus Chart | - | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes | |
Volcano small video | Media Direct | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time. Targeted conditions are supported. Targeted conditions affect the unit price. Targeted crowd packages are not supported. The delivery is finally made by the media. DeviceID return is not supported. | Monitor the ad delivery | Supported | The migration is supported. | BDID, IP, Useragent, operating system, timestamp, IP, UserAgent, operating system, media name, monitoring activity name, city, city level Note BDID is an ID type specific to byte hopping. | Yes |
Media Bidding Platform | Screen opening and information flow | - | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes | |
Programmatic delivery | Screen opening and information flow | Using interesting media for delivery can support direct return. If other platforms are used, the data is on the third-party DSP platform, and the customer needs business communication to determine whether the deviceID can be retrieved. There are two ways:(1) other monitoring tools have been used to support one party's data uploading to QA; (2) media backflow monitoring can be used to return ID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, MAC, AndroidID, OAID, IP, UserAgent, operating system, timestamp, campaign ID, campaign name, order ID, order name, creative ID, creative name, media name, ad slot name, city, city level | Yes | |
Watermelon Video | Media Direct | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time. Targeted conditions are supported. Targeted conditions affect the unit price. Targeted crowd packages are not supported. The delivery is finally made by the media. DeviceID return is not supported. | Monitor the ad delivery | Supported | The migration is supported. | BDID, IP, Useragent, operating system, timestamp, IP, UserAgent, operating system, media name, monitoring activity name, city, city level Note BDID is an ID type specific to byte hopping. | Yes |
Media Bidding Platform | Screen opening and information flow | - | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes | |
Programmatic delivery | Screen opening and information flow | Using interesting media for delivery can support direct return. If other platforms are used, the data is on the third-party DSP platform, and the customer needs business communication to determine whether the deviceID can be retrieved. There are two ways:(1) other monitoring tools have been used to support one party's data uploading to QA; (2) media backflow monitoring can be used to return ID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, MAC, AndroidID, OAID, IP, UserAgent, operating system, timestamp, campaign ID, campaign name, order ID, order name, creative ID, creative name, media name, ad slot name, city, city level | Yes | |
PP Assistant | Media Direct | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time, supports directional conditions, which will affect the unit price, does not support directional crowd packages, does not support openAPI backflow effect data, and finally is delivered by the media party, supporting monitoring code backflow DeviceID; There are two ways:(1) other monitoring tools have been used to support one party's data upload to QA; (2) media backflow monitoring can be used to upload ID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Media Bidding Platform | Screen opening and information flow | - | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes | |
Play more games | Media Direct | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time. Targeting conditions are supported. Targeting conditions affect the unit price. Targeting crowd packages are not supported. OpenAPI is not supported to return effect data. The media is finally released by the media. Monitoring code is supported to return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Media Bidding Platform | Screen opening and information flow | - | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes | |
Momo Native Advertising Platform | Media Direct | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time. Targeting conditions are supported. Targeting conditions affect the unit price. Targeting crowd packages are not supported. OpenAPI is not supported to return effect data. The media is finally released by the media. Monitoring code is supported to return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Media Bidding Platform | Screen opening and information flow | - | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes | |
Huichuan (formerly UC) | Media Direct | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time. Targeting conditions are supported. Targeting conditions affect the unit price. Targeting crowd packages are not supported. OpenAPI is not supported to return effect data. The media is finally released by the media. Monitoring code is supported to return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Media Bidding Platform | Screen opening and information flow | - | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes | |
Sogou Search | Media Direct | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time. Targeting conditions are supported. Targeting conditions affect the unit price. Targeting crowd packages are not supported. OpenAPI is not supported to return effect data. The media is finally released by the media. Monitoring code is supported to return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Media Bidding Platform | Screen opening and information flow | - | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes | |
Meitu Effect Marketing | Media Direct | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time. Targeting conditions are supported. Targeting conditions affect the unit price. Targeting crowd packages are not supported. OpenAPI is not supported to return effect data. The media is finally released by the media. Monitoring code is supported to return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Media Bidding Platform | Screen opening and information flow | - | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes | |
Programmatic delivery | Screen opening and information flow | Using interesting media for delivery can support direct return. If other platforms are used, the data is on the third-party DSP platform, and the customer needs business communication to determine whether the deviceID can be retrieved. There are two ways:(1) other monitoring tools have been used to support one party's data uploading to QA; (2) media backflow monitoring can be used to return ID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, MAC, AndroidID, OAID, IP, UserAgent, operating system, timestamp, campaign ID, campaign name, order ID, order name, creative ID, creative name, media name, ad slot name, city, city level | Yes | |
Meiyou | Media Direct | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time. Targeting conditions are supported. Targeting conditions affect the unit price. Targeting crowd packages are not supported. OpenAPI is not supported to return effect data. The media is finally released by the media. Monitoring code is supported to return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Media Bidding Platform | Screen opening and information flow | - | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes | |
Baidu | Media Direct | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time. Targeting conditions are supported. Targeting conditions affect the unit price. Targeting crowd packages are not supported. OpenAPI is not supported to return effect data. The media is finally released by the media. Monitoring code is supported to return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Media Bidding Platform | Screen opening and information flow | - | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, OAID, operating system, timestamp, media name, monitoring activity name, city, city level | Yes | |
A little information | Media Direct | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time. Targeting conditions are supported. Targeting conditions affect the unit price. Targeting crowd packages are not supported. OpenAPI is not supported to return effect data. The media is finally released by the media. Monitoring code is supported to return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Media Bidding Platform | Screen opening and information flow | - | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes | |
Zhihu | Media Direct | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time. Targeting conditions are supported. Targeting conditions affect the unit price. Targeting crowd packages are not supported. OpenAPI is not supported to return effect data. The media is finally released by the media. Monitoring code is supported to return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Programmatic delivery | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time, supports directional conditions, which will affect the unit price, does not support directional crowd packages, does not support openAPI backflow effect data, and finally is delivered by the media party, supporting monitoring code backflow DeviceID; There are two ways:(1) other monitoring tools have been used to support one party's data upload to QA; (2) media backflow monitoring can be used to upload ID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, MAC, AndroidID, OAID, IP, UserAgent, operating system, timestamp, campaign ID, campaign name, order ID, order name, creative ID, creative name, media name, ad slot name, city, city level | Yes | |
Changhong OTT | Media Direct | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time, and finally the media party puts the device ID back to support monitoring code. | Monitor the ad delivery | Supported | No click behavior | MAC, IP, UserAgent, OS, and timestamp | Yes |
Programmatic delivery | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time, and finally the delivery platform completes the delivery, supporting the monitoring code return device ID. | Monitor the ad delivery | Supported | No click behavior | MAC, IP, UserAgent, OS, and timestamp | Yes | |
TCL-OTT | Media Direct | Start a cloud computer | The customer communicates with the media offline to determine the location and delivery time, and finally the media party puts the device ID back to support monitoring code. | Monitor the ad delivery | Supported | No click behavior | MAC, IP, UserAgent, OS, and timestamp | Yes |
Programmatic delivery | Start a cloud computer | The customer communicates with the media offline to determine the location and delivery time, and finally the delivery platform completes the delivery, supporting the monitoring code return device ID. | Monitor the ad delivery | Supported | No click behavior | MAC, IP, UserAgent, OS, and timestamp | Yes | |
Hisense-OTT | Media Direct | Start a cloud computer | The customer communicates with the media offline to determine the location and delivery time, and finally the media party puts the device ID back to support monitoring code. | Monitor the ad delivery | Supported | No click behavior | MAC, IP, OS, and timestamp | Yes |
Programmatic delivery | Start a cloud computer | The customer communicates with the media offline to determine the location and delivery time, and finally the delivery platform completes the delivery, supporting the monitoring code return device ID. | Monitor the ad delivery | Supported | No click behavior | MAC, IP, UserAgent, OS, and timestamp | Yes | |
UC Wolong | Media Bidding Platform | Search | - | Monitor the ad delivery | Supported | The migration is supported. | deviceid, creative, timestamp, IP | Yes |
oppo | Media Direct | Lock Screen | The customer communicates with the media offline to determine the location and delivery time. Targeting conditions are supported. Targeting conditions affect the unit price. Targeting crowd packages are not supported. OpenAPI is not supported to return effect data. The media is finally released by the media. Monitoring code is supported to return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Programmatic delivery | Lock Screen | The customer communicates with the media offline to determine the location and delivery time, supports directional conditions, which will affect the unit price, does not support directional crowd packages, does not support openAPI backflow effect data, and finally is delivered by the media party, supporting monitoring code backflow DeviceID; There are two ways:(1) other monitoring tools have been used to support one party's data upload to QA; (2) media backflow monitoring can be used to upload ID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, MAC, AndroidID, OAID, IP, UserAgent, OS, Timestamp, Campaign ID, Campaign name, Order ID, Order name, Creative ID, Creative name, Media name, Ad slot name, City, City level | Yes | |
soul | Media Direct | Lock Screen | The customer communicates with the media offline to determine the location and delivery time. Targeting conditions are supported. Targeting conditions affect the unit price. Targeting crowd packages are not supported. OpenAPI is not supported to return effect data. The media is finally released by the media. Monitoring code is supported to return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Programmatic delivery | Lock Screen | The customer communicates with the media offline to determine the location and delivery time, supports directional conditions, which will affect the unit price, does not support directional crowd packages, does not support openAPI backflow effect data, and finally is delivered by the media party, supporting monitoring code backflow DeviceID; There are two ways:(1) other monitoring tools have been used to support one party's data upload to QA; (2) media backflow monitoring can be used to upload ID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, MAC, AndroidID, OAID, IP, UserAgent, operating system, timestamp, campaign ID, campaign name, order ID, order name, creative ID, creative name, media name, ad slot name, city, city level | Yes | |
Huawei Application Market | Media Bidding Platform | - | - | Monitor the ad delivery | Supported | The migration is supported. | OAID, advertising task ID, advertising task name, delivery application ID, delivery application name, channel package ID, channel package name, targeted package ID, targeted package name, promotion resource type, operating system, timestamp, media name, and monitoring activity name | Yes |
Programmatic delivery | Lock Screen | The customer communicates with the media offline to determine the location and delivery time, supports directional conditions, which will affect the unit price, does not support directional crowd packages, does not support openAPI backflow effect data, and finally is delivered by the media party, supporting monitoring code backflow DeviceID; There are two ways:(1) other monitoring tools have been used to support one party's data upload to QA; (2) media backflow monitoring can be used to upload ID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, MAC, AndroidID, OAID, IP, UserAgent, OS, Timestamp, Campaign ID, Campaign name, Order ID, Order name, Creative ID, Creative name, Media name, Ad slot name, City, City level | Yes | |
vivo | Media Direct | Lock Screen | The customer communicates with the media offline to determine the location and delivery time. Targeting conditions are supported. Targeting conditions affect the unit price. Targeting crowd packages are not supported. OpenAPI is not supported to return effect data. The media is finally released by the media. Monitoring code is supported to return DeviceID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Programmatic delivery | Lock Screen | The customer communicates with the media offline to determine the location and delivery time, supports directional conditions, which will affect the unit price, does not support directional crowd packages, does not support openAPI backflow effect data, and finally is delivered by the media party, supporting monitoring code backflow DeviceID; There are two ways:(1) other monitoring tools have been used to support one party's data upload to QA; (2) media backflow monitoring can be used to upload ID. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, MAC, AndroidID, OAID, IP, UserAgent, OS, Timestamp, Campaign ID, Campaign name, Order ID, Order name, Creative ID, Creative name, Media name, Ad slot name, City, City level | Yes | |
Lower Kitchen | Media Direct | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time, and finally the media party puts the device ID back to support monitoring code. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Bean Fruit Cuisine | Media Direct | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time, and finally the media party puts the device ID back to support monitoring code. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Look at the comics. | Media Direct | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time, and finally the media party puts the device ID back to support monitoring code. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |
Douban | Media Direct | Screen opening and information flow | The customer communicates with the media offline to determine the location and delivery time, and finally the media party puts the device ID back to support monitoring code. | Monitor the ad delivery | Supported | The migration is supported. | IMEI, IDFA, ANDROIDID, OAID, IP, UserAgent, Operating System, Timestamp, Media Name, Monitoring Activity Name, City, City Level | Yes |