For maximum page performance, all the Lime Light traffic attribution script code should be added to the BOTTOM of your traffic pages, before the closing </body> tag. If you view this page's source, you'll see the working examples of what is described here.
Copy and Paste the script below on all your offer pages
ga( 'create', 'UA-80325941-3', 'auto', 'limelightTracker' );// This is “UA-80325941-3” (not your own) - you are free to still have your own analytics tracking along with this.
ga( 'limelightTracker.set', 'dimension1', 'appkey' );// Your Lime Light subdomain here (appkey.limelightcrm.com)
ga( 'limelightTracker.set', 'dimension2', 'Campaign_ID' );// your Lime Light campaign ID here, this will be unique per LL campaign
ga( 'limelightTracker.send', 'pageview' );
UtmCookie = new UtmCookie();
document.write('utm_medium: ' + UtmCookie.utm_medium() + '<br>')
document.write('utm_source: ' + UtmCookie.utm_source() + '<br>')
document.write('utm_campaign: ' + UtmCookie.utm_campaign() + '<br>')
document.write('utm_term: ' + UtmCookie.utm_term() + '<br>')
document.write('utm_content: ' + UtmCookie.utm_content() + '<br>')
document.write('device_category: ' + UtmCookie.device_category() + '<br>')
Lime Light Traffic Attribution requires a small amount of work on front end traffic pages. A combination of using Google Analytics and passing in related fields into your NewOrder/NewOrderWithProspect/NewOrderCardOnFile API calls allows us to collect the data we need to provide analytics based reporting for your entire traffic funnel and match it with all the existing metrics found in our Analytics product. We will be able to fully segment your traffic by utm_source/utm_medium/deviceCategory using this method (and also further analyze by utm_campaign, utm_term, and utm_content if you so desire.
This is important for the 2nd part of the integration. Instantiating this on every page will automatically look for any google utm_ parameters on the URL and save them to a cookie for later use. You will need to pass this utm_ and device_category information into the Lime Light API calls for executing transactions. How you do this will be specific to your implementation of the Lime Light integration. Since the utm_source, utm_campaign, utm_medium, utm_term, utm_content, and device_category parameters need to be sent into the NewOrder, NewOrderCardOnFile, and/or NewOrderWithProspect API calls, you may need to post these 6 fields as hidden fields to your server side that is making the API calls (via the checkout page/form).
Below example is just an illustration of how to pull out the utm_ and device_category data out of the UtmCookie object in order to pass it into the Lime Light API call. You would likely have to embed these into your checkout form as hidden fields-->
Feel free to add utm_source, utm_campaign, utm_medium, utm_term, utm_content parameters to the URL string of this test page, and see how they get carried (and saved) into the UtmCookie object. This ensures in multi-step pages all the original landing page utm_ data is available later on. New API parameters