Event firing on page view instead of button click

  • Hey,

    I’ve setup an event called FBStartSurvey which I want to trigger when a button is clicked. Trigger is set on CSS selector #lp-pom-button-16

    Q1) when the page loads the event fires on page view, before I have a chance to click the button. Why is that happening?

    Q2) is it possible to make the event fire when EITHER the top button or the bottom buttons are clicked? #lp-pom-button-16 OR #lp-pom-button-58

    Thanks!

    The page I need help with: [log in to see the link]

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

    (@antoscarface)

    Hi,

    1) have you added the conversion event in “Conversions/Events” tab? I ask this, because I checked the source page of your website and I see that the event you mentioned is called manually at Pixel Initialization and not as conversion event from Pixel Caffeine. Check this screenshot: https://snag.gy/97FqDC.jpg. This is the reason why you see the event trigger immediately.

    2) You can, but you need to add two separated events, one for #lp-pom-button-16 and one for #lp-pom-button-58

    Thread Starter robncampbell

    (@robncampbell)

    Thanks for the reply.

    1) Yes I added FBStartSurvey in the Conversion/Events tab in pixel caffeine, as seen here: https://take.ms/0Pci8

    I had to manually implement the code on this page (https://thedancedojo.com/fb/are-you-ready/), because it’s a landing page built in Unbounce that’s placed on our domain. Pixel Caffeine’s implementation only fires the pixel on our wordpress pages, not pages built in Unbounce.

    Without manually adding the pixel code to that page, there was no pixel firing. What script should I add to that landing page, so that it only fires on CSS selector and not page view?

    Screenshot: https://take.ms/muKr4

    2) If I create a separate event for each button/css selector is it ok if it has the same name: FBStartSurvey? I.e. will it work properly?

    Plugin Author Antonino Scarfì

    (@antoscarface)

    1) I suggest you to not add any additional facebook pixel code, at least use directly the fbq( statement, instead of all code facebook gives you, in order to avoid double initialization. Then, I can’t see anymore that page, anyway try to check with Pixel Helper Chrome Extension if the pixel is fired properly when you click in that button. Make attention immediately after the click because you can’t notice it cause of the redirect. I checked the source and everything seem good.

    2) Yes, you can without any problem ??

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Event firing on page view instead of button click’ is closed to new replies.