Skip to main content
Meta customer list Custom Audiences let you target ads on Facebook and Instagram to people from your own first-party data. The Cargo integration lets you create Custom Audiences, push contacts into them, remove contacts, and pull audience size and status, all from your workflows.

​
Authentication

Connect to Meta Ads with Facebook Login for Business.
Sign in as an admin of the business portfolio that owns your ad accounts, then pick the ad accounts Cargo can use. Cargo requests the ads_management, ads_read, and business_management permissions and stores a business system-user token that does not expire.
Each ad account must accept Meta’s Custom Audience terms before audiences can be created on it. If Create Audience fails with a terms error, accept them in Meta Ads Manager under Audiences.

​
Meta Ads actions

​
Create Audience

Create a new customer list Custom Audience on a Meta ad account. Configuration Returns The newly created audienceId, plus the name and the adAccountId.

​
Add Contact to Audience

Add a single contact to a Custom Audience. An email or phone number is required. The other fields improve the match rate. Configuration
Cargo normalizes and SHA-256 hashes every identifier before sending it to Meta, as the Custom Audience API requires. Send raw values, not pre-hashed ones.
Meta processes uploads asynchronously. Changes can take up to 24 hours to show in the audience.

​
Remove Contact from Audience

Remove a contact from a Custom Audience by email.

​
Create Report

Fetch the approximate size and status of a Custom Audience. Returns

​
Use cases

Sync engaged contacts (MQLs, trial signups, demo requests) into a Custom Audience and retarget them on Facebook and Instagram.
Keep a Custom Audience of your best customers in sync and use it as the source for a Lookalike Audience in Ads Manager.
Keep customers or unsubscribed contacts in an audience and exclude it from campaigns.

​
Limitations

  • One contact per action call: each Add Contact to Audience call uploads one row. Meta allows up to 10,000 rows per request, so very high-volume syncs may hit ad account rate limits.
  • Remove by the same identifier: removing by email only removes contacts whose hashed email matches.