Shopify Checkout GA Cross Domain Tracking

Grovemade.com has a very odd setup using Shopify. We have our own frontend layer using the Shopify API to populate products, with the rest of the site fully in our control.

This is done by having nginx proxy all requests to our app *except* shopify URLs such as /cart, /checkout

We then use the JS API and proxy requests to Shopify with a few fake headers to allow Shopify to work this way.

The biggest problem thus far has been e-commerce tracking, as Shopify does not let us control the checkout pages. E-commerce data arrives, but is not associated to any visitor session.

 

Shopify has a decorator that sets a _shopify_ga cookie immediately upon direct checkout links or cart submissions being executed. The response from Shopify appends parameters that identify the session on the previous domain to the checkout.shopify.com URL.

If you host pages outside Shopify and want cross domain support for Google Analytics, replicate the linker decorator and add the GA linker string in a cookie called _shopify_ga on click for checkout links or carts.

Any action that ultimately takes you to checkout.myshopify.com should add the _shopify_ga cookie with google linker parameter.

Here’s the relevant function to use on your site.

In our case, we had to modify the form element being looked for to match our environment.

 window.addShopifyLinkerLinks = function() {
  ga('require', 'linker');
  function addListener(element, type, callback) {
    if (element.addEventListener) {
      element.addEventListener(type, callback);
    }
    else if (element.attachEvent) {
      element.attachEvent('on' + type, callback);
    }
  }
  function decorate(event) {
    event = event || window.event;
    var target = event.target || event.srcElement;
    if (target && (target.getAttribute('action') || target.getAttribute('href'))) {
      ga(function (tracker) {
        var linkerParam = tracker.get('linkerParam');
        var cookie = '_shopify_ga=' + linkerParam + '; ' + 'path=/';
        document.cookie = cookie;
      });
    }
  }
  for (var i=0; i < document.forms.length; i++) {
    var action = document.forms[i].getAttribute('action');
    if(action && action.indexOf('/cart') >= 0) {
      addListener(document.forms[i], 'submit', decorate);
    }
  }
  for (var i=0; i < document.links.length; i++) {
    var href = document.links[i].getAttribute('href');
    if(href && href.indexOf('/checkout') >= 0) {
      addListener(document.links[i], 'click', decorate);
    }
  }
}

Advertisements

Hubspot API undocumented “Options” format

HubSpot documentation ignores how to format the "Options" field in their API calls.

Their examples always leave it empty.

It returns an “Incorrect JSON format” error straight from Java if you try to pass an array of values.

The correct format is

[
{
u’description’:None,
u’value’:u’WALNUT & LEATHER iPHONE CASE’,
u’label’:u’WALNUT & LEATHER iPHONE CASE’,
u’readOnly’:None,
u’hidden’:False,
u’displayOrder’:-1,
u’doubleData’:None
}
]

I’m not sure what doubleData does.

Safari Flexbox Hidden Placeholder Bug

I’ve discovered a relatively difficult to reproduce bug with Safari and Placeholder text / blinky cursor not appearing upon input focus.

If you have flexbox elements that are hidden, then revealed later, the placeholder won’t render and no cursor will render.

Sublime Shortcut for Toggling Find/Search “In Selection”

Sublime has shortcuts for almost all of the common search operations.

Find in file.
Find and replace in file.
Find and or replace in entire project.
Use regex
Match case
Match whole words

In selection is a very common, and useful tool.

You can add it by adding this to your user key bindings. I picked super+alt+s, which follows the rest of the search hotkeys. It overrides the "save all files" command, but only when the search window is open.

Plus, I hardly use that command, and when I need to, I use the command pallete.

    { "keys": ["super+alt+s"], "command": "toggle_in_selection", "context":
      [
         { "key": "setting.is_widget", "operator": "equal", "operand": true }
      ]
   }

Get Instagram oAuth Token

This should be rather simple but there are no 3 step tutorials to do this. I’ve even done it multiple times in the past. Bullet points:

1: Register an application in instagram’s developer page. https://instagram.com/developer/clients/manage

2: Take the CLIENT ID from the newly created app.

3: Log into the instagram account of the client that you want access to

4: Visit the following URL, replacing client_id and redirect_uri with the ones you defined in your application. https://instagram.com/oauth/authorize/?client_id=*****************&redirect_uri=*************&response_type=token

5: Accept. NOTE: If you are using this to use a javascript / frontend / non serverside method of communicating with the API, ensure you add &scope=basic to the URL https://instagram.com/oauth/authorize/?client_id=*****************&redirect_uri=*************&response_type=code&scope=basic So that a publicly available key can’t be abused.

6: You will get your token in the redirect_url in the form of a hash (#<ACCESS_TOKEN>)

7: Profit

Removing Shopify Admin Bar

The admin bar keeps adding new tricks, like adding top: 40px to any fixed elements.

Try this:

<script>
try {
document.addEventListener("DOMContentLoaded", function(event) {
try {
var element = document.getElementById("admin_bar_iframe");
var html = document.getElementsByTagName("html")[0];
element.parentNode.removeChild(element);
html.style.paddingTop = "0"

} catch(ex) {}
})
} catch(ex) {};

function removeShopifyAdminBarHeights() {
$('[style="top: 40px;"]').css('top', '');
}
$(function() {
removeShopifyAdminBarHeights();
});
setTimeout(removeShopifyAdminBarHeights, 500);
</script>

Using Jinja from string with django 1.8 – undocumented

Django documents how to specify a template engine via

django.template.engines

But not what custom template engines are named.

You can specify a "NAME" parameter to your template configuration to reference it from django.template.engines.

template = engines['jinja'].from_string(template_code)