Search

How to Configure a Use Case to Send CAPI Events with Desty Commerce

Article author
Learning Center Mekari
  • Updated

Desty Commerce offers advantages over Room Tag-based triggers because events can be triggered automatically based on shopping activities that occur in the system. In addition, the transaction value from purchases can also be obtained automatically because transactions are recorded in the commerce system. Therefore, you do not need to rely on manually applying labels and can use the transaction value to support more accurate ROAS calculations.   
In the following guide, you will learn how to configure a use case to send CAPI events with Desty Commerce.

Important
Make sure the following requirements have been met:
- Desty Commerce is connected to Mekari Qontak.
- The product catalog is active.
|- Business Manager is connected to Mekari Qontak.

A. Configuration Steps

  1. Log in to your Qontak account, then select the “Settings” menu.
  2. Then select the Integrations tab, and click “Channel Integration”.
  3. Then, in the Meta conversion API manager section, click “Manage”.
  4. Then select one of the Pixel names, and click “View details”.
  5. Click “Add use case”.
  6. Then select Commerce as the trigger source by clicking “Add”.
  7. Enable the events you want to send. We recommend enabling all available events so that the data sent can provide a more complete view of the sales funnel. Then click “Add use case”.

B. Mapping Desty Commerce Activities to Meta Standard Events 


 

The Purchase event that includes the transaction value can help Meta optimize ad performance and serve as the basis for calculating ROAS in your reports.

C. Running Desty Commerce Together with Room Tag

Both trigger sources can be used simultaneously on the same Pixel. This configuration is suitable if some sales come from the Desty Commerce catalog, while other sales are processed manually through conversations.

To prevent events from being sent more than once, make sure each trigger source has a clearly defined division of responsibilities.

Important
Avoid configuring both sources to send the same event. If Desty Commerce has already sent the Purchase event, do not add a Room Tag use case that also sends the Purchase event to prevent a single transaction from being recorded more than once. 

This concludes the explanation of how to configure a Use Case to send CAPI Events with Desty Commerce.

Diskusikan fitur ini