Template rendering information flow advertisement: Supports graphic and video styles. Developers do not need to edit and render the advertisement styles by themselves. They can directly call the relevant interface to get the advertisement view to display. Developers can adjust the style of the selected template on the CSJ platform at any time. Under the premise of reducing access costs, the level of cpm will not be affected, and high competitiveness can still be maintained.
Supported ad sizes: Developers can select multiple templates and multiple sizes on the CSJ platform. Template rendering information flow ads support developers to adjust and edit
Note: Developers are not allowed to add buttons to the view and block ads.
Template feed ads： Provided by default
Template rendering information flow request method（TTNativeExpressAd）
Attention： The template ad request method requires the developer to set the setExpressViewAcceptedSize parameter in dp.
If the height is set to 0, the returned view will be highly adaptive according to the different templates checked on the platform.
Create ad request AdSlot
The code ID created by the platform starts with 9 and 9 digits
The number of requests is 1-3. It is recommended to set to 1
Set the size of the request template creative unit: dp
Call loadNativeExpressAd(AdSlot adSlot, @NonNull NativeExpressAdListener listener) to load ads asynchronously
Note: The click event registration time is before the ad render, otherwise it will affect the display and click data reporting
Advertisement request failed callback The returned error code (code) indicates the reason for the failure of the advertisement request.See the link for details
A callback for a successful ad request, the client can call render() in the callback for ad rendering
The callback of the ad click, the action after the click is controlled by the sdk.
Advertisement display callback, display volume can be counted in the method provided by CSJ
Personalized template rendering failed
The personalized template is rendered successfully, the client can directly add the view of the advertisement to the control to be displayed in the callback
The dislike logic helps us to improve the advertising experience and match, please follow the access instructions to set:
The following logic is the logic in the CSJ version 3500 SDK. SDK developers below 3500 version can refer to the corresponding demo for integration
Callback when the user clicks on filterWord in the case of a custom style
In the case of custom styles, the user clicked "Why see this ad"
The default dislike style, click filterWord to call back. The developer can remove the ad in this callback
Default dislike style, dislike pop-up window shows back
Default dislike style, click to cancel callback
The default dislike style, the user repeatedly clicks the dislike button to call back. 3600 version abolished
Ads that have been displayed and are no longer used need to call the destroy method to destroy the ads in time to avoid excessive memory usage.
For the detailed code of the information flow of the personalized template, please refer to NativeExpressActivity in the Demo. If you use it in the information flow scenario, refer to NativeExpressListActivity.
1、In the parameter setting of the template size setExpressViewAcceptedSize, if the height is set to 0, the height will be adaptive
2、The template information flow closed pop-up window does not support removing, the dislike logic helps to improve the advertising experience and matching degree
3、The registration time of the click event of the advertisement needs to be before the advertisement render, otherwise it will affect the display and click data reporting.
Online Customer Service24/7 Online Customer Service BotManual customer service, weekdays 10~ 12 o'clock/14~ 19 o'clock