RJMetrics_Campaigns1.0.0.2stableASLcommunityCaptures visitor source information from the Google Analytics cookie and stores it to the Magento database.<p>Perform in-dept analysis on your referral sources and see which channels bring in the most valuable users. This tool captures visitor source information from the Google Analytics cookie and stores it to your Magento database.</p>
<p>Once you install the Acquisition Source Grabber, a set of new data fields will be available in your Magento database. Each of your new users will then have corresponding acquisition source data, and each new order will have corresponding referral source data. Essentially, you will be able to segment users and orders by GA referral sources (please also see this article on GA source data terminologies).</p>
<p><strong>Order Referral Source Data</strong></p>
<p>An order's referral source data corresponds to the web location that a user visited prior to a specific purchase. For example, the same user may have found your product via Google Search this time and an Advertisement the next time, so this value is specific to the purchase and may differ for a single user over time.</p>
<p>Orders have their corresponding referral data stored in the following data table and columns:</p>
<ul><li />`sales_flat_order`.`rjm_utm_source`
<li />`sales_flat_order`.`rjm_utm_medium`
<li />`sales_flat_order`.`rjm_utm_term`
<li />`sales_flat_order`.`rjm_utm_content`
<li />`sales_flat_order`.`rjm_utm_campaign`
</ul>
<p><strong>User Acquisition Source Data</strong></p>
<p>A user's acquisition source data corresponds to the web location from which the user visited your site the first time.</p>
<p>Users will have their corresponding acquisition source data stored in the `customer_entity_varchar`.`value` table and column. Since the `customer_entity_varchar` table is an EAV type table, a specific `customer_entity_varchar`.`attribute_id` is needed to identify a specific utm field.</p>
<p>You can find the exact `attribute_id` values in the `eav_attribute` table by running the following query, which returns the exact `attribute_id` and corresponding user acquisition utm field:</p>
<p>SELECT `attribute_id`, `attribute_code` FROM `eav_attribute` WHERE `attribute_code` like 'rjm_utm%'</p>
<p>Here are the five user acquisition utm fields (`attribute_code`) that you will find:</p>
<ul>
<li />`rjm_utm_source`
<li />`rjm_utm_medium`
<li />`rjm_utm_term`
<li />`rjm_utm_content`
<li />`rjm_utm_campaign`
</ul>
<p>For example, you may find that the `attribute_id` for `rjm_utm_source` may be a number such as 997. If that is the case, then you can query a user's corresponding acquisition utm_source with the following query which returns a user's utm_source and entity_id values:</p>
<p>SELECT cev.`value`, ce.`entity_id` FROM `customer_entity` ce JOIN `customer_entity_varchar` cev ON ce.`entity_id`=cev.`entity_id` WHERE `attribute_id`=997 LIMIT 100</p>Fixes issue where acquisition source was not updating.rjmetricsrjmetricsthandy@rjmetrics.com2013-08-055.1.06.0.0