Better/ More Granular Tracking

Hi Rich,

Unfortunately this is against the Terms of Service of Google Analytics and in Europe we think it’s also against GDPR.

To protect user privacy, Google policies mandate that no data be passed to Google that Google could use or recognize as personally identifiable information (PII). PII includes, but is not limited to, information such as email addresses, personal mobile numbers, and social security numbers. Because laws across countries and territories vary, and because Google Analytics can be used in many ways, consult an attorney if you are in doubt whether certain information might constitute PII or not.

Google interprets PII as information that could be used on its own to directly identify, contact, or precisely locate an individual. This includes:
? email addresses
? mailing addresses
? phone numbers
? precise locations (such as GPS coordinates – but see the note below)
? full names or usernames

Here is more information about that: Avoid sending PII to Google when collecting Analytics data & What Google considers PII.

This is the reason why we don’t offer the possibility to pass this data to Google Analytics.

Sorry if this doesn’t help you, but we don’t like to break the TOS of third party services.

Best regards from Spain.

• This reply was modified 6 years, 6 months ago by apasionados. Reason: Added formatting and goodbye message

You’re miss reading what I wrote.

I will simply just provide an example as I believe it will make far more sense.

The firm I work for has 20 Lawyers. Each Lawyer has their own contact form as the recipients differ form Lawyer to Lawyer. Now in the older itterations of CF7 I was able to use the ON sent OK and submit something which looked like this:

on_sent_ok: “ga( ‘send’, ‘event’, ‘Contact Form’, ‘submit’, ‘Contact Form-LawyerName’, ‘1’ );”

This then allowed me to track WHICH lawyer had the form submission and also allowed us as a firm to see groupings of our lawyers who were being contacted. Now fast forward to today.

The code I have added per your site is the following. Adding this to the bottom of functions.php:

	
//CF7 Forms & DOM

add_action( 'wp_footer', 'hgrgp_cf7_DOM_formtrack_footer' );
 
function hgrgp_cf7_DOM_formtrack_footer() {
?>
<script type="text/javascript">
document.addEventListener( 'wpcf7mailsent', function( event ) {
   
                 //Lawyer 1 Contact Form
    if ( '####' == event.detail.contactFormId ) {
        ga( 'send', 'event', 'Contact Form', 'submit', 'Lawyer1-Contact', '1' );
   }
	        //Lawyer 2 Contact Form
    elseif ( '####' == event.detail.contactFormId ) {
        ga( 'send', 'event', 'Contact Form', 'submit', 'Lawyer2-Contact', '1' );
   }
	        //Lawyer 3 Contact Form
    elseif ( '####' == event.detail.contactFormId ) {
        ga( 'send', 'event', 'Contact Form', 'submit', 'Lawyer 3-Contact', '1' );
   }
	 	//Lawyer 4 Contact Form
    elseif ( '####' == event.detail.contactFormId ) {
        ga( 'send', 'event', 'Contact Form', 'submit', 'Lawyer 4-Contact', '1' );
   }
}, false );
</script>
<?php
}

The ####’s above are the contact forms which correlate to each lawyer. Now when I go into my GA I do not see any detail past the Event Action. Everything else is showing as not set.

You will also note that what I am attempting here has ZERO GPDR implications as the information which is being passed along is internal and organizational data and is not attempting to track the submitter of the form.

Hi there,

In Google Analytics you should see the following data:

• Event Category: Contact form 7
• Event Action: sent
• Event Label: URL of the contact form

If you only have one contact form on each page, the URL gives you the information of which lawyer was contacted.

If you are using more than one contact form on each page, this plugin will not help you as it can’t track different contact forms on one page.

Maybe there is something we don’t understand, but this is the way it should work and works for us.

Best regards from Spain.

Apologies. This probably should be re-posted in the CF7 forum. Your response, while not what I was asking for, is appropriate as the DOM tracking plugin is limited to only the information you mentioned.