How a configurator can connect with Meta Ads

Measurement and adsAssessed per project

Meta Ads is the advertising system behind Facebook and Instagram. It optimises campaigns on the events a website reports through the Meta Pixel, or a server through the Conversions API.

What a configuration could hand over

A social campaign learns from what you report to it. We can measure a submitted configuration as a separate Lead event and give it a value if agreed. Whether it goes through the pixel, from the server or both is decided by the consent the user has given.

  • Lead event

    Submitting a configuration could be reported to Meta as the standard Lead event, with value and currency where the configurator knows the price.

  • Conversions API

    The server can report the same event through the Conversions API, with action_source set to website and the URL of the page where the customer submitted the configuration.

  • Deduplication

    The pixel and the server would carry the same event_id and event name, so Meta does not count one enquiry twice.

  • Customer information

    With consent, the server can add an email or phone number hashed with SHA-256, which helps match the event to a Facebook or Instagram user.

What we need to connect it

  1. We need the pixel ID and Events Manager access with developer rights, where the Conversions API access token is generated.

  2. The token would belong to a system user in your business portfolio, not to a salesperson’s personal account.

  3. We check the events in Events Manager’s Test Events tool before you build campaigns on them.

  4. Reporting would follow the consent from your cookie banner; what may be reported without consent is your company’s call.

Worth deciding up front

  • Meta accepts a server event at most 7 days after it happened and otherwise rejects the whole request, which matters when reporting outcomes back from the CRM.
  • Customer email and phone may reach Meta only hashed, and the legal basis for doing so is your company’s decision.
  • If you also run a lead form directly on Facebook, decide which event is primary for campaign optimisation.

Questions about this connection

Why report the event from the server as well, when we have the pixel?

A browser pixel can be stopped by an extension or a declined consent, while the server does not depend on the browser. Meta requires deduplication when both routes run together, and whether that makes sense for your site is assessed during implementation.

If the Lead event carries a value from the price calculation, Ads Manager can show it with campaign results. Whether your account can also use it in value-based strategies depends on its settings and event volume, so we do not promise that in advance.

Other integrations

Put Meta Ads to work in your sales.

Tell us what you sell and how an enquiry is handled today. On the demo you will see the configurator, and we will go through which data could flow from it into your system.

treede is not an official partner or reseller of the systems named here. All names and marks belong to their owners. Integration options are verified during implementation against the system interface and version. Meta Ads official site