That’s a great suggestion! I’ve opened an issue on GitHub to track this feature.
@funsail This has been added in version 0.7.0 of the plugin.
Thanks. That is fantastic and so fast!
Can you consider splitting GA,FB into fields, so we can enter custom events with category
Eg I may have
ga(‘gaTracker.send’, ‘event’, ‘ContactForm’, ‘Send’);
or
ga(‘gaTracker.send’, ‘event’, ‘SupportForm’, ‘Send’);
For FB it’s more complex
fbq(‘track’, ‘Lead’, {content_name: ‘ContactForm’, content_category: ‘Cars’});
or
fbq(‘track’, ‘Lead’, {content_name: ‘ContactForm’, content_category: ‘Boats’});
or some people have more fields
Problem with FB there is only 1 pixel, if I use across 2 items or sites, I can’t tell where the click came from.
-
This reply was modified 7 years, 1 month ago by
funsail.
I guess if GA had the option name=‘ContactForm’
I think FB would be always ‘Lead’ so you just need a free field
payload=”{content_name: ‘ContactForm’, content_category: ‘Boats’}”
So it’s just 1 field each.
These are great suggestions, similar to what was mentioned in this support thread.
What are your thoughts on having a free-form input field with references to input field IDs that would be passed as event action in addition to the default submit/spam/fail events?
I’m not sure if it’s going to be too much work. You’d need at least 2 option sets
GA we can get away with just 1 form name
ga(‘gaTracker.send’, ‘event’, ‘ContactForm’, ‘Send’);
or
ga(‘gaTracker.send’, ‘event’, ‘SupportForm’, ‘Send’);
For FB it’s much more complex
fbq(‘track’, ‘Lead’, {content_name: ‘ContactForm’, content_category: ‘Cars’});
or
fbq(‘track’, ‘Lead’, {content_name: ‘ContactForm’, content_category: ‘Boats’, other_stuff});
I don’t even know what you’d do, other than to leave a free field for generic js.
I think the best way would have been a textfield for random js, and I’d just put in
ga(‘gaTracker.send’, ‘event’, ‘ContactForm’, ‘Send’);
fbq(‘track’, ‘Lead’, {content_name: ‘ContactForm’, content_category: ‘Cars’});
and also do other field manipulation if I want
