How to Configure a Campaign with Wechat Ads

  • Advertisers

Introduction

Wechat, one of AppsFlyer's integrated partners, is a Chinese multi-purpose messaging, social media and mobile payment app developed by Tencent.

To configure your campaigns with Wechat, follow the steps below.

Setting Up Wechat

Go to the dashboard of your app and click on Integrated Partners on the left bar.

Integrated_Partners_link.png

Enter "Wechat" in the search field and click on its logo to open Wechat's configuration window.

Wechat's configuration window includes 4 tabs: Integration, Tracking link, Data enrichment and Permissions. Click on the items below to read about the tabs setup. 

For a detailed description of the Partner Configuration Window Header, click here.

 Tip

  • The General Settings step in the Integration tab is mandatory for all partners
  • All the rest of the steps are either descriptive or optional

Integration Tab

The Integration Tab is divided into different sections as described below. 

 Note

As an ALL-Installs network, Wechat prefers to receive postbacks for all new installs of your app from ANY source, including organic. It is recommended to select Events attributed to any partner to send all install postbacks to Wechat. 

General Settings

Partner ID

Wechat connects with AppsFlyer via three unique parameters:

  1. Sign ID

  2. Wechat App ID

  3. Encrypt Key

If you don't already have the Sign ID, Wechat App ID and Encrypt Key you must obtain it from Wechat to continue with the integration.

wechat-integration-general-settings.png

 

Default Postbacks

AppsFlyer can send automatic postbacks to Wechat following user installs and re-engagements. Use this section to define the source of the users that allow sending these postbacks. 

wechat-default-postbacks.png

Select Only events attributed to this partner for events coming only from users attributed to Wechat.
Select Events attributed to any partner or organic to have your entire user base available to be reported to Wechat.

In-App Events Settings

In this section you can map your AppsFlyer events with Wechat via postbacks.

wechat-in-app-events.png

  1. Enter the Encrypt Key again.
  2. Toggle In-App Event Postbacks to ON
  3. Select the Sending Option for all SDK defined events.
    - Only events attributed to this partner for events coming only from users attributed to this partner
    - Events attributed to any partner or organic to have your entire user base available to be reported to the partner
  4. Click Add Event to add an SDK Event to the list
  5. Complete the following parameters:
Parameter Name Description
SDK Event Name The name of the event, as received by AppsFlyer either from the SDK integrated in your app, or from server to server events.
Tip - If you don't see the event you want in the list, make sure to activate the event on a device with a non-organic installation and recheck.
Partner Event Identifier The unique name or ID of each event as defined on Wechat's side. 
Obtain the corresponding Event ID from Wechat and set in the text field.
Send Revenue When unchecked - AppsFlyer sends all the parameters of the rich in-app event to the partner, except for the revenue parameter, which is contained in the af_revenue parameter.
When checked - AppsFlyer sends all the parameters including the revenue value (if it exists in the event). 

Tracking Link Tab

In this tab, you can create the tracking links you want to send to Wechat for tracking Wechat's campaigns, ad sets or even single ads. Note that AppsFlyer DOES NOT save your generated partner's tracking links.

This tab is divided into different sections:

Tracking Link Parameters

In this section, select which parameters you want to add to the tracking link. 

Adding parameters to the tracking link here enables you to later perform thorough drill-down analyses. Parameters that are already defined on the tracking link can be edited by adding them and their new values here.

  • Campaign - add it to compare different campaigns running with Wechat. 
    Tracking link parameter: c
  • Adset - set ad set names to compare different ad sets within specific Wechat campaigns.
    Tracking link parameter: af_adset
  • Ad Name - set ad set names to compare different creatives within specific ad sets within specific campaigns Wechat.
    Tracking link parameter: af_ad
  • Site ID and Sub Site ID - set Site ID parameter to attribute installs to specific publishers. If many publishers exist, we advise on limiting the number of used site IDs and using the sub site ID parameter, to avoid exceeding the site ID limitations.
    Tracking link parameters: af_siteid and af_sub_siteid
  • Subscriber Parameters - use any of the 5 subscriber parameters to insert useful values. Note that these parameters get parsed and appear in the raw data report, which makes them very handy for performing data aggregation or filtering.
    Tracking link parameters: af_sub1, af_sub2, af_sub3, af_sub4, af_sub5 


tracking-link-params.png

Add any other parameter to the tracking link simply by typing it in a new parameter box. For more information about AppsFlyer's Tracking Link Structure and Parameters.

Click-Through Attribution

This slider allows you to set the maximum time from click to install. Only installs (first launches) that take place within the lookback window may be attributed to Wechat.

Tracking link parameter: af_click_lookback

More details about the click lookback window here

Click Tracking Link

This is the tracking link that contains all the setup information you have set for it. Send it to Wechat to be activated when leads click on a corresponding ad.

Data Enrichment Tab

 

Currently, the integration with Wechat doesn't include Cost Data and Ad Revenue.

wechat-data-enrichment.png

Permissions Tab

In this tab, you can select the permissions to grant to the partner, whether the partner acts as an ad network, agency or even both. Note that even if attribution is disabled for the partner, the permissions tab is active and you can grant control to the partner.

wechat-permissions.png

 
Was this article helpful?
0 out of 0 found this helpful