A tracking pixel is a 1x1 pixel image that gets placed in the header or the footer of the sent email so that when the recipient reads/opens the email the image gets downloaded and you can track the downloads of the image.

Obviously, it is important to keep a correlation between the image and the emails sent, so you can uniquely identify each email.

You need to create 2 processes in PROCESIO and 1 Webhook:

We need to create first the Webhook, by selecting the option “I want to manually define webhook payload”. You can give it any name you want.

In the “Payload definition” section paste the following JSON structure and click “Generate data model”:

Now, copy the “Webhook URL” and save the webhook!

The first process looks like in the following image:



Define the variables that you are going to use in this process as in the following image:



Now configure the actions as follows:

EmailGuid (Utilitary/Generate GUID action) - it generates a unique ID (GUID) for the email that is about to be sent.

Register Email (Database/SQL Server/Execute command action) - it logs in a database the email that is about to be sent so you can reference it later.



You will need to define your SQL server credentials to connect to a database where to store data in a table.

This action executes a stored procedure in the database which in turn saves the information to a table.

To create the required objects in the database, run the following script:

Encode tracking URL (Strings/String Url Encode action) - it encodes the payload to be sent via the webhook to the 2nd process



String Concat (Strings/String Concat action) - it concatenates the Webhook URL you copied when creating the webhook and the encoded payload, as shown in the image bellow.



Send Email (Send Email action) - it sends the actual email.



You will need to define your SMTPserver credentials to send emails with PROCESIO.

Keep in mind that you need to mark “Body is HTML” and in the Body, you need to have this:

Where

Is the actual Tracking Pixel, basically adding the Webhook URL + Payload as an image to the email so that the email client will try to download the image triggering the webhook which in turn will trigger the 2nd process to run.

The 2nd process looks like in the following screenshot:



We need to assign the created webhook to this process so that the webhook will trigger this process when an email is read.

Go to the right-hand sidebar, to the “Webhooks” menu and click “Assign webhook”, as seen in the screenshot:



Now, select the webhook you created and give a name to the “Local variable name”:

Now, define the variable “QueryOUT” that you are going to use in this process as in the following image:



You will notice that the “TrackEmail” variable coming from the webhook is already visible and you will be able to use it in the process.

Now configure the actions as follows:

Track email in DB (Database/SQL Server/Execute command action) - it logs in a database the email ID that was read.



You will use the same SQL server credentials you used in the 1st process to connect to a database where to store data in a table.

The command is:

This action executes a stored procedure in the database which in turn saves the information to a table.

To create the required objects in the database, run the following script:

By using the import file you will obtain this almost ready to use, use-case directly to the workspace. You won't have to follow all the above mentioned steps but only perform the import & some configuration adjustments depicted in the video below.

Video tutorial on how to import

Watch below youtube tutorial, in order to do the ncessarly adjustment post-import.