How to Send Data from a Successful Stripe Payment to the Meta Conversions API (CAPI)
IN THIS ARTICLE
Sending data from a successful sale to the Meta Conversions API is mainly used to improve the performance and accuracy of your campaigns within the Meta Platforms ecosystem.
In practice, this solves an important issue: browser-based tracking (pixel).
In different scenarios, this type of tracking is not possible, such as when the payment is completed on an external platform outside your website/store, as is the case with Stripe.
Using Albato, this type of flow becomes possible, and below you will learn in just a few steps how to configure this automation.
Connecting the apps
The first step is to make sure that both apps we will use in this automation are connected in Albato.
If you haven’t set this up yet, go to the Apps section in Albato, click on Add a Connection , and search for Stripe.

Follow all the instructions until you see that the connection has been successfully created. If you have any questions during this process, this article can help.
Finally, repeat the process, but this time to connect the Meta Conversions API. Once you also see the success message, you will be ready to create your automation.
How to create the automation
The first step is to go to the Automations section in Albato and click to Create a new automation.

Next, click to add a trigger to your automation.

At this stage, select the Stripe app and then choose the Succeeded payment trigger.

Now click to add a new action.

By default, Stripe does not provide all the customer data who made the purchase, so we need to add another Stripe step to retrieve the customer data using their ID.

After clicking save, in the ID field, use the ID collected from the trigger step, like this.

Now, this step will provide all the data we need to send to Meta via the Conversions API.
However, note that the format of this data must be encrypted using a format called hash, specifically SHA-256 (Secure Hash Algorithm 256 bits).
In Albato, it is fully possible to configure this. To do so, add a new tool by clicking here.

Then, select the Hash Value tool.
If you want to learn more about this tool and its settings, see the Hash Value Tool article.

In the first field (algorithm), select the standard required by Meta (SHA-256). In the value field, insert the email field obtained from the customer data step, like this.

Important: By default, Meta requires either email or phone to be sent. In this step, we configured email, but you can also send the customer's phone number and first name. To do this, simply repeat this step. You need to add one hash step for each parameter you want to send.
Another important point is the format that the data must follow before being processed by the hash tool and sent to Meta.
The following standards must be respected.
- Email: must not contain spaces or uppercase letters
- First name: must not contain spaces, uppercase letters, accents, or special characters
- Phone: must include the country code and must not use the "+" character Therefore, make sure that the information stored in Stripe for this customer always follows these guidelines.
Finally, add the Meta step to send the conversion. Click to add the final step.

Then, select the corresponding action (send event).

Now you need to fill in some required fields requested by Meta. First, fill in the email field using the hashed value.

If you processed other values as mentioned (phone and first name), fill in the corresponding fields using the output from each hash step. You can also send the purchase value in the appropriate field. If you fill in this field, don’t forget to include the currency used in the payment.
The other required fields must be filled manually and should look like this.

Now just save this step and activate the automation.

Now you will have a fully automated flow, ensuring that the data from each Stripe sale is sent to Meta in the HASH format accepted by Meta.

Conclusion
With this automation, each successful Stripe payment can be sent to Meta in the correct format, helping your campaigns receive more reliable conversion data and improving attribution without manual work.
Did this answer your question?