Skip to content

Blog · Integrations and data

Meta Andromeda: what changed in your ads and how to connect your conversions

What Meta Andromeda is, why 5 ideas beat 50 versions, and how to report each step of the sale to Meta and Google from WhatsApp and your CRM.

Equipo editorial de Meteor Published 5 min read

What is Meta Andromeda and what should I change in my click-to-WhatsApp ads?

Andromeda is the system Meta uses to choose which ads it can show each person. According to Meta, it lets many more candidates in per person and makes the selection more personal. For advertisers two things change. The first is creative: 50 versions of the same idea are one chance, and 5 different ideas are 5. The second is the signal: Meta looks for people who do what you set as the goal, so if your ads open WhatsApp and you only tell Meta who wrote, it brings people who write. To bring people who buy, each step of the sale (left their details, got qualified, asked for a quote, bought with its amount) has to go back to Meta and Google from your CRM.

This guide has three parts: a checklist to review your account, how to test each point today, and the step-by-step to connect it in Meteor.

What changed with Andromeda

Meta describes Andromeda as its ads retrieval engine: the stage that, out of all available ads, picks the candidates that are then ranked for each person (Engineering at Meta). With more capacity at that stage, more candidates get in and the selection is more personal.

For advertisers, that has two consequences:

  • Creative. Near-identical versions of an ad compete with each other for the same slot. Someone who scrolled past an idea tends to react the same way to a different hook. Different ideas reach different people.
  • Signal. To rank, Meta predicts who will do what you set as the goal. If the goal is “conversation started”, it brings people who write. Whether they buy or not, Meta does not know unless someone tells it.

The checklist

Whatever is left unchecked is what your ads are not telling the algorithm.

AreaWhat to review
The signalYou know which event each campaign optimizes for today, that event resembles a sale, and what happens inside the chat goes back to Meta.
The steps of the saleYou have defined when a contact left their details and when they are a qualified lead, with a rule your whole team applies the same way. You report the quote, the booking and the purchase when it really closes.
The valueEach purchase travels with its amount and currency, and the amount comes from your CRM, not from what someone typed in a chat.
AttributionYou store which ad each contact came from on their first message, you know how many days after the click you keep counting, and each event counts once per contact.
QualityYou send around 50 conversions per week and per ad set of the event you optimize for, and you review how many events are accepted and rejected.
CreativeEach ad is a different idea: problem, before and after, gift, comparison or testimonial. When one wins, you make variations of the concept, not of the hook.

How to test each point today

  1. The signal. Open your campaign and look at the optimization event. If it says messages or conversations and your business lives on sales, that is the leak.
  2. The steps of the sale. Write down what has to happen for a contact to be “qualified” in your business. If two people on your team define it differently, you do not have an event yet.
  3. The value. Look at your last ten reported purchases. If they are all worth the same or zero, the amount is missing. A purchase of 50,000 pesos and one of 5,000,000 pesos are not worth the same, but without an amount Meta counts them alike.
  4. Attribution. Go in through one of your own ads and write. Then check in your system whether that contact was tagged with the source ad. If it is not stored on the first message, it is lost.
  5. Quality. Count how many of last week’s purchases came from ads. Meta uses about 50 events per week in each ad set as a reference to learn (learning phase). If you have fewer, pick the earlier step that does reach it.
  6. Creative. Line up your active ads. If they look the same with the sound off, they are the same idea.

How to connect it in Meteor

In Meteor the WhatsApp conversation, the CRM and the conversion reporting live in the same account. That is why what happens in the chat can go back to Meta and Google without stitching tools together.

Before you start you need your WhatsApp connected to Meteor through the official API, Meta ads that open that WhatsApp, a dataset created in Meta’s Events Manager, and a user with the Administrator role in Meteor (or with the permission to manage conversions).

  1. Open the conversions screen. Ask your main Met to take you to conversion measurement. You will see a Meta card, a Google Ads card and, below, the events and the results. Nothing is reported until you turn on each connection.
  2. Connect Meta. Sign in, accept the permissions, confirm the active dataset is the one from your ad account and verify the connection.
  3. Complete the WhatsApp account. If the card says the WhatsApp account is missing, open the manual setup, enter the WhatsApp Business Account ID of your number and save.
  4. Run a test before turning it on. In Meta’s Events Manager, Test Events tab, copy the test code. In Meteor open the manual setup, paste it in the test event code field, save, and then send a test event. It should show up within seconds. The test needs at least one contact who arrived through one of your ads in recent days.
  5. Tell it which CRM stage is a sale. Fill in the stage field, the qualified lead status, the confirmed purchase status, the purchase value field and the currency (COP, USD, MXN). Write the statuses exactly as they are in your CRM. From then on, when a contact moves to the won stage, the purchase is reported on its own with its value. A purchase without an amount is not reported.
  6. Turn it on. Mark the connection as active and save. Once you finish testing, choose to remove the test event code and save again to switch to real events.
  7. Connect Google Ads (optional). Enter your account ID and connect it: it stays in validation mode, without reporting. Paste the ID of each conversion action you created in Google Ads, and when you are ready turn off validation mode and turn on reporting. An event without a configured action is not sent.
  8. Check the results. For the last 30 days you see accepted and rejected conversions, the acceptance rate and the reasons events were discarded.

Good to know

For Meta, only contacts who arrived through an ad count; nothing is attributed to someone who wrote on their own (Conversions API for Business Messaging). The window is 7 days by default, counted from the moment the contact writes through the ad, and each event counts once per contact. You pay for ads directly to Meta and Google: Meteor reports what happened in the conversation and in the CRM.

If you would rather not do it alone, write to us and we will connect it with you, with your ad account and your CRM.

The limits

What this article does NOT answer

We would rather say it here than leave you hunting for something that is not there.

Keep going

What this article mentions, in detail

The integrations, the Mets and the automations named above, each with its own page.

Where it comes from

Sources

Everything this article claims that we did not measure ourselves, with its origin.

Frequently asked

Questions on this topic

No. It is part of the infrastructure Meta uses to choose ads, and it applies to your account without any action. What you do decide is which ideas you give it to choose from and which event you ask it to optimize for.

As a reference, Meta points to around 50 optimization events per week in each ad set to leave the learning phase. If your purchases do not reach that number, optimize for an earlier step that does, such as qualified lead or quote, and keep reporting the purchase with its value.

Yes, and that is where it matters most. The first message from an ad that opens WhatsApp carries the data of the ad it came from. If you store it at that moment, the steps that happen later in the chat and the CRM can be reported to Meta attributed to that ad.

Left their details, showed real interest (qualified lead), asked for a quote, added to cart, purchased, booked and left a review. Following this guide, qualified lead and purchase are reported when the contact changes stage in the CRM, not when the Met assumes it.

Not to Meta. Only contacts who arrived through an ad count, within the attribution window (7 days by default from the moment the contact writes), and each event counts once per contact.

Keep reading

Other articles on the same thing

Want to see it running on your operation?

We show it with your own accounts connected, not with a canned demo.