---
# System prepended metadata

title: Untitled

---

Luis Berner's Issues regarding odoo

**SUMMARY**
* Login at odoo and access to specific companies
* Facebook Pixel
* Google's Pixel

***1. Login at odoo and access to specific companies***

Although I have a login and both Hedra's and N-1's workspaces are shown to me, when I try to change the company in the selector from EdLab to n-1 or to Hedra Matriz, a server error appears to me, telling me that "the selected company is not compatible with the companies of the related user(s)"

***2. Facebook Pixel***

1.1. I'm not sure about Hedra's, as we are inactive for a while, but n-1's pixel is not working properly and is still giving me inconsistent data:
* Initiated checkout is not coherent with the ammount of "add_to_chart" events
* We still have a small ammount of "missing events" being reported
* No "view content" event being reported
* No leads reported

2.2. Regarding Hedra's facebook pixel, still missing the parameters already reported to N-1's events

***3. Google Ads Pixel***

I had an interesting training call with Googles's support for marketing managers and we realized that only the Google Analytic Code will not be enougth.

The complete documentation for enganced ecommerce can be found at https://developers.google.com/analytics/devguides/collection/gtagjs/enhanced-ecommerce

The great news is that they have a perfect exemple of how they use the code that can be found at http://enhancedecommerce.appspot.com/
They give you 3 ways to write the code, but what we really need is to set up the gTag code (always the first option).

The only big issue is that this way the price of the products are fixed, and we'll need a dynamic pricing logic

The gTag for Hedra's website is the following:

<!-- Global site tag (gtag.js) - Google Ads: 1019919366 -->
<script async src="https://www.googletagmanager.com/gtag/js?id=AW-1019919366"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());

  gtag('config', 'AW-1019919366');
</script>



Finnally, we will need to set up two important events:

- offline conversions (gclid code)
- refund events (when a purchase is canceled by any reasons, as due to credit card denied or even a "boleto" expiration)

----> 1. The gclid code, that communicates an offline conversion, must be stored on the database. As soon as a purchase is confirmed, it must trigger a purchase confirmation that identifies this.

----> 2. This is an example of a refund event:

gtag('event', 'refund', {
  "transaction_id": "79.18502354114992",
  "affiliation": "Google online store",
  "value": 23.07,
  "currency": "BRL",
  "tax": 1.24,
  "shipping": 0,
  "items": [
    {
      "id": "P12345",
      "name": "Android Warhol T-Shirt",
      "list_name": "Search Results",
      "brand": "Google",
      "category": "Apparel/T-Shirts",
      "variant": "Black",
      "list_position": 1,
      "quantity": 2,
      "price": '2.0'
    },
    {
      "id": "P67890",
      "name": "Flame challenge TShirt",
      "list_name": "Search Results",
      "brand": "MyBrand",
      "category": "Apparel/T-Shirts",
      "variant": "Red",
      "list_position": 2,
      "quantity": 1,
      "price": '3.0'
    }

