Bricks Meta Events 0.9.1

Bricks Meta Events 0.9.1

• Shorter, plainer labels in the Meta tracking panel on Bricks forms, buttons and links: Event, Event name, Value, Sending and Customer details.
• Event options no longer all start with "They". For example, "They become a lead (Lead)" is now "Became a lead (Lead)".
• Empty dropdowns now show what will be used, such as Automatic, instead of Bricks' "Default".
• A form where no event has been picked now sends your Default form event from Settings, which is what the panel shows. It used to send Lead whatever that setting said.

Bricks Meta Events 0.9.0

Bricks Meta Events 0.9.0

• Works with Meta for WooCommerce as well as Meta pixel for WordPress. Either one will do, and Meta pixel for WordPress is no longer required.
• When both are switched on, Meta for WooCommerce is used, and the Status tab warns that page views are being counted twice.
• On Meta for WooCommerce, each conversion is sent straight to Meta and Meta's reply is recorded, so the conversions list shows whether Meta received it rather than only that it was handed over.
• The plugin's row on the Plugins screen now has a Settings link.
• Test mode now has its own on and off switch, and the test code stays saved when it's off, so you don't have to copy it from Events Manager again. If a code was saved before this update, test mode stays on until you turn it off.
• On the Testing tab, "Events Manager, Test Events" links straight to this pixel's Test Events.
• The settings screen is split into four tabs, Status, Conversions, Settings and Testing, and every check now leads with a one-word status such as Connected or Off. Labels and help text are shorter throughout.
• On Meta for WooCommerce, people who can manage WooCommerce are not tracked, the same as Meta for WooCommerce does for purchases. With test mode on, their form submissions are sent to Test Events from your site, so you can test while signed in.

Bricks Meta Events 0.8.4

Bricks Meta Events 0.8.4

• Renamed the two success results on the Diagnostics screen so they no longer read as the same news. "Accepted by Meta" is now "Received by Meta, confirmed", and "Sent in the background and confirmed on its way to Meta" is now "Sent in the background, not confirmed by Meta".
• Only the first of those means Meta acknowledged the conversion. The second means the handover ran and a send was attempted, which is all the background route can ever report.

Bricks Meta Events 0.8.3

Bricks Meta Events 0.8.3

• Shortened the plugin description on the Plugins screen, which repeated the "Requires: Meta pixel for WordPress" line WordPress already shows, and never mentioned that button and link clicks are covered too.
• Shortened the help text under How to send it on a form. It spelled out the four choices listed directly above it, so it now names only the two things worth knowing: redirecting forms are handled, and one enquiry is never counted twice.

Bricks Meta Events 0.8.2

Bricks Meta Events 0.8.2

• Corrected the help text under How to send it on a form. It said Automatic always sends from both your site and the visitor's browser, which is not what it does: it sends from your site alone when the form redirects, and from the browser alone when your site cannot reach Meta.

Bricks Meta Events 0.8.1

Bricks Meta Events 0.8.1

• While test mode is on, tracking now reports what it is doing in the browser console. A click leaves no record on the server, so this is the only way to tell a button that fired from one that quietly did not.
• It also says why nothing was sent, the usual reason being that you are signed in as staff, which Meta pixel for WordPress ignores. Clicks already counted during the same visit are reported too.

Bricks Meta Events 0.8.0

Bricks Meta Events 0.8.0

• Buttons and text links now have their own Meta tracking panel, so you choose exactly which ones count. Works on a link styled as a button and on a real button, including one with no link at all such as a popup trigger.
• A button or link you have set up yourself takes priority over the phone and email sweep, so a tracked phone link is counted once rather than twice.
• Clicks are counted once per button per visit.
• Updates now appear on the Plugins screen and install like any other plugin, instead of uploading a ZIP by hand.

Bricks Meta Events 0.7.0

Bricks Meta Events 0.7.0

• Added window.bmeTrack, for recording something the plugin cannot see for itself. It can be called straight from a Bricks Interaction with no code, using trigger click and action JavaScript (Function).
• Added an optional setting to count a click on a phone number or email address link as getting in touch. Clicks are counted once per link per visit. Off by default, because a click is not a confirmed enquiry and pointing your ads at unverified clicks makes them worse.
• Anything sent this way is browser only and carries no customer details.

Bricks Meta Events 0.6.0

Bricks Meta Events 0.6.0

• Added a Settings section, so a site with many forms does not need the same decision made on every one of them.
• Choose what most of your forms mean, and newly tracked forms start on it.
• Set a currency once, used whenever a form has a value but no currency of its own.
• Choose roles that should not be tracked, on top of the ones Meta pixel for WordPress already skips. Useful when you do not want existing customers counted as new enquiries.
• Added a switch to never send customer details from any form, for sites that are not allowed to.

Bricks Meta Events 0.5.1

Bricks Meta Events 0.5.1

• The Earlier conversions heading now appears as soon as you have sent one, and says that the list fills up from the second onwards. It used to be hidden entirely, which looked like the list was broken.
• The raw reply from Meta is now only shown when Meta refused a conversion, where it explains why. On a successful one the result line already says everything useful.