Announcement

**Dan - Glendale Designs** · 09-22-16, 07:31 AM

What method/variable was used with this integration to pass the revenue value?

**lesliekirk** · 09-22-16, 08:23 AM

Originally posted by Dan - Glendale Designs View Post

What method/variable was used with this integration to pass the revenue value?

The site was configured to use the Universal Enhanced Ecommerce analytics.js. Miva Support provided the most recent code for the Main Template (which as of today has made no difference).

The INVC Template has this in the <head> section:

Code:

<mvt:item name="ga_transaction" />
<script>
    ga('require', 'ecommerce');

    ga( 'ecommerce:addTransaction', {
        'id'            : '<mvt:eval expr="int( l.settings:ga_tracking:order_id )" />',
        'revenue'        : '<mvt:item name="ga_jsencode" param="ga_tracking:order_total" />',
        'affiliation'    : '<mvt:item name="ga_jsencode" param="store:name" />',
        'tax'            : '<mvt:item name="ga_jsencode" param="ga_tracking:total_tax" />',
        'shipping'        : '<mvt:item name="ga_jsencode" param="ga_tracking:total_ship" />'
    } );

    <mvt:foreach iterator="ga_orderitem" array="ga_tracking:orderitems">
    ga( 'ecommerce:addItem', {
        'id'        : '<mvt:eval expr="int( l.settings:ga_tracking:order_id )" />',
        'name'        : '<mvt:item name="ga_jsencode" param="ga_orderitem:name_unencoded" />',
        'price'        : '<mvt:item name="ga_jsencode" param="ga_orderitem:price" />',
        'sku'        : '<mvt:item name="ga_jsencode" param="ga_orderitem:code_unencoded" />',
        'category'    : '<mvt:item name="ga_jsencode" param="ga_orderitem:cancat_code_unencoded" />',
        'quantity'     : '<mvt:eval expr="l.settings:ga_orderitem:quantity" />'
    } );
    </mvt:foreach>

    ga( 'ecommerce:send' );
</script>

There is also a Google Conversion tag in the INVC Footer.

Did something change in version 9.00063 that broke this?

**Dan - Glendale Designs** · 09-22-16, 08:25 AM

Is the separate Adwords conversion tracking snippet in place?

**lesliekirk** · 09-22-16, 08:57 AM

Originally posted by Dan - Glendale Designs View Post

Is the separate Adwords conversion tracking snippet in place?

I'm assuming the you are referring to the googleadservices javascript and img pixel code? It's there too. None of the code was changed. The only thing that changed was the Miva update.

**Dan - Glendale Designs** · 09-22-16, 09:02 AM

I'm assuming the you are referring to the googleadservices javascript and img pixel code? It's there too. None of the code was changed. The only thing that changed was the Miva update.

Understand, what I am trying to figure out is if the Adwords Conversion Tracking snippet is using the Toolkit or some other method to pass the order subtotal, which may have failed with the upgrade. The fact that you stated revenue data is stilling pulling into Analytics, but not Adwords, makes me think it could be the Adwords Conversion tracking snippet, not Google Analytics/Enhanced Ecommerce.

**lesliekirk** · 09-22-16, 10:04 AM

No, there is no Toolkit/Toolbelt/Tool used. My apologizes, I am trying to get clarification from the person who handles the site's Google Analytics / Google AdWords. She's telling me it Google Analytics not AdWords. So I am confused (what else is new?).

**lesliekirk** · 09-22-16, 10:59 AM

I've managed to get a peek inside the GA account. What I'm seeing is a little different from what I have been trying to convey. In the Acquisition > Campaigns > Paid Keywords the Sessions almost completed dropped off to nothing. There are maybe 3 or 4 a day but it's a very visible dropoff. So I next went to Acquisition > AdWords > Campaigns and the Sessions have the same dropoff. I then went and looked at Acquisition > All Traffic > Channels and the Sessions didn't have the visible dropoff.

Is there something else in the GA admin I should look at to try and figure out where things are breaking down at?

**pbrynie** · 09-22-16, 12:50 PM

We don't send any parameters that affect how sessions or AdWords are tracked in GA, so I can't think of anything on our side that would have affected that. The only information I could find regarding session grouping was about conflicting campaigns.

https://support.google.com/analytics..._topic=1012046

**lesliekirk** · 09-22-16, 01:11 PM

Originally posted by pbrynie View Post

We don't send any parameters that affect how sessions or AdWords are tracked in GA, so I can't think of anything on our side that would have affected that. The only information I could find regarding session grouping was about conflicting campaigns.

https://support.google.com/analytics..._topic=1012046

So is it just coincidence that the numbers dropped off the day after I ran the Miva update? Nothing was changed in the Google Analytics settings. Nothing was changed in the store configuration. This used to work, so I don't think there is any sort of conflicting campaigns (unless there was some sort of change made at Google on the same day I ran the Miva update).

**lesliekirk** · 09-22-16, 01:51 PM

FYI - I am probably incorrectly pointing to the 9-00063 update as being to culprit - it could have been the 9-0006 update which does have some Google Analytics bug fixes in it:

22118: Module: mvga: mvga.mv: Google Analytics: Checkout options are no longer sent on OSEL submission
22119: Module: mvga: mvga.mv: Google Analytics: price fields inconsistently contained in quotes
22120: Module: mvga: mvga.mv: Google Analytics: never sends a transaction on INVC
22121: Module: mvga: mvga.mv: Incorrect product code being sent in AddToBasketSubmit call

I'm wondering if the code on the INVC page needs to be updated to work with the bug fix.

**pbrynie** · 09-23-16, 09:32 AM

You do need to apply the INVC template change noted in the 9.6 template change document as it was directly related to bug 22120: Google Analytics: never sends a transaction on INVC. This was a fix to a change made which suppressed the transaction from being sent in the case where there was a payment error on OPAY. This fix inadvertently suppressed all transaction calls due to a different system change we made where an exception is always generated on INVC for security purposes. If your Google Analytics Tracking Code template does not include the change below you will not see any final checkout transactions in GA.

Code:

<mvt:if expr="( g.UI_Exception NE 1 ) OR ( g.Session:cache:last_ui_exception EQ 'order_invoice' )">
ga( 'send', 'pageview', { 'page':'<mvt:item name="ga_jsencode" param="ga_tracking:url_override_unencoded" />' } );
</mvt:if>

**pbrynie** · 09-23-16, 09:34 AM

To be clear, the change I mentioned above is in regards to the Google Analytics Tracking Code template, not the actual INVC page template. It is near the bottom of the module template within the INVC if block.

**lesliekirk** · 09-23-16, 09:42 AM

Originally posted by pbrynie View Post

To be clear, the change I mentioned above is in regards to the Google Analytics Tracking Code template, not the actual INVC page template. It is near the bottom of the module template within the INVC if block.

Thanks, yes, I've already changed the Google Analytics Tracking Code template.

**lesliekirk** · 09-23-16, 09:49 AM

I'm wondering why this code was added to the INVC screen right after the <mvt:item name="ga_transaction" /> token (which is right after the <mvt:item name="hdft" param="global_footer" /> tag in the INVC page template:

Code:

<script>
    ga('require', 'ecommerce');

    ga( 'ecommerce:addTransaction', {
        'id'            : '<mvt:eval expr="int( l.settings:ga_tracking:order_id )" />',
        'revenue'        : '<mvt:item name="ga_jsencode" param="ga_tracking:order_total" />',
        'affiliation'    : '<mvt:item name="ga_jsencode" param="store:name" />',
        'tax'            : '<mvt:item name="ga_jsencode" param="ga_tracking:total_tax" />',
        'shipping'        : '<mvt:item name="ga_jsencode" param="ga_tracking:total_ship" />'
    } );

    <mvt:foreach iterator="ga_orderitem" array="ga_tracking:orderitems">
    ga( 'ecommerce:addItem', {
        'id'        : '<mvt:eval expr="int( l.settings:ga_tracking:order_id )" />',
        'name'        : '<mvt:item name="ga_jsencode" param="ga_orderitem:name_unencoded" />',
        'price'        : '<mvt:item name="ga_jsencode" param="ga_orderitem:price" />',
        'sku'        : '<mvt:item name="ga_jsencode" param="ga_orderitem:code_unencoded" />',
        'category'    : '<mvt:item name="ga_jsencode" param="ga_orderitem:cancat_code_unencoded" />',
        'quantity'     : '<mvt:eval expr="l.settings:ga_orderitem:quantity" />'
    } );
    </mvt:foreach>

    ga( 'ecommerce:send' );
</script>

Announcement

AdWords Revenue stopped after 9.00063 update

AdWords Revenue stopped after 9.00063 update

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment