SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

How to migrate from Facebook CAPI Classic to Actions?

Objective

Assuming you're already using Facebook Conversions API (Classic) destination, the Facebook Conversions API (Actions) destination is expected to have no breaking changes when upgrading. With the exception of a few new properties added to your events in the new Actions destination, there should be no difference in the data received in Facebook CAPI when using either of the Facebook destinations.

This guide walks you through how to re-create your mappings in the new Facebook CAPI (Actions) destination. Since this destination is built on a different framework from the Classic one, the mappings can't be migrated automatically and will need to be set up again from scratch.

If you'd like to double-check everything before switching over, you can configure the new destination to point to a different Facebook project, connect it to the same source(s) as your Classic destination, and manually verify that the events look correct.

 

Product

Twilio Segment

 

Environment

Segment Console

 

Procedure 

To create a custom destination action, start from the Mapping tab. If necessary, click New Mapping to create a new action.

  1. In the edit panel, define the conditions under which the action should run.
  2. Test those conditions to make sure that they correctly match an expected event. This step looks for events that match the criteria in the debugger queue, so you might need to trigger some events with the expected criteria to test your conditions. You can skip the test step if needed, and re-try it at any time.
  3. Set up the data mapping from the Segment format to the destination tool format.
  4. Test the mapping with data from a sample event. The edit panel shows you the mapping output in the format for the destination tool. The Select Object option sends the entire object from the event, while the Edit Object option lets you map each individual property. You can change your mapping as needed and re-test.
  5. When you're satisfied with the mapping, click Save. Segment returns you to the Mappings table.
  6. In the Mappings table Status column, verify that the Enabled toggle is on for the mapping you just customized.

The required fields for a destination mapping appear automatically. Click + to see optional fields.

 

Additional Information 

More information can be found in the docs below:

Have more questions? Submit a request
We can’t wait to see what you build.
Powered by Zendesk