Skip to content
Start free trial

Track request form conversions with Facebook (Meta) ads

Last updated:

When you embed your SortScape request form on your website, SortScape can tell your page the moment a new request is submitted. You listen for that signal and fire your own tracking tag, like a Meta Pixel lead conversion, so Facebook (Meta) ads, Google Ads, or any other platform can attribute the lead back to the campaign that sent it.

SortScape does not store any Facebook or Meta credentials. Your Pixel fires on your own website, using the Pixel you already have set up, so you stay in full control of what gets tracked.

What you need

Section titled “What you need”
  • Your request form embedded on your website (not just the shared link). See Managing leads and requests for the embed code.
  • Your tracking tag already installed on the same page, for example the Meta Pixel (fbq), Google Ads (gtag), or GA4.

How it works

Section titled “How it works”

When the form is embedded and a visitor submits a new request, SortScape sends a message from the form to your page and fires a browser event called sortscape:request-submitted on the page’s window. The event carries a unique ID for that submission in event.detail.eventId.

You add a small listener that reacts to this event and calls your tracking tag. The event fires only once per submission, so you won’t double-count if the visitor refreshes the success page.

The event fires for new requests only. It does not fire when someone updates an existing request, and it does not fire if the submission fails.

Set it up

Section titled “Set it up”
  1. Open Settings → Quotes & requests → Requests.
  2. Copy the Embed code and paste it on your website page (if you haven’t already).
  3. Under Conversion tracking, copy the example listener and paste it into the same page, just below the embed code.

The example that ships in SortScape fires a Meta Pixel lead conversion:

<script>
  window.addEventListener('sortscape:request-submitted', function (event) {
    fbq('track', 'Lead', {}, { eventID: event.detail.eventId });
  });
</script>

Passing eventID lets Meta deduplicate the conversion if the event is ever sent more than once, so a single submission counts as a single lead.

Using a different platform

Section titled “Using a different platform”

The sortscape:request-submitted event works with any tag or tool, not just Meta. Put your own tracking call inside the listener. For example, a Google Ads conversion:

<script>
  window.addEventListener('sortscape:request-submitted', function (event) {
    gtag('event', 'conversion', {
      send_to: 'AW-XXXXXXXXX/YYYYYYYYYYYYYYYY',
    });
  });
</script>

Replace the send_to value with your own conversion ID and label. The same pattern works for GA4, TikTok, LinkedIn, and other platforms: listen for the event, then call that platform’s tracking function.

Troubleshooting

Section titled “Troubleshooting”
  • The event never fires. Conversion tracking only works with the embedded form. If you send people to the shared request link (a separate SortScape page or new tab), your page can’t receive the event. Switch to the embed code instead.
  • Nothing happens in your ad platform. Confirm the Pixel or tag is installed and working on the same page as the form, then submit a test request. Meta’s Pixel Helper and Google’s Tag Assistant can confirm the event fired.
  • The conversion isn’t counted. Make sure your listener is on the page that holds the embedded form, and that it loads before someone submits.
  • You regenerated your form URL. Copy the embed code again and replace the old snippet on your site. Your conversion tracking listener can stay as it is.
Section titled “Related”