Packet capture example

Overview

In daily feedback, there are many scenarios where developers need to provide relevant request information or ad creatives to Taku support colleagues for issue troubleshooting. The following content describes how to perform Taku ad packet capture.

📢: If you do not see any AnyThink-related domains during packet capture, please check whether the ad requests in the project are actually being sent and whether the SDK Initialization logic is normal.

Usage scenarios include but are not limited to the following:

• No ad fill
• Abnormal ad display
• Bad cases of ad blocking
• Ad complaints

Step 1: Client Configuration

Configure the network_security_config.xml file on the client side.

<network-security-config>
    <base-config cleartextTrafficPermitted="true" />
    
    <debug-overrides>
        <trust-anchors>
            <certificates src="user"/>
        </trust-anchors>
    </debug-overrides>
</network-security-config>

Step 2: Configure Charles

Configure Charles & install the Charles certificate. For specific configuration methods, refer to online tutorials or use this link.

Step 3: Ad Packet Capture

When developers actively request ads, they can capture Taku ad-related request data through the packet capture tool.

Developers provide the corresponding ad request and response information to Taku developer personnel for issue troubleshooting:

• The domain for ADX ad requests is: adx-xx.anythinktech.com/bid, adx-xx.anythinktech.com/request

• The domain for ad requests is: cn-api.anythinktech.com

• Save Request, Response