Differences Between Sygnal Pixel (rrq) and Facebook Pixel (fbq)

Sygnal Pixel (rrq) and Facebook Pixel (fbq) are both tools for tracking user interactions on web pages, but they have some key differences. This article outlines these differences to help you understand how to use each effectively.

#Terminology

Signal: Used instead of the term "event" to describe tracking interactions.

#Supported APIs

Sygnal Pixel (rrq):

track: Used for both custom and standard signals.

rrq("track", "SignalName", { parameter: "value" });

Facebook Pixel (fbq):

track: Used for standard signals.

fbq("track", "SignalName", { parameter: "value" });

trackCustom: Used for custom signals.

fbq("trackCustom", "CustomSignalName", { parameter: "value" });

Purchase Events

Sygnal Pixel: All purchase signals must include the order_id parameter, which corresponds to the actual order ID from the sales platform database. This is crucial for deduplicating multiple purchase signals.
```
rrq("track", "Purchase", {
  value: "0.00",
  currency: "USD",
  order_id: "ORDER12345",
});
```

Facebook Pixel: The order_id parameter is optional, but including it can help in deduplication.

fbq("track", "Purchase", {
  value: "0.00",
  currency: "USD",
  order_id: "ORDER12345",
});

#Unsupported Features

Sygnal Pixel does not support running multiple pixels on the same page by design. Therefore, the following APIs from Facebook Pixel are unsupported in Sygnal Pixel:

fbq('consent', 'revoke')
fbq('consent', 'grant')
fbq('set', 'autoConfig', 'false', 'your-pixel-id-here')

Using these unsupported calls with Sygnal Pixel will result in no action or errors.

#Summary

While both Sygnal Pixel and Facebook Pixel serve the purpose of tracking user interactions, there are notable differences in their APIs and supported features. Understanding these differences ensures you implement tracking correctly and leverage the unique capabilities of each pixel.