fbpix

Catalog of server pixels for Facebook Conversion API. Allows creating a large number of pixels.

Hack settings interface

  • Default proxy. The standard proxy for sending postback requests, specified in the format proto://user:pass@host:port or host:port:user:pass. More about proxy formats is described on the page "Proxy formats".
  • Checkbox Add the item to the Tools menu. When enabled, the hack is accessed via the "Facebook Pixels" subsection of the "Tools" section; otherwise — via the "Flows" section (for webmasters) or "Traffic" (for agencies).

Working with the hack

Using the hack at the user level is done in the "Facebook pixels" subsection of the "Tools" / "Flows" / "Traffic" section. The hack can be used on behalf of a team only by its leaders via the "Gang" section.

Note. Each user (even an administrator) has their own personal page for working with pixels. When entering the subsection each person sees their own data. In team mode these are the team's shared pixels, not all personal pixels of team members.

To add a new pixel, click the "Add" button and fill out the form:

  • Pixel ID. Numeric identifier of the Facebook pixel.
  • Tag. The label in which the pixel ID will be searched (if the Value field is not set).
  • Value. An arbitrary value which, if present in the label chosen above, will trigger the pixel. DO NOT duplicate the pixel ID in this field.
  • Token. Facebook app token with access to send pixels.
  • Proxy server. Proxying of postback requests. Specified in the format proto://user:pass@host:port or host:port:user:pass. More about proxy formats is described on the page "Proxy formats".
  • New. The name of the event that will be sent with the pixel when a new lead arrives.
  • Hold. The name of the event that will be sent with the pixel when a lead moves to the Hold phase.
  • Approve. The name of the event that will be sent with the pixel when a lead moves to the Approve phase.
  • Checkbox Send hashed lead data. Enabled by default. If unchecked, lead data will not be sent.
  • Checkbox Generate click ID if none present in lead. Useful if for some reason the click is absent in the fbclid parameter.
  • Comment. Internal comment for convenience, does not affect operation.

After adding, the new pixel will appear in the list with the status "Not checked yet". When it fires, the status will be updated and will take one of the following values:

  • "Works normally" — everything is fine :)
  • "Incorrect access token" — an incorrect API token is being used.
  • "Network problems" — connection problems. Check your proxy if you are using one. Set a proxy if you are not using one.
  • "Invalid parameters" — any problems on Facebook's side.

Note. Pixel firings can be seen in the postback log.

Important! For correct operation you must pass the Facebook click identifier in the fbclid parameter. If this is not possible for some reason — generate it.

Example of a classic setup

  • Pixel ID: 1234567898765432
  • Tag: domain
  • Value: purrmeow.cat
  • Token: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.*********.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c
  • Proxy server: socks5://1.2.3.4:5678@purr:meow
  • New: Lead
  • Hold: InitialCheckout
  • Approve: Purchase
  • ✔️Send hashed lead data
  • ✔️Generate click ID if none present in lead