Leads do not stay in Facebook
A lead-form lead goes into the CRM board, and a WhatsApp conversation opened from a click-to-WhatsApp ad is marked with the ad it came from. From there you continue with a call, WhatsApp or an automation.
To the CRM →Connect your Meta ad account and build a campaign, an ad set and an ad for Facebook and Instagram from inside Lynxbe. A lead from a Facebook lead form opens as a card on your CRM board, and a lead, call, booking or payment from a customer who came from an ad is sent to Meta as a conversion.
Everything runs on your own Meta ad account: what you build here also appears in Meta Ads Manager.
Pick an objective (awareness, traffic, engagement, leads or sales), set up an ad set with countries, ages and a daily or lifetime budget, and upload an image or video for the ad. You see a preview before it runs, then pause and activate from the same screen.
Say what you want (website visits, messages to your Page, engagement or reach), the daily budget, who to reach and the text and image. The system creates the campaign, ad set and ad paused, and if a step fails it removes what it already created.
Connect your Facebook Page, and every new lead from a lead form opens as a card on your CRM board with name, phone and source. The board automations run on it like on any new card.
Set a pixel and add the Lynxbe tracking snippet to your website. When a customer who came from an ad click leaves a lead, calls, books or pays, the event is sent to Meta as Lead, Contact, Schedule or Purchase, and the phone number is sent as a hash, not in plain text.
See the custom audiences that already exist in your ad account, create a lookalike audience from them by country at 1% to 20%, and keep saved audiences for reuse.
Spend, impressions, clicks, CTR, CPC and CPM for every campaign, with breakdowns. The numbers come from your Meta ad account.
Rules that pause or activate a campaign, ad set or ad by spend, clicks, CTR, CPC or CPM, run from the screen. The AI suggests pausing an ad set or ad, or changing a daily budget, and it happens only when you click to apply it.
Write one sentence about the business or the offer and get up to 5 versions of headline, text and button, in Hebrew or English. You can also create an image for the ad from a short description.
Build on the computer, check and answer leads from your phone
The Facebook ads screen is in the Lynxbe app on the web, iPhone and Android, and the CRM board that receives the leads is in the same app.
Experience a powerful interface designed for productivity on any screen
Lynxbe works with your ad account through the Meta API. Part of the work moves into the system, and part stays in Ads Manager.
A lead-form lead goes into the CRM board, and a WhatsApp conversation opened from a click-to-WhatsApp ad is marked with the ad it came from. From there you continue with a call, WhatsApp or an automation.
To the CRM →A lead, call, booking or payment from a customer who came from an ad is sent to the Conversions API, so Meta also sees what happened after the click, not only the click itself.
To Facebook and Instagram ads →A website-visitor audience, uploading a customer list, dynamic remarketing from catalog products, an ad set optimized for website conversions, and choosing placements and interests. You set these up in Meta Ads Manager.
Related modules: Facebook and Instagram ads in one screen · Google Ads campaigns from the system · TikTok Ads campaigns from the system · Marketing strategist with an approval queue · The CRM that receives the leads
The common ways to manage Facebook campaigns are directly in Meta Ads Manager, through an agency or freelancer, or in another ad management tool. The comparison is by type of tool, not by a specific tool; where it says "depends on the tool", check with the vendor.
| Topic | Meta Ads Manager directly | An agency or freelancer | Another ad management tool | Lynxbe |
|---|---|---|---|---|
| Building a campaign and an ad | Every Meta option | The agency builds it for you | Depends on the tool | 5 objectives, countries, age, budget, image or video; a quick ad in one form |
| Lead-form leads | Stored in Meta; download a file or connect a tool | Depends on the agreement | Depends on the tool | A card on the CRM board with name, phone and source |
| Conversions after the click (call, booking, payment) | Conversions API, set up yourself or through a partner | Depends on the agency | Depends on the tool | Sent from the CRM once a pixel and the website snippet are set |
| Audiences and remarketing | Every audience type, including website visitors and customer lists | Depends on the agency | Depends on the tool | Viewing audiences, lookalike and saved audiences; no website audience building and no list upload |
| Ad text | Meta AI tools | The agency copywriter | Depends on the tool | Up to 5 AI versions in Hebrew or English |
| Pausing ads and changing budget | You, or Meta automated rules | The agency | Depends on the tool | You; rules and AI recommendations run only when you trigger them |
| Google and TikTok | No, Meta only | Depends on the agency | Depends on the tool | Google Ads, TikTok Ads and Google Local Services Ads, each on its own screen |
Everything you need to know about this module
Book a demo and we will show you building an ad, a Facebook lead-form lead arriving in the CRM, and setting up conversions to the Conversions API.
Get the Lynxbe app
Review access, privacy, encryption, retention, and audit controls against your organisation's requirements. Certification or legal compliance is confirmed only with current independent evidence and legal review.
Define roles, permissions, sensitive-data scope, and approval paths, then verify them in a test environment before production access is granted.
Map access, correction, export, deletion, consent, and retention workflows to the legal requirements that apply to your organisation. Regulatory compliance depends on configuration and operating processes and requires legal review.
Confirm transport encryption, storage protection, backup handling, and secret management for the selected services during the security review.
Review account scoping, role boundaries, administrator access, and integration permissions against your security requirements before launch.
Review which user and configuration events are recorded, how long logs are retained, and which exports are available for the modules you select.
Define access, export, retention, and deletion requirements during implementation and verify the workflow for the modules and jurisdictions you use.
For more information, please review our App Privacy Policy, Privacy Choices, and Terms of Service.