Skip to main content

How to put the code google remarketing


 View.phtml
Paste the below code on your product view template. You can find the file inside the catalog folder.
<?php $_product = Mage::registry("current_product");?>
<?php if ($_product && $_product->getId()): ?>
<script>
dataLayer.push({
"event": "fireRemarketingTag",
"google_tag_params": {
"ecomm_prodid’: "<?php echo $_product->getSku(); ?>",
"ecomm_pagetype’: "product",
"ecomm_totalvalue’: <?php echo $_product->getfinalprice(); ?>
}
});
</script>
<script type="text/javascript">






/* <![CDATA[ */






var google_conversion_id = XXXXXXXXXXX;






var google_custom_params = window.google_tag_params;






var google_remarketing_only = true;






/* ]]> */






</script>






<script type="text/javascript" src="//www.googleadservices.com/pagead/conversion.js">






</script>






<noscript>






<div style="display:inline;">






<img height="1" width="1" style="border-style:none;" alt="" src="//googleads.g.doubleclick.net/pagead/viewthroughconversion/XXXXXXX/?guid=ON&amp;script=0"/>






</div>






</noscript>
Cart.phtml
Paste the below code on your cart template. You can find the file inside the checkout folder.
<?php $items = Mage::getSingleton("checkout/session")->getQuote()->getAllItems();?>
<script>
dataLayer.push({
"event": "fireRemarketingTag",
"google_tag_params":
{
"ecomm_prodid": [<?php foreach ($items as $item) {?>"<?php echo $item->getSku();?>",<?php }?>],
"ecomm_pagetype": "cart",
"ecomm_totalvalue": [<?php foreach ($items as $item) {?><?php echo $item->getPrice(); ?>,<?php }?>]
}
});
</script>
 Success.phml
Paste the below code on your success template. You can find the file inside checkout folder.
<?php
$order = Mage::getModel("sales/order")->loadByIncrementId($this->getOrderId());
$items = $order->getAllItems();
$total = $order->getGrandTotal();
?>
<script>
dataLayer.push({
"event": "fireRemarketingTag",
"google_tag_params":
{
"ecomm_prodid": [<?php foreach ($items as $item) {?>'<?php echo $item->getSku();?>",<?php }?>],
"ecomm_pagetype": "purchase",
"ecomm_totalvalue": "<?php echo $total; ?>"
}
});
</script>

I did it the same way in my Magento installation and it works fine

Comments

Post a Comment

Popular posts from this blog

Magento 2 product collection Filtering multi-select attribute values

  If you have multi-select attribute of product like below If you want filter value for this option Use below syntax to get product data: ->addAttributeToFilter('store_model', array('finset' => $params['store_model'])) finset key is used for multiselect attribute filter. $objectManager = \Magento\Framework\App\ObjectManager::getInstance(); $products = $objectManager->get('Magento\Catalog\Model\Product')         ->getCollection()         ->addAttributeToSelect('*')         ->addAttributeToSelect('store_brand')         ->addAttributeToSelect('store_model')         ->addAttributeToSelect('store_year')         ->addAttributeToFilter('store_brand', array('finset' => $params['store_brand']))         ->addAttributeToFilter('store_model', array('finset' => $params['store_model']))         ->ad...
6 comments
Read more

What startSetup() and endSetup() methods actually does?

The startSetup() and endSetup() methods are used in setup scripts. They are often at the beginning and the end of an upgrade/install method, like in “upgrade()” method of Magento/Catalog/Setup/UpgradeData.php The question is “do you really need them?” Or does it just “look necessary”? This blog post explores what these functions do and then explains when you do and do not need to use these methods. Let’s see what these methods are doing. First, startSetup(): public function startSetup() {   $this->rawQuery("SET SQL_MODE=''");  $this->rawQuery("SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0");   $this->rawQuery("SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO'");   return $this;  } 1. Disable foreign keys check. It may be necessary in some rare cases (for example, in a case of cyclic references between tables), but it’s not needed in common situations. It even may lead to hiding real problems...
Post a Comment
Read more

magento 1 extension converted in to magento 2 process

Simple Install =================================== Download as a zip below link. unzip and upload it to your public_html or other rootdoc directory. https://github.com/magento/code-migration. login to your server via shell switch to the code-migration-develop directory by running following command   cd code-migration-develop Run command following command in root directory of this toolkit composer instal Before running the migration, the following directories need to be prepared: ===================================== * `<src>` - Directory that contains custom Magento 1.x code that is intended to be migrated. The code must follow the Magento 1.x directory structure.   Magento1.x core files must not be included. * `<dst>` - Empty directory for the toolkit to put the generated Magento 2 code to * `<m1>` - Directory that contains: * Vanilla Magento 1.x codebase, and * Custom Magento 1.x code same as...
11 comments
Read more