Viewing 22 posts - 1 through 22 (of 22 total)
  • Author
    Posts
  • #943754

    Hello Enfold Community,

    Having problems getting Form Submission Event to fire through Google Tag Manager with Enrique Fold theme. Typically, there is a form id=”form-id” that I can specify in GTM, but I don’t see one clearly in the wholesale code that comes with the Avia form. Here’s the code:

    <form action=”https://mysite.com/&#8221; method=”post” class=”avia_ajax_form av-form-labels-visible avia-builder-el-41 el_after_av_hr avia-builder-el-last av-custom-form-color av-light-form ” data-avia-form-id=”1″ data-avia-redirect=””>

    I’ve tried adding class contains avia_ajax_form and that didn’t work either. Could you help me in specifying a clear form id in the above code.

    Any help in this matter would be greatly appreciated.
    Thank you!!

    #944435

    Hey hunter_ncmed,

    Thank you for using Enfold.

    How do you track the events? Please provide a screenshot of the tag options in your google manager panel.

    Docs: https://support.google.com/analytics/answer/6164470?hl=en

    Best regards,
    Ismael

    #945563

    The link to Google support is broken, but I set the event. The way I typically do it is dependent on the trigger which is set to Some forms > Form ID > Equals > Form Id Name (which is not clear and present in the Avia form).

    The Event is set up in GTM as the track type for Universal Analytics and is baked into the Tags available in GTM.

    Not sure how to send a screenshot through the forum here, so apologies for that.

    Thanks Ismael for any further assistance.

    #945770

    Hi,

    Thank you for the info.

    Edit the event and try to set the Trigger to “Clicks” and the condition variable to “DOM” element. Set it to “CSS selector” and use the “.avia_ajax_form” in the “Element Selector” field. Leave the second field empty. Enable the “Custom CSS Class” field from the Enfold > Layout Builder > “Show element options for developers” if you want to use a more specific css selector.

    Please use imgur or dropbox for the screenshots.

    Best regards,
    Ismael

    #946093
    This reply has been marked as private.
    #946401

    Hi,

    You can use imgur or dropbox. Just put the image url in the private field. Provide screenshots of the tag options and triggers. Please note that it takes a while before the changes in the google tag manager takes effect on the actual site. Are you creating additional conditions?

    Best regards,
    Ismael

    #949296

    Hello Ismael,
    Did you receive the Dropbox screen captures of GTM? Please advise and thanks!!

    #949345

    Hi,

    Where did you send it? Please add the link in the private field.

    Best regards,
    Ismael

    #949602

    Please find Dropbox links in private content links below. Thanks Ismael.

    • This reply was modified 6 years, 7 months ago by hunter_ncmed.
    #949955

    Hi,

    I don’t think that’s the correct dropbox url. You have use the share or the public url. Please try imgur.

    Best regards,
    Ismael

    #950216

    Please try the link below. Thanks and sorry for that. Don’t use Dropbox that much.

    #951274

    Hi,

    Thanks for the update. The configuration looks correct. However, you may want to adjust the css selector to target the “submit” button instead of the whole contact form container.

    .avia_ajax_form .button
    

    Best regards,
    Ismael

    #951802

    Hello Ismael,

    Tried 3 different trigger combinations with the .avia_ajax_form .button. I have attached the screenshots and added them to Dropbox. Ran 3 tests, couldn’t get the tag to fire in preview mode.

    #953050

    Hi,

    Did you try to publish an event just to test it? Please provide your mail account so that we could check the google tag manager console.

    Best regards,
    Ismael

    #953494

    The container is published. We have 4 tags and 3 fire when they’re supposed to. 2 All Pages, 1 Click To Call, and the Form – which doesn’t seem to fire in Preview more or the published container.

    Please send me an email and I will add you as a user in GTM.

    Thank you!!

    #954512

    Hi,

    I’m sorry but I can’t give you an email. Do you have an extra gmail account? Please provide that instead.

    Best regards,
    Ismael

    #954964

    Including Read permissions to extra Gmail account in private content.

    Thank you!!

    #955164

    Hi!

    Thanks for the update. I can’t get the preview button to display. I checked the site with the Tag Assistant chrome extension and it didn’t find any tags in the page even though the google tag manager snippet is there. Please provide the WP login details. We’ll disable the css and js compression and then try the preview again.

    Best regards,
    Ismael

    #955362

    Before I put in the page caching, all tags fired with the exception of the Forms Submit. Do you not see the tags firing for Google Analytics, JSON, and the Click to Call when in Preview mode? I do. Please see new screenshot added in Dropbox, link provided below.

    tags-fire-preview.PNG

    #956288

    Hi,

    I managed to take a look at the preview. The live or latest version is still using the old version of the “DOM Form Submit” variable and it only matches the selector “.avia_ajax_form” instead of the “.avia_ajax_form .button”. Somehow, using the account that you gave me, I can’t publish the changes to the live version. Please publish the latest version of the tags.

    // https://imgur.com/a/RjYcsL7

    Best regards,
    Ismael

    #957627

    The account is in preview mode only. We should be able to see the trigger fire, and see the event in Google Analytics in real time labeled as Form Submit – which doesn’t happen. I’m not sure where to go here. I’ve never experienced this problem before when a form has a clear form id=”form-1″.

    I really appreciate the thorough help on this Ismael, but not sure I should replace the form with a 3rd party form or not.

    #958479

    Hi,

    Yes, it’s in preview mode but the DOM Form Submit variable targets the form element instead of the button inside that form. The selector is still set to “.avia_ajax_form” instead of the “.avia_ajax_form .button” element.

    You should try it with the Contact Form 7 plugin. Let us know if it works.

    Best regards,
    Ismael

Viewing 22 posts - 1 through 22 (of 22 total)
  • You must be logged in to reply to this topic.