Facebook Ads Offline Conversion Tracking: CRM Events, Qualified Leads and Revenue

Facebook and Instagram Ads can generate large numbers of enquiries, but a low cost per lead does not necessarily mean profitable advertising.

One campaign may produce cheap form submissions that never answer the telephone. Another may appear more expensive in Meta Ads Manager but generate qualified opportunities, accepted quotations and high-value customers. If Meta receives only the original form-submission event, both campaigns are judged using an incomplete definition of success.

Facebook Ads offline conversion tracking helps close this measurement gap. By sending lead-status changes, appointments, sales and revenue from your CRM or back-office systems to Meta, you can measure what happens after the initial online conversion. In eligible campaign configurations, these signals can also help Meta optimise towards people more likely to become qualified leads rather than simply people likely to complete a form.

This is now better understood as a combination of Meta datasets, the Conversions API, CRM events and qualified-lead optimisation. The familiar term “offline conversion tracking” remains useful, but it no longer describes only purchases made in a physical shop. The same architecture can report a website enquiry that later becomes a sales opportunity, a Meta Instant Form lead that books a consultation, a telephone lead that purchases, or a deal closed by a sales team weeks after the advert was clicked.

This guide explains the strategy, current terminology, technical options and practical safeguards required to build a reliable closed-loop measurement system for lead generation.

What Is Facebook Ads Offline Conversion Tracking?

Facebook Ads offline conversion tracking is the process of sending business outcomes that Meta could not fully observe through the browser back to Meta for measurement and, where supported, campaign optimisation.

These outcomes may include:

• A new lead being contacted successfully

• A prospect meeting your qualification criteria

• A consultation, survey or sales appointment being booked

• A quotation or proposal being issued

• A sales opportunity being created

• A contract being signed

• An offline or telephone payment being completed

• A deal being marked closed-won

• The revenue associated with a sale

• A repeat purchase or renewal

Meta attempts to match the event to a person and relevant advertising interaction using the identifiers supplied. Matched events may then appear in reporting and attribution. When the correct CRM integration and performance goal are used, selected downstream outcomes may also become feedback for Meta’s ad-delivery system.

Meta describes the Conversions API as a connection between an advertiser’s marketing data and its optimisation systems. It can receive website, app, messaging, telephone, physical-store and CRM events. For offline and CRM activity, automated Conversions API integrations are generally more useful than occasional spreadsheet uploads because the feedback is faster and less vulnerable to manual errors.

Why the Word “Offline” Can Be Misleading

The original purpose of offline conversion tracking was to connect digital advertising with outcomes such as shop purchases and telephone orders. Its modern role is broader.

A lead can be captured online but become qualified offline. For example:

• Someone submits a form on your website

• A salesperson contacts the lead

• The lead attends a consultation

• A quotation is accepted

• Payment is taken by bank transfer

Only the first step is visible to a conventional browser-based Meta Pixel setup. CRM event tracking supplies the missing commercial outcomes. “Offline conversion” should therefore be interpreted as a result recorded outside the original Meta or website conversion session, not necessarily an event that happened without the internet.

Online Tracking, Conversions API and CRM Events

These technologies are complementary rather than interchangeable.

The Meta Pixel remains valuable for website behaviour and browser context. Conversions API does not make the Pixel obsolete. For website campaigns, a well-designed implementation commonly uses browser and server events together, with consistent event IDs so Meta can deduplicate the same action rather than count it twice.

CRM events are different. A qualified lead recorded three days after a form submission is not a duplicate of the initial lead; it is a separate lower-funnel outcome. It should have its own event time, meaning and identifier.

Why Lead-Generation Advertisers Need CRM Feedback

Ecommerce advertisers can often optimise towards a purchase recorded during the online session. Service businesses usually start with a much weaker signal: a lead.

The initial lead event cannot tell Meta whether the person:

• Was in the service area

• Needed the advertised service

• Had the required budget

• Supplied valid contact details

• Answered follow-up calls

• Booked an appointment

• Accepted a quotation

• Became a profitable customer

This produces a lead-quality blind spot. Meta’s delivery system is very effective at finding people likely to complete the event it is given. If the event is merely “submitted a low-friction form”, the system may find more form submitters without understanding which people generate revenue.

This is why improving Facebook Ads lead quality requires more than adding form questions. Landing-page quality, offer clarity, audience strategy, creative qualification, sales follow-up and CRM feedback all matter.

A Simple Commercial Example

Consider two campaigns with the following results:

If Ads Manager receives only the initial lead, Campaign A appears better because its cost per lead is lower. Once CRM stages and revenue are included, Campaign B is clearly the stronger commercial investment.

This is the central purpose of closed-loop measurement: replace a proxy metric with evidence from the sales process.

Meta Datasets and the Conversions API

Meta previously separated website Pixel data and offline event sets more visibly. Events Manager now uses datasets as broader containers that can receive information from sources such as websites, apps, messaging, offline activity and CRMs.

A dataset is the Meta-side destination and organisational layer for event data. It does not, by itself, integrate your CRM. You still need a method for moving data from the CRM into Meta, such as:

• A native CRM integration

• A supported partner connection

• An automation platform

• A custom Conversions API implementation

• A manual file upload for occasional or historic events

Our guide to Facebook Ads datasets explains this architecture in more detail.

The practical distinction is important. Creating a dataset or completing Meta’s CRM setup wizard does not automatically mean that valid events are being sent. Events Manager must receive correctly formatted events with sufficient matching information, and the chosen CRM stages must be mapped to meaningful outcomes.

CRM Funnel Events: What Should You Send?

The best event structure reflects genuine commercial progress without reproducing every administrative status in the CRM.

A sensible lead-generation framework may look like this:

Not every company needs every stage. A short sales cycle might require only Lead, Qualified Lead and Purchase. A considered B2B sale may benefit from Qualified Lead, Sales Opportunity and Closed-Won.

Define Stages Before Mapping Them

The CRM stage must have a consistent business definition. For example, “Qualified Lead” might mean all of the following:

• The person can be contacted

• The requirement matches the company’s service

• The location is serviceable

• The expected budget is viable

• The decision timeframe is credible

If one salesperson marks a lead as qualified after a brief conversation while another waits until a proposal is requested, the event becomes unreliable training data.

Fields should hold the source-of-truth data used for reporting and qualification. Tags can assist automation and categorisation, but they should not replace a controlled lifecycle or opportunity-stage model.

Use Positive Outcomes, Not Noise

Meta needs clear evidence of success. Avoid sending every minor action as though it were an equally valuable conversion. Internal notes, task creation, automated email sends, and unverified stage changes add noise without representing commercial progress.

Negative outcomes such as spam, duplicate or unqualified may be useful inside the CRM and in your own reporting, but they should not be treated as successful conversion events. The optimisation signal should represent the positive result you want more often.

Choose a Stage With Enough Volume and Reasonable Delay

The deepest stage is not always the best initial optimisation event.

Closed-won revenue is commercially strongest, but it may be too sparse or delayed for stable learning. A consistently defined qualified lead or attended appointment can provide a faster, more frequent signal. You can still send later sales and revenue events for reporting even if the campaign initially optimises towards an earlier milestone.

The right choice balances three factors:

• Value: the event should correlate strongly with revenue

• Volume: it should occur often enough to provide useful feedback

• Speed: it should be returned soon enough to influence decisions and delivery

There is no universal conversion-volume threshold that guarantees good results. A campaign with ten qualified leads a month will provide much less learning data than one with hundreds, but poor-quality volume is not a substitute for a well-defined event.

Qualified Leads Optimisation in Meta Ads

Meta separates three settings that are often confused:

“Qualified leads” or similar wording is a performance goal, not a separate campaign objective. Meta describes it as a way to show ads to people more likely to convert after sharing their contact information.

Earlier implementations associated conversion-lead optimisation mainly with Instant Forms. Meta’s current performance-goal documentation also lists qualified-lead optimisation for eligible website lead configurations. Availability can depend on the conversion location, account, data connection and current Ads Manager interface. Some combined conversion-location configurations do not offer all performance goals, so check the options shown in the relevant ad set rather than assuming that every Leads campaign is eligible.

For a broader comparison of the options, see our guide to Facebook lead optimisation for quality versus quantity.

Instant Forms and CRM Feedback

With Facebook Lead Ads, Meta controls the initial form interaction and supplies a lead identifier. Your CRM should retain that identifier when the lead is created. When the prospect later becomes qualified or purchases, the CRM integration can return the downstream status to Meta.

This produces a feedback loop:

Instant Forms can reduce friction and increase mobile conversion rate, but they are not automatically low quality. Higher-intent form settings, qualifying questions, clear advert copy and fast follow-up can improve results. CRM feedback addresses a different problem: it tells Meta what happened after submission.

Website Leads and CRM Feedback

For website leads, the initial event should be measured using the Pixel and website Conversions API where practical. Attribution identifiers and first-party customer data then need to survive the transition into the CRM.

A typical flow is:

Meta currently supports qualified-lead optimisation in eligible website configurations, but implementation requirements and availability must be checked in the account. Even when that performance goal is unavailable or unsuitable, CRM events remain valuable for reporting and manual budget decisions.

Calls and Other Conversion Locations

Telephone leads require particular care because the advertising click, telephone call, caller identity and CRM record must be connected reliably. Depending on the setup, this may involve Meta call reporting, a call-tracking platform, captured landing-page identifiers and CRM matching.

Do not assume that every call can be attributed merely because a salesperson later enters a telephone number in the CRM. The measurement design must establish how the original advertising interaction is retained and how consented customer data is sent.

Reporting and Optimisation Are Not the Same

Sending an event to Meta does not automatically mean that a campaign is optimising towards it.

There are three distinct uses of CRM data:

1. Measurement: determine which campaigns, ad sets and adverts generated later-stage outcomes.

2. Manual optimisation: compare cost per qualified lead, customer acquisition cost and revenue, then reallocate budget.

3. Automated optimisation: select an eligible performance goal that explicitly uses the chosen downstream event for delivery.

This distinction prevents a common implementation error: events appear in Events Manager, so the advertiser assumes Meta is bidding towards them. Unless the campaign is configured to optimise for the appropriate outcome, the data may improve reporting without changing the delivery goal.

Revenue reporting also does not automatically unlock value-based bidding for every Leads campaign. Meta’s value optimisation features depend on objective, conversion location, event eligibility, data volume and account availability. Send accurate values because they improve commercial reporting; only claim value optimisation when the relevant setting is actually available and selected.

How Meta Matches CRM Events to Advertising

Meta can only attribute an event when it can match the CRM record to a person and relevant advertising activity with sufficient confidence.

Useful identifiers may include:

• Meta Lead ID for Instant Form leads

• Email address

• Telephone number

• First and last name

• Town, postcode and country where appropriate

• Browser identifiers such as _fbp

• Click identifiers represented through _fbc or the underlying fbclid

• A stable external customer or contact ID

• Event time, source and source URL where relevant

The exact fields depend on the event source and integration. Personal data must be normalised and hashed where required by Meta’s specification. A reputable native or partner integration commonly handles this transformation, but the advertiser remains responsible for lawful collection and use.

Meta’s Event Match Quality indicates how effectively the customer information supplied with server events may support matching. It is a diagnostic indicator, not a guarantee of attribution or campaign performance. For offline datasets, Meta may also surface an offline data-quality score based on factors such as event coverage and data alignment.

Preserve Attribution at Lead Capture

Attribution cannot be reconstructed reliably after it has been discarded. For website leads, capture relevant source fields when the lead is created, not days later.

Useful CRM fields can include:

• Original source and latest source

• Landing-page URL and referrer

• UTM source, medium, campaign, content and term

• fbclid, _fbc and _fbp where technically and legally appropriate

• Meta campaign, ad set and advert identifiers when supplied by the integration

• Meta Lead ID for Instant Forms

• Initial conversion time

UTM parameters are excellent for CRM reporting, but UTMs alone are not a complete Meta identity-matching strategy. Likewise, fbclid can be useful, but customer information and first-party identifiers can strengthen matching where permitted.

Deduplicate Website Events Correctly

When the same website conversion is sent from both Pixel and Conversions API, use a shared event name and event ID according to Meta’s deduplication requirements. Otherwise, one lead may be counted twice.

Do not reuse the initial website lead’s event ID for a later qualified-lead or sale event. These are different business outcomes and should remain separate.

Ways to Connect Your CRM to Meta

The best integration is usually the simplest reliable native route that supports the required events and identifiers.

Native CRM Integration

Platforms such as HighLevel, HubSpot and Salesforce provide varying levels of Meta lead synchronisation and Conversions API functionality. Native support can reduce the number of credentials, mappings and failure points involved.

Before choosing it, verify that the integration supports both directions you need:

• Meta lead capture into the CRM

• CRM stage or lifecycle events back to Meta

These are separate capabilities. An integration that imports Instant Form leads is not necessarily capable of returning qualified-lead or revenue events.

Our Facebook Ads CRM integration guide compares the wider operational and tracking considerations.

Partner Integration

Meta supports partner-led Conversions API connections. These can provide a guided setup without requiring a fully bespoke build. Check which event sources, CRM stages, values and identifiers the partner actually supports rather than relying on a generic “CAPI enabled” label.

Zapier or Make

Automation platforms are useful when the CRM lacks a suitable native route or the data must be transformed before it reaches Meta. A workflow might trigger when an opportunity moves to Qualified Lead, format the customer and event data, then send a conversion event.

This adds flexibility but also creates another operational dependency. Monitor authentication, task failures, mapping changes, duplicate triggers and API responses. Our guide to Facebook Ads automation with Zapier covers common use cases.

Custom Conversions API Integration

A bespoke integration may be appropriate for proprietary CRMs, complex databases, high event volumes or unusual identity models. It offers maximum control but creates responsibility for API versioning, security, hashing, retries, deduplication, logging, monitoring and consent governance.

Manual Uploads

Meta still supports manual offline-event uploads. These can help with historic data, testing and low-frequency reconciliation. They are less suitable for an optimisation feedback loop because delayed or irregular uploads reduce freshness and introduce manual risk.

Step-by-Step Implementation Framework

The following process is more reliable than beginning with a connector and deciding what the events mean afterwards.

1. Map the Actual Customer Journey

Document where leads originate, how they enter the CRM, which stages they pass through, who updates them, how revenue is recorded and how long the sales cycle takes.

Include Meta Instant Forms, website forms, telephone calls, messages, appointments and imported leads. Identify where contacts can be duplicated or lose their source data.

2. Define the Primary Business Outcome

Choose the result that should guide commercial decisions. This may be qualified lead, attended appointment, sales opportunity, customer or revenue.

Write an operational definition. “Good lead” is too subjective. “Homeowner within our service area requesting an eligible project with an expected value above £X” is testable.

3. Audit CRM Data Discipline

Check whether salespeople update stages consistently, whether deals can move backwards, whether lost reasons are used, whether revenue includes VAT, and whether duplicate contacts are merged.

Automation cannot repair an ambiguous process. It will simply send ambiguity faster.

4. Select or Create the Correct Dataset

In Events Manager, identify the dataset that should receive CRM events and confirm its relationship with the correct business and ad account. Avoid creating unnecessary parallel datasets without understanding the existing Pixel and CAPI configuration.

5. Choose the Integration Route

Use this order of preference where it meets the requirements:

1. Suitable native CRM integration

2. Supported partner connection

3. No-code automation for a clear gap

4. Custom API integration for genuinely bespoke requirements

The cheapest connector is not necessarily the lowest-cost system if it requires regular manual repair.

6. Capture Matching and Attribution Data

For Instant Forms, preserve the Meta Lead ID. For website leads, store the relevant click, browser and customer identifiers. Standardise telephone numbers, country codes and email formatting before transmission.

Collect only data you are permitted to use and retain it for no longer than necessary.

7. Map CRM Stages to Meta Events

Map only real business milestones. Prevent multiple triggers when a record is edited without actually entering a new stage. Decide how reopened opportunities, cancellations, refunds and repeat purchases should be handled.

8. Send Test Events

Use Meta’s test and diagnostics facilities where supported. Confirm:

• The event reaches the intended dataset

• The event name and time are correct

• Currency and value are correctly formatted

• Customer information is normalised as required

• Source and action-source fields are accurate

• Event IDs are unique where they should be

• Website browser/server events deduplicate

• CRM progression events remain separate

9. Validate Matching and Coverage

Do not stop when one test event appears. Compare the number of eligible CRM records with the number of events received by Meta over a representative period.

For example, if 100 leads became qualified but Meta received only 62 Qualified Lead events, investigate trigger failures, missing identifiers, integration errors and exclusions.

10. Configure the Campaign Deliberately

Within the Leads objective, select the appropriate conversion location and review the performance goals actually available. If qualified-lead optimisation is eligible and the data is reliable, select the relevant option and dataset or event as required by the interface.

If there is insufficient volume or the CRM process is immature, begin with standard lead optimisation while collecting downstream events for measurement. A controlled transition is better than training delivery with inconsistent feedback.

11. Build a Sales-Funnel Report

Ads Manager should not be your only source of truth. Combine Meta spend and lead data with CRM outcomes.

Report at least:

• Leads

• Contact rate

• Qualified-lead rate

• Cost per qualified lead

• Appointment or opportunity rate

• Customer acquisition cost

• Revenue

• ROAS

• Average customer value

• Time from lead to qualification and sale

Segment by campaign, ad set, advert, offer, location and lead source where volume permits.

12. Monitor the Pipeline

Create alerts or routine checks for:

• Event volume falling unexpectedly

• Authentication expiring

• Dataset diagnostics

• Match or offline data quality declining

• Duplicate event spikes

• CRM stages no longer being updated

• Revenue arriving without currency

• Qualified events exceeding actual qualified CRM records

Tracking is an operational system, not a one-off installation.

How to Evaluate Performance Properly

Do not assess the system solely by whether reported Meta conversions increase. The business outcome is what matters.

Funnel Metrics

Use the following calculations:

• Contact rate: contacted leads ÷ total leads

• Qualification rate: qualified leads ÷ total leads

• Opportunity rate: sales opportunities ÷ total leads

• Close rate: customers ÷ total leads or customers ÷ qualified leads

• Cost per qualified lead: ad spend ÷ qualified leads

• Customer acquisition cost: ad spend ÷ customers

• ROAS: attributed revenue ÷ ad spend

These metrics reveal where performance changed. A higher cost per lead can still be beneficial if qualification and close rates improve enough.

Allow for Sales-Cycle Delay

Recent leads have had less time to qualify and purchase. Comparing yesterday’s leads with last month’s mature cohort will understate recent conversion rates.

Use cohort reporting by lead-created date and allow an appropriate maturity window. If most sales close within 30 days, do not make final revenue judgements after three days.

Reconcile Meta and CRM Reporting

Meta and the CRM may not produce identical numbers because they answer different questions.

Differences can arise from:

• Attribution windows

• View-through attribution

• Cross-device matching

• Time-zone settings

• Event-time versus upload-time reporting

• Consent restrictions

• Unmatched events

• Duplicate contacts

• Different revenue definitions

Use Meta for platform-attributed campaign analysis and the CRM as the operational record of leads, deals and revenue. Reconcile the systems, but do not force artificial equality.

Common Problems and How to Fix Them

Events Arrive but Few Are Attributed

Likely causes include missing or poorly formatted customer identifiers, lost Meta Lead IDs, absent _fbc or _fbp values for website leads, incorrect event times, or the wrong dataset.

Improve identifier capture at the original conversion, normalise customer data and review Meta’s diagnostics. Do not invent identifiers after the fact.

Events Are Counted Twice

For website events, check browser/server deduplication. For CRM events, inspect whether several workflows trigger when the same record is saved or moves backwards and forwards between stages.

Use idempotent workflow logic and a unique event identifier. Record the time and status of transmission in the CRM where possible.

Meta Optimises for the Wrong Result

Confirm which performance goal and event the ad set actually uses. An event visible in Events Manager is not proof that it is the optimisation event.

Also examine whether “Qualified Lead” has drifted into a weak or inconsistent stage. The algorithm cannot compensate for poor labels.

Qualified-Lead Volume Is Too Low

Consider optimising towards a slightly earlier but strongly correlated milestone, consolidating fragmented campaigns, improving lead volume, or using CRM outcomes for manual optimisation until the dataset matures.

Do not relabel unqualified leads simply to manufacture more conversions.

Revenue Is Misleading

Standardise whether value represents gross order value, revenue excluding VAT, gross profit, recurring annual value or collected cash. If different teams use different definitions, ROAS becomes unreliable.

Refunds, cancellations and repeat payments also need an agreed treatment. For long-term contracts, customer lifetime value can be useful for strategic analysis but should not be passed as though it were already collected revenue.

Privacy, Consent and Data Governance

Conversions API is not a way to avoid privacy obligations or consent requirements. Server-side collection is still data processing.

Advertisers should:

• Identify an appropriate lawful basis for collecting and using customer data

• Provide clear privacy information

• Respect applicable consent choices

• Configure cookie and tracking controls appropriately

• Limit data to what is necessary

• Protect access tokens and integration credentials

• Hash personal identifiers where Meta requires it

• Apply retention and deletion policies

• Avoid sending sensitive or prohibited information

• Review Meta’s Business Tools Terms and applicable UK data-protection requirements

Technical matching performance never overrides legal and ethical responsibilities. Obtain professional legal advice where the processing or data category creates uncertainty.

Best-Practice Checklist

• Use the Leads objective and distinguish it from conversion location and performance goal.

• Treat qualified leads as a defined commercial milestone, not a subjective label.

• Retain Meta Lead ID for Instant Forms and appropriate attribution fields for website leads.

• Use Pixel and website Conversions API together where suitable, with correct deduplication.

• Send CRM milestones as separate downstream events rather than duplicates of the initial lead.

• Prefer a suitable native CRM integration before adding middleware.

• Return events quickly and automatically where possible.

• Choose an optimisation stage that balances value, volume and speed.

• Verify the qualified-lead performance goal shown in the actual account and conversion location.

• Do not assume that an uploaded event is automatically used for bidding.

• Send accurate revenue for measurement, but do not assume every Leads campaign supports value optimisation.

• Compare received events with CRM source records, not just a successful test.

• Monitor event quality, coverage, failures and stage discipline continuously.

• Evaluate campaigns using cost per qualified lead, acquisition cost and revenue—not cost per lead alone.

Frequently Asked Questions

Is Facebook Offline Conversion Tracking the Same as Conversions API?

No. Offline conversion tracking describes the business use case: returning outcomes such as qualified leads and offline sales. Conversions API is a principal technical method for sending those events to Meta. Manual uploads and some partner integrations can also support offline data.

Do I Still Need the Meta Pixel?

For website activity, usually yes. Pixel supplies browser-side context while Conversions API can provide server-side events. A combined implementation can improve resilience and matching, provided duplicate events are deduplicated correctly.

Can Meta Optimise for Qualified Leads From Website Forms?

Meta’s current documentation lists qualified-lead optimisation for eligible website lead configurations as well as Instant Forms. Availability and setup requirements can vary by account and conversion location. Check the performance goals displayed in the relevant ad set and ensure that CRM events are connected correctly.

Is a Meta Dataset the Same as a Pixel?

Not exactly. A dataset is a broader event-data container in Events Manager and can receive data from several sources. Existing web datasets may retain a Pixel ID, which is why the terms can appear together in the interface.

Can I Upload Offline Conversions Manually?

Yes. Manual uploads can be useful for tests, historic records and low-frequency activity. Automated CRM or partner integrations are generally better for timely optimisation and dependable ongoing reporting.

Which CRM Stage Should I Optimise Towards?

Use the deepest stage that is consistently defined, occurs with adequate frequency and returns within a useful timeframe. For many service companies, Qualified Lead or Attended Appointment is a more practical initial signal than Closed-Won. Continue sending later sales and revenue events for reporting.

Will CRM Events Automatically Improve Lead Quality?

No. The data must be accurate, matchable and frequent enough, and the campaign must use an eligible quality-focused performance goal. Creative, offer, landing page, form design, audience, follow-up speed and sales process still affect lead quality.

Should I Create Audiences From CRM Data as Well?

First-party CRM segments can support customer exclusions, re-engagement and lookalike strategies where permitted and appropriately configured. This is separate from sending conversion events. Review the use case, permissions and audience size before assuming the same data should be used for targeting. Our Facebook Ads targeting guide explains the wider audience strategy.

Final Thoughts

The purpose of Facebook Ads offline conversion tracking is not to make Ads Manager contain more events. It is to give advertising decisions a better definition of success.

For lead-generation businesses, the initial enquiry is only the beginning of the commercial journey. A reliable CRM feedback loop connects the advert to qualification, opportunity, customer and revenue. It enables management to compare campaigns using meaningful business outcomes and, in eligible configurations, gives Meta better information for qualified-lead optimisation.

The strongest implementation combines accurate website or Instant Form tracking, disciplined CRM stages, preserved identifiers, a dependable Conversions API connection and routine data-quality monitoring. When these foundations are in place, Meta advertising can be managed as a revenue system rather than a form-submission system.

If you need help auditing or implementing Meta Pixel, Conversions API, CRM events and qualified-lead tracking, learn more about our Facebook Ads management service or explore our latest Facebook Ads guides.