Automatic audience update for clients in Meta Ads

Budget: 3000 UAH Deadline: 3 days

Good day! I have done exactly such integrations — synchronizing CRM with Meta through the Marketing API. I am from BotCraft Group, we write our own code on our VPS.

Here’s how I see the implementation: once a day, the script pulls the latest orders from the CRM, retrieves the phone and email, removes duplicates, hashes in SHA-256 to the Meta format, and performs a full audience replacement via replace-session (customaudiences/{id}/users) — the audience ID remains the same, so exclusions in campaigns do not break. I implement protection strictly: if the CRM returns an empty or corrupted list — the replacement does not start, the old audience remains as it was.

Access needed: Business Manager with ads_management permission for this ad account, ID of the existing audience, and a method to retrieve orders from the CRM (API key or export — depending on what CRM you have).

Regarding your question: yes, a full daily replacement via API is possible, this is a standard scenario (replace users session). What should be considered in advance: Meta only accepts hashed data, the match rate depends on the quality of the numbers and emails, and there is a minimum size below which the audience cannot be used in exclusions — this is built into the logic.

I can do it with clean code (more reliable, without a monthly subscription to Make) or through Make — whichever is more convenient for you for further support.

Please clarify: what CRM do you have and do you already have access to the Meta Marketing API, or does it need to be set up from scratch?

Timeline — 2-3 days. I am taking a starting price of 3000 UAH: I am currently gathering initial reviews on Freelancehunt, so I am offering a good deal. I am ready to show live examples of my integrations.

Petro Pankov, BotCraft Group Expand

Budget: 3500 UAH Deadline: 3 days

Vladimir, good afternoon. Optimally: Make according to the schedule, and the Meta API replaces the existing audience's composition without changing the ID. I will normalize and deduplicate contacts; an empty set will not pass. Risks - token rights, limits, and data quality. I need CRM APIs, audience IDs, and Meta Business access. I will start today: in 1-2 hours after access, I will show the scheme and test. The final will be in 3 days.

Budget: 18000 UAH Deadline: 5 days

Evaluation - 18,000 UAH
Deadline - 4-5 working days, if the CRM has a normal API for the latest orders.

Full daily replacement of the existing Custom Audience with the current ID is possible through the Meta Marketing API - for this, there is usersreplace. I would do it through Make as a scheduler and orchestrator, and the actual work with Meta - through HTTP requests to the API. This reduces dependency on ready-made Make modules, which sometimes do not cover all Meta methods.

Meta limitations - up to 10,000 records per request, processing changes usually takes up to 24 hours, accepted Custom Audience Terms are required, ads_management permission, correct access to the ad account and Business. There is also a risk of blocking updates if the audience receives status 471 or Meta policies are triggered. For your volume of 400 orders, this is technically a small amount, but data quality checks are critical here.

Implementation - we take the latest orders from the CRM, normalize the phone and email, hash personal data in SHA-256, remove duplicates, check the minimum size and validity of the list, update the audience through usersreplace, and log the last successful update. If the CRM returns an empty or suspiciously small list - we do not touch the audience to avoid breaking the exceptions. Well, yes, this is the case where automation needs to be a bit paranoid =)

Access - CRM API or webhook with order fields, Meta Business with the ad account, audience ID, access to the Meta app or Meta system user, ads_management permission, confirmed Custom Audience terms, access to Make or a separate environment for the scheduler.

> Questions
>> Which CRM exactly and does it have an API for retrieving the latest 400 orders?
>> Is the audience created as a customer list from a file, or in another way?

Experience - worked with Meta API, Make, advertising events, audiences, CRM integrations, payments, and analytics. For similar tasks, I can show
> https://business.ingello.com/eva - marketplaces, accounting, product and advertising data
> https://business.ingello.com/vorfahr - data automation, SaaS, integrations, and payment logic
> https://business.ingello.com/forma-crm - CRM and working with client data

Main profile of Ingello for FLH - https://systems-fl.ingello.com/ua Expand

Budget: 4500 UAH Deadline: 3 days

Volodymyr, the main risk here is not in the replacement of the list itself, but in where this exclusion currently stands in the advertising cabinet. In 2026, Meta left only a few controls truly strict: location, age, language, and audience exclusion, if it is set in Audience Controls. If it somehow ended up in Suggestions (after switching to Advantage+, some old campaigns remain), Meta does not guarantee its adherence, and even a perfectly synchronized audience simply will not work as an exclusion.

Technically: Make pulls the latest orders from the CRM on schedule, I clean duplicates, format phone and email to Meta's format (SHA-256, E.164), and replace the composition of the existing Custom Audience without changing the ID through usersreplace. I will show a test run on a small sample before payment; an empty or suspiciously small list from the CRM halts the launch, and the old audience remains as is. A full daily replacement via API is possible, with limitations of up to 10,000 records per call and up to 24 hours for full processing on Meta's side. Access needed: CRM API or webhook for orders, Business Manager with ads_management, audience ID. 4500 UAH, the profile is new, the first feedback is now more important than the amount, 3 days after access. Have you already checked in which campaigns this exclusion currently stands - in Audience Controls or still in the old targeting variant?

Budget: 7000 UAH Deadline: 7 days

I will set up a daily scenario in Make: retrieving the latest orders from the CRM, normalizing phone numbers and emails, deduplication, and data quality checks before any changes. Then, through the Meta Marketing API, the scenario will update users in the existing Custom Audience without changing its ID and will send a report on the results. If the CRM returns an empty, too small, or incorrect list, the update will be halted—the current audience will remain unchanged.

Access to the CRM API, Business Manager, advertising account, and a system user or token with rights to manage Custom Audiences is required for this work. A complete daily replacement should be implemented carefully: the API has limitations on the volume and frequency of operations, so I will anticipate batch processing and an error log.

What is the approximate daily volume of new customers, and does the CRM already have stable API access?

Budget: 7500 UAH Deadline: 7 days

Good day. The task is clear: a daily job pulls the last 400 orders from the CRM, normalizes phone numbers and emails to the Meta format (SHA-256, country code, etc.), removes duplicates, and replaces users in the existing Custom Audience via the Marketing API, preserving its ID. Protection against an empty or incorrect list is mandatory to avoid accidentally deleting the audience.

I have 3.5 years of experience in full-stack development, building integrations between various services via API. In this project, I will implement the logic on the Make side (or a small script in TypeScript if Make does not cover a certain step). The scenario is approximately as follows: a scheduled trigger, an HTTP request to the CRM, data transformation, a conditional check for a minimum number of records, and only then a replace via the Marketing API. After setup, I will check that the audience is correctly processed in the exclusions of campaigns.

I am ready to discuss the details: which CRM, whether there are already Meta API tokens, and what to consider an "incorrect" list for protection.

Budget: 3400 UAH Deadline: 5 days

Experience with Meta Marketing API and Make.

The optimal option is the usersreplace endpoint, which replaces the entire list in one call, without intermediate audience clearing. This is important for exclusions; the audience will not be "empty" during the update.

Logic: Make pulls orders from CRM - normalizes phone/email - removes duplicates - hashes Meta - checks that the list is not empty and correct - only then sends to Meta via usersreplace. If the check fails, the update is skipped, and the old audience remains as is.

Access can be discussed in private messages.

Budget: 14000 UAH Deadline: 5 days

Good day, Volodymyr.

I see the task as a secure daily synchronization of the CRM with the existing Custom Audience without changing its ID. I will implement the retrieval of the last 400 orders, normalization of phone numbers and emails, removal of duplicates, and SHA-256 hashing before transferring data to Meta.

The optimal scheme is to use Make as a scheduler and control the scenario, while the audience replacement will be done through the Meta Marketing API. I will also add a check for the number and validity of records: if the CRM returns an empty, corrupted, or suspiciously small list, the update will not start. Additionally, I will set up a log for results and errors, a test run, and a check that this same audience remains in the campaign exclusions.

A complete replacement of the list while preserving the ID is possible. The main risks are Meta rights, token status, accepted conditions of Custom Audience, and audience processing delays.

I have over 6 years of experience with production API integrations, CRM, and background synchronizations. After the launch, I will provide a brief description of the logic and the accesses used. Which CRM is being used, and does it have a ready API?

Budget: 7500 UAH Deadline: 5 days

Hello, Volodymyr. I will set up a daily update of the existing Custom Audience without changing its ID and with protection against accidental clearing.

Scenario: we take the latest orders from the CRM, normalize the phone/email, remove duplicates, check the minimum volume and quality of the sample, after which we update the audience via the Meta API. An empty, abnormally small, or incorrect response from the CRM stops the launch and is logged. I will add retries for temporary errors, control the result, and check that the current exclusions in the campaigns continue to refer to this audience.

A complete replacement of the audience composition is technically possible, but before final implementation, I will check the actual rights to the asset/app, the current version of the API, and behavior on a test sample. After the launch, I will provide a brief logic scheme, a list of used accesses, and a verification instruction.

Read-only/API access to the CRM, the audience ID, and editing rights in Meta Business are needed. Which CRM is being used, and does it have an endpoint for orders with phone/email and a stable ID?

Cost — 7500 UAH, deadline — up to 5 working days, work through the Safe.

Budget: 5000 UAH Deadline: 3 days

When manually updating the audience, you risk missing fresh orders, causing buyers to enter the ads and spend the budget. Reliable automation with protection against empty lists is needed — I have already implemented this. Solution: 1. I connect to the CRM and daily extract the latest 400 orders with phone numbers/emails. 2. I clean duplicates, format according to Meta requirements (SHA256 hashes, delimiters). 3. 4. I have experience integrating with API parsing and automation (Allegro API -> CMS, GA4/GTM setup). Details: https://freelancehunt.com/showcase/work/razrabotka-parsera-sistemyi-avtomatizatsii-allegro/2039438.html What CRM is being used? Does it have

Price: 5000 UAH
Deadline: 3 days

Budget: 5000 UAH Deadline: 10 days

Ready to automate the daily replacement of Custom Audience considering protections to avoid accidental audience clearing and to maintain its current ID.

What I will do first: check access to the CRM and the current audience, run a test with a small sample, log the results, and implement a rollback mechanism in case of incorrect data.

Key technical detail: Meta requires a correct normalized format and SHA256 hashing of emails and phones, so normalization (E.164 for phones) and deduplication before hashing are critically important.

Full daily replacement via API is possible, but there are risks: short windows when the audience may be incomplete, and limitations on rate limits and request batch sizes; this can be minimized through checks, batches, and minimizing the number of operations.

Required accesses and permissions: access to the CRM API to read the latest orders, ID of the existing Custom Audience, Business Manager/Ad Account rights to edit audiences, and a token with ads_management and business_management permissions, as well as the ability to connect Meta in Make if you choose automation through it.

After setup, I will provide a brief description of the working logic, a list of provided and used accesses, and a short instruction on how to verify that the audience is correctly used in campaign exclusions.

I have experience working with the Meta Marketing API and setting up automations in Make for bulk uploads and updates of audiences.

Which CRM do you use, and can I get a test API key and the current ID of the Custom Audience for a quick check? Expand

Budget: 24000 UAH Deadline: 5 days

We have an almost ready scheme for such automation for CRM, advertising accounts, and daily audience updates; it can be quickly adapted to your CRM and launched via Make or directly through the Meta Marketing API.

Regarding timelines - approximately 4-5 working days.
Regarding cost - 24,000 UAH.

The optimal option is to use Make as a scheduler and control layer, while audience replacement should be done through the Meta Marketing API. For complete daily replacement, the endpoint usersreplace is needed - it allows removing current users from the existing Custom Audience and uploading a new prepared list without changing the audience ID.

What is included in the implementation:
- retrieving the latest orders from the CRM
- normalizing phone numbers and emails according to Meta requirements
- hashing data before sending
- removing duplicates
- minimum threshold for valid records
- protection against audience clearing in case of an empty or strange response from the CRM
- error log and synchronization results
- checking that the audience is still used in campaign exclusions
- a brief description of the logic of operation and used accesses after setup

Access requirements:
- access to the CRM or its API
- ID of the existing Custom Audience
- access to Meta Business Manager and advertising account
- token or system user from Meta with ads_management permission
- access to Make if we are doing the automation there

Regarding risks with Meta - complete replacement is possible, but there are nuances. Data must be correctly normalized and hashed. There may be delays in audience processing on Meta's side. Important application rights, token, and advertising account must not violate the rules of consent for using client data. For large volumes, API limits are important, but for 400 orders per day, this is usually a manageable volume.

I would like to clarify two points:
- which specific CRM is being used and whether it has an API for retrieving the latest orders
- is it better to access Meta through your existing application and system user, or should this be prepared from scratch

Relevant examples:
- https://business.ingello.com/prime-eva - accounting, integrations, production and product data
- https://business.ingello.com/eva - marketplaces, accounting, and data synchronization
- https://business.ingello.com/vorfahr - SaaS, automation, Stripe, AI, and working with business data

Our main profile for FLH:
https://systems-fl.ingello.com/ua

We can go through the accesses and choose a simpler implementation path here on the marketplace. I am available. Expand

Budget: 6700 UAH Deadline: 3 days

Hello Vladimir! I immediately see that the task of automating the update of Custom Audience through the Meta Marketing API and integrating with CRM for 400 orders daily is not just a technical hint, but an attempt to address a real business need: to maintain the effectiveness of advertising campaigns without manual work. I have worked with similar scenarios through Make when it was necessary to synchronize customer data with exclusions in Facebook Ads, so I know exactly what nuances can arise when dealing with duplicates and data formats.

My approach: first, I will set up a Make scenario that will receive the latest 400 orders from the CRM every day at 2 AM (via webhook or API, depending on your access), then I will use Google Sheets or the built-in Make module to clean the data, check emails/phones using regular expressions and uniqueness. The third step will be to send the list to Meta via the Marketing API, using the endpoint for updating Custom Audience ("/act_{ad_account_id}/customaudiences/{audience_id}"), after checking that the list is not empty. If the CRM does not return data, the script will simply not initiate the update. The price is $150, the deadline is 3 working days. I know that Meta sometimes blocks bulk updates due to limits of 10,000 records at a time, so I can suggest how to split the list or use an "automatic duplicate" in the audience to avoid errors.

Budget: 3600 UAH Deadline: 3 days

In essence: how many clients are currently in the audience and is there a ready endpoint in the CRM for retrieving the last 400 orders, or will the data need to be pulled directly from the database?

I would implement it through the Marketing API: hashing the phone/email in SHA256, converting to Meta format, deduplication, and replacing the audience composition by its ID through the Custom Audience Users API, with a check for an empty response from the CRM before replacement. I will connect Make as a trigger on a schedule and for intermediate data processing.

Full replacement daily is possible, there are limits on batch size and time for processing Meta hashes. Deadline: 3 days.

Budget: 3500 UAH Deadline: 4 days

Vladimir, you want to eliminate the manual upload of clients into Meta Ads by setting up a stable data flow from your CRM through Make. The key point here is to securely update the list without the risk of deleting the audience in case of failures during the export from the CRM.

I will implement a scenario where Make collects the data, validates it, and hashes it according to Meta's requirements (SHA256), after which it updates the Custom Audience via the API using the list replacement method. I will add a check on the number of records before sending to protect the audience from being cleared in case of an error on the CRM server side.

Please let me know which CRM is used for storing orders and if you have an active Business Manager with developer rights to create an app for API integration?