1. Integrations
  2. Meta Pixel

Meta Pixel integration: conversation results sent to your Meta pixel as events

Agenola's Meta Pixel integration sends what happens in a conversation (a ticket, an appointment, contact details, a purchase) to your Meta pixel from the server as events. Your Facebook and Instagram ads see the results the agent brings in and can be optimized for them. You connect it with your Meta business account; there's no code or key to copy.

How it works

When connecting, you choose your business and the pixels Agenola will use in Meta's window. Then you turn on Meta Pixel in each agent's Measurement settings tab, choose the pixel and tick the events to send: conversation started, contact details left, conversation completed, ticket created, appointment booked, product searched.

Events are sent from the server, not the visitor's browser, so ad blockers don't stop them. If the visitor came from your ad, the event is matched by the ad click; otherwise by their email, phone number and browser. If your WooCommerce or Shopify store is connected, an order placed within seven days of the conversation is also sent as a purchase event.

In a step's Tracking tab you can define one of Meta's standard events or your own. If you enter a test code on the "Send event" flow step, the event appears only in Events Manager's Test events tab.

  • Email and phone number go to Meta only as a hash that can't be reversed.
  • The connection belongs to your business, not a person: it keeps working even if the person who connected it leaves the business.
  • Don't turn off any permission in Meta's window: if one is turned off, Meta grants none. To use a pixel you add later, reconnect and select it too.
  • When you remove the connection, Agenola stays in your business's Connected apps list; you can remove it there.

What it does

This list is generated from the same source as the Meta Pixel page in the dashboard: if it isn't listed here, we don't do it with Meta Pixel. Flow steps live in the flow editor under Add step → Integrations → Meta Pixel.

EventAction · Flow step1
  • Send event

    Sends an event to the pixel you choose. If the visitor came from your ad it's matched by the click; otherwise by their email, phone and browser. Email and phone reach Meta only as a summary that can't be reversed.

Example conversations

A visitor from an Instagram ad leaves contact details

Visitor: Could you tell me the price of the pilates package I saw on Instagram?

Agent: The 8-class package is $180. Would you like to leave your contact details for a trial class?

Visitor: Yes, +1 415 555 0119

Agent: Thank you. The studio will call you to schedule your trial class.

Behind the scenes: When the visitor leaves their phone number, a "Contact details left" event goes to your Meta pixel. Because the visitor came from an ad, the event is matched by the ad click; the phone number goes only as a hash.

An order after the conversation counts as a purchase

Visitor: Do you have these shoes in a size 10?

Agent: Size 10 is in stock; if you order today, it ships tomorrow.

Visitor: Great, I'm placing the order.

Behind the scenes: When the visitor completes the order, a purchase event with the order value and currency goes to your Meta pixel; the order's email and phone number are added only as a hash.

Setup

Our app on the Meta Pixel side is currently going through approval. Until it is approved the connection is not open to everyone; once approved, the steps on this page apply as written.

  1. 1In Agenola, go to Integrations → Meta Pixel and press "Connect to Meta".
  2. 2In Meta's window, choose your business and the pixels Agenola will use, and approve; don't turn off any permission.
  3. 3In the agent's Measurement settings tab, turn on Meta Pixel, choose the pixel and tick the events to send.

Detailed setup: How do I connect analytics and ad platforms?

Permissions and where your data goes

  • Sent to Meta: the events you choose, with their names and parameters, ad click and browser details; the visitor's email and phone number only as a hash. For a purchase, the order value, currency, and the IP address and browser details of the browser that placed the order are sent too.
  • Read from Meta: your business's pixels, for choosing.
  • Permissions requested: reading ad data and managing business assets. The connection works through a system user created for Agenola in your business.
  • Connection details are stored encrypted on the server. Only the workspace owner and admins can connect or remove it. Informing your visitors and obtaining the consent required is your responsibility.

Related integrations

See all integrations

Frequently asked questions

Do I need to copy my pixel's code or an access key?

No. Choosing your business and the pixel in Meta's window is enough; you don't copy any code or key from Events Manager.

Are events blocked by ad blockers?

No. Events are sent to Meta from the server, not from the visitor's browser.

A pixel I just added isn't in the list. What should I do?

Reconnect to Meta and select that pixel in the window too. Agenola only has access to the pixels you select when connecting.

Try the Meta Pixel connection on your own account

Agenola and our partners use cookies to improve the site and show you relevant ads. We count which of our ads bring visitors without using your name or email; anything more only happens if you allow it. Privacy Policy(opens in a new tab)