Filtering Data

Our objective is to confirm whether a conversion happened before sending the signal and parameters to a network. To achieve this, we need a unique identifier for that conversion, which is usually the transaction_id for transaction-based conversions. In this guide, we will use a common example of an ecommerce store where the conversion is a purchase, and each purchase has a unique ID that is submitted to our data layer.

Before delving into the process of "how", let us first briefly discuss the "why" aspect of it. Some marketing tools lack the capability of deduplication within their internal processes, which means that the tracking system has to filter out duplicate signals. This usually happens during page reloads, such as when you close the website app on your smartphone after making a purchase and then reopen the same app. This results in the recent page being reloaded and unintentionally sending a redundant conversion signal. To filter out such signals before sending the conversion, we can implement a short routine.