• Hi, how can I fix the count per pixel event? For example, I have a contact form and I want to track how many people click submit. The pixel event tells me 420 have. However, I’ve only received 4 submissions.

    All the other events are miscounting the same amount: 420. I’m assuming all the standard events are getting activated by the same interaction on the website, rather than by they specific purspose (addtocart, checkout, etc).

    Can you please point me in the right direction to fix this? Thank you

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Antonino Scarfì

    (@antoscarface)

    Hi,

    how did you create the event? Could you share with a screenshot the event configuration? Are you referring the “CSS element” field to the exact selector of the submit button?

    Let me know more details about the event you are referring to, thanks.

    Thread Starter aimfulmedia

    (@aimfulmedia)

    Hi there,

    Here’s the screenshot: https://imgur.com/a/MSWdj

    What you are asking, I think I am missing some configuration. I should give some parameters so that it tracks properly, right? Can you please suggest what should that be? The website is https://www.anabaudone.com and I want to track how many people click on the button “contactame”

    Thank you

    Plugin Author Antonino Scarfì

    (@antoscarface)

    Hi,

    you should create the custom conversion event with “CSS Selector” in the “trigger on” option.

    In this way, you can specify what element should fire the pixel when a user clicks on it.

    To know how to refer to that element, open the inspector from your browser (see here how to: https://webmasters.stackexchange.com/questions/8525/how-do-i-open-the-javascript-console-in-different-browsers#answer-77337) and check for the html class or better ID. See this screen about your submit button: https://snag.gy/zvFsNg.jpg

    In your example, to refer to that button, you should use “#wpcf7-f6-o1 .submitbtn”. So, put this css selector in the custom conversion event configuration and when an user clicks in that button, the pixel will be fired. You can check it from Pixel Helper Chrome Extension.

    I hope is all clear.

    Thread Starter aimfulmedia

    (@aimfulmedia)

    Hi,

    Thank you for the instructions. I believe I followed them correctly. I have a few follow-up questions if you don’t mind.

    1. The hmtl class you suggested “#wpcf7-f6-o1 .submitbtn” has a # in front, yet in the inspector I didn’t see the #. Do I have to add the # every time I use a html class as a CSS Selector? I ask for future reference.

    2. I believe now the CompleteRegistration event is firing properly. Here is today’s test: https://imgur.com/a/UQDQr
    Here are the changes in the Caffeine Pixel dashboard: https://imgur.com/a/WdTZX

    However, AdvancedEvents is firing too, apparently matching CompleteRegistration. I don’t see AdvancedEvents in the Caffeine Pixel dashboard. How can I edit it/delete it?

    3. The CompleteRegistration event now registers when people click on the CTA button, but it fires when people click on it even if the contact form does not send (wrong information, errors, etc). Is there a way to be more accurate?

    Thread Starter aimfulmedia

    (@aimfulmedia)

    4. One more issue: https://imgur.com/a/i2HhQ The Pixel Helper is giving an warning error. How can I solve that?

    Thank you,

    Plugin Author Antonino Scarfì

    (@antoscarface)

    Hi,

    sorry for the late response.

    1. You should add # for the id="" reference, instead you use the dot . for class="" references. Examples:
    – if you see something like <div id="iamadiv">, you have to use #iamadiv.
    – if you see something like <div class="iamadiv">, you have to use .iamadiv.

    2. The AdvancedEvents is fired automatically by the plugin to add some extra information about the page you are. There isn’t any problem if it’s fired together other pixels. It just tracks other info useful when you create custom audience from the Pixel Caffeine amdin.

    3. It depends how the form is developed. After submit form, is there something we can append to know that the form is submitted without errors?

    4. That is an event fired automatically by Facebook, it’s not something managed by the plugin. It happens when you click twice or more into the button, because facebook detects that it is a button. I don’t know exactly because it’s a problem for Facebook, you can see further info here: https://developers.facebook.com/docs/facebook-pixel/pixel-helper#multiple-activations

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Pixel Events Misscouting’ is closed to new replies.