Cookie and tracking notice

How advertising measurement works.

Meta Pixel and Conversions API may be used to measure website enquiries and improve campaign delivery.

They help us understand whether an ad led to a visit or enquiry. They do not receive your free-text workflow summary.

Last updated: 19 June 2026

Meta measurement status loading

Meta Pixel Conversions API UTM campaign links Tracking choice

What the site uses.

A concise record of advertising measurement and essential website tools.

01

Meta Pixel

The browser-based Meta Pixel may record page visits, successful form submissions, browser or device details, IP address, referring page, campaign information and Meta identifiers stored in cookies or similar technologies.

02

Conversions API

Conversions API sends matching server-side events to Meta to improve attribution and campaign delivery. After a form is submitted, this may include securely hashed contact details for matching. Browser and server copies of the same event should use one event ID so Meta counts the enquiry once.

03

Campaign and site tools

Links from ads may contain UTM parameters that identify the campaign or source. Essential hosting, security, anti-spam, email and form-delivery tools may also process basic technical information needed to operate the website.

04

What is excluded

Names, email addresses and confidential information should not be placed in URLs. ArxLayer should not send workflow summaries, client files, passwords, source code or sensitive personal information to Meta through Pixel or Conversions API events.