Use your audiences in ads

The people who already know you are cheaper to reach and likelier to buy than strangers. Most businesses advertise to strangers anyway, because the list of people they know is sitting in a different tool. Mirroring closes that. You pick an audience you built in Hamla, and it appears in your Meta ad account as a Custom Audience. Then it keeps up: someone who joins the audience starts seeing your ads, someone who leaves stops.

​

What you need

• A connected Meta ads account. Mirroring refuses without one
• An audience worth mirroring. See Build audiences
• Contacts with an email or a phone number. Those are what Meta matches on

​

Turn it on

Open Contacts → Contacts Management → Segments, pick the audience, and enable the ad-audience mirror on it. Hamla creates the audience in your Meta account, uploads the current members with their details hashed, and from then on refreshes it every hour — sending only what changed.

​

Three things worth doing with it

​

Retarget people who already know you

Mirror your “gone quiet” or “browsed but did not buy” audience and run ads at exactly those people. Small audience, high intent, low spend.

​

Stop paying to advertise to customers

This is the one businesses forget, and it is free money. Mirror your existing customers audience and set it as an exclusion on your acquisition campaigns. You stop paying to introduce yourself to people who already bought.

​

Find more people like your best ones

A lookalike is the only thing here that reaches strangers. Meta takes your audience as a seed and finds people who resemble it — so the seed decides everything. Seed it with your best customers, not with everyone. And when the seed carries what each person spent, Meta weights the search by value: it stops looking for “more customers” and starts looking for “more customers like the ones who spent the most”. That only works if Hamla knows what people spent, which is what importing your history is for.

​

Whatever your business is

​

Two safety behaviours to expect

A sudden collapse gets stopped, not synced. If a run would change far more of the audience than a normal day ever does — a rule edited by accident, a custom field renamed — Hamla refuses the upload and flags it instead of emptying a live audience an ad set is spending against. You unblock it deliberately with Sync now. A broken rule freezes rather than empties. If the audience depends on a custom field that no longer exists, Hamla holds the last known membership rather than uploading nobody. It heals by itself when the field comes back. Both exist for the same reason: an ad audience that silently empties keeps spending money on nothing, and nobody notices for a week.

​

Check on it

How many people are in my customers segment, and is it growing?

Then look at the audience size in Meta. If Meta’s number is much lower than Hamla’s, that is match rate — not everyone’s email or phone is on a Meta account — and it is normal.

​

Related