Set up 鲸鸿动能 | Petal Ads

鲸鸿动能 | Petal Ads is an ad network integrated with Adjust. Our integration lets 鲸鸿动能 | Petal Ads receive attribution and in-app event data through automated callbacks.

In this article, learn how to set up measurement with 鲸鸿动能 | Petal Ads for your app. This includes activating the integration, creating a campaign link, and choosing what data Adjust can share with 鲸鸿动能 | Petal Ads.

Before you begin


Select 鲸鸿动能 | Petal Ads and your app in Campaign Lab

  1. Under Campaign Lab, select Partners.
  2. Select New partner > 鲸鸿动能 | Petal Ads. Select Next to move to the next screen.
  3. In the App selection screen, choose the app for which you want to create the link, and enable the integration to share data with 鲸鸿动能 | Petal Ads.
  4. Select Next.

Enable data sharing

Enable data sharing to activate the integration with 鲸鸿动能 | Petal Ads. To enable data sharing:

  1. Enter your SecretKey (for help finding this, see this section or contact your 鲸鸿动能 | Petal Ads representative). Your SecretKey is required only if you run campaigns in China.

Once you enable data sharing with 鲸鸿动能 | Petal Ads, Adjust automatically sends 鲸鸿动能 | Petal Ads the following data, by default:

  • installs (attributed only)
  • event (attributed only)

Set your data sharing options

If you’re working with a multi-platform app with data sharing enabled for multiple platforms, you can:

  1. Separate data sharing options at the platform-level by selecting Use platform-specific settings.
  2. Set the same data sharing settings for multiple platforms by selecting Use global settings.

Now, under What will be shared by default?, review the activities that Adjust shares with 鲸鸿动能 | Petal Ads by default.

  • installs (attributed only)
  • event (attributed only)

Send additional data

Choose the amount and type of data that you want to share with 鲸鸿动能 | Petal Ads through callbacks. 鲸鸿动能 | Petal Ads may use this information to optimize performance.

Map events

Map events that you want to share to the values that 鲸鸿动能 | Petal Ads can receive. Data for unmapped events is not shared with 鲸鸿动能 | Petal Ads.

Under Map events, follow these steps to choose the in-app events you want to directly send to 鲸鸿动能 | Petal Ads.

  1. Select Map event.
  2. In the Adjust event list, choose the Adjust event that you want to share with 鲸鸿动能 | Petal Ads.
  3. In the Partner event list, choose or enter a custom event name that you want to map the Adjust event to. You might have to map an event to several values.
  4. Select Apply.

Now 鲸鸿动能 | Petal Ads will receive in-app event data for each of your linked events.

Configure your link and settings

You have the option to set your:

Create your link and share it with 鲸鸿动能 | Petal Ads

In the Setup review screen, you can review your choices. You can also go back and make changes to:

  • Your selected app
  • Data sharing options
  • Link structure parameters
  • User destinations
  • Attribution settings

Select Create link to create your click URL, impression URL, QR code and link token. Creating a link also enables data sharing and the integration with 鲸鸿动能 | Petal Ads.

Once you’ve created your link, share it with 鲸鸿动能 | Petal Ads for placement in campaigns.

Partner specific setup instructions

Create a campaign and see your secret key

In the Petal Ads dashboard, you create campaigns and enter the Adjust tracker URL. Once you do this, your Petal secret key displays.

In your Petal Ads dashboard:

  1. Select Tools > Associated tools.
  1. Select + New Association.
  1. In the Tool Provider field, select "Adjust".
  2. Enter your tracking URL(s).
  3. Select Submit.

From your overview list, you can now see Adjust added. Click to see your Petal Ads secretKey.

Run a conversion test

Before going live, you will need to run a conversion test at the very beginning. 
Once the conversion test is successful, you will see “Activated“ status in the Petal Ads dashboard.

List of all parameters forwarded to 鲸鸿动能 | Petal Ads

鲸鸿动能 | Petal Ads requires Adjust to send the following parameters (data points) with your callbacks:

{ip_address}Device IP address
{tracking_enabled}1 if tracking is enabled, 0 if not
{created_at_milli}Activity timestamp with millisecond placeholders
{created_at}Activity timestamp
{oaid_md5}OAID MD5 hash