I am referring to this site https://developers.google.com/analytics/devguides/collection/ua/gtm/enhanced-ecommerce to send e-commerce data from the Google tag manager to the Google analytics dashboard.
Below is the GTM tag for the order-receipt page. While other checkout operations are kept in separate tags.
I am trying to send the purchase event through custom HTML in GTM Tag:
<script>
ga('create', 'UA-random-id-12', 'auto', {'name': 'PurchasePage'});
ga('PurchasePage.require', 'ec');
ga('PurchasePage.set', 'dimension1', 'c4f0cab13b5537uid32yiu334f0354c18');
ga('PurchasePage.ec:addProduct', {
'id': '12345',
'name': 'App1',
'price': '10.0000000000',
'variant': '7364284628',
'quantity': 1,
'coupon': '',
'brand': 'EYUIYEI',
'currency': 'USD'
});
ga('PurchasePage.set', 'dimension2', 'ALL');
ga('PurchasePage.set', 'dimension3', 'Marketplace');
ga('PurchasePage.set', 'dimension4', true);
ga('PurchasePage.ec:setAction', 'purchase', {
'id': '12345', 'revenue': '110.0000000000', 'tax': '0.0000000000', 'coupon': null, 'step': 4,
});
ga('PurchasePage.ec:setAction', 'checkout', {
'step': 4
});
ga('PurchasePage.send', 'pageview', {
'title': 'Order Receipt Page'
});
</script>
I can see the debug logs on the chrome console where the purchase event is being sent
_ _ _ _
| | | | | | (_)
__ _ ___ ___ __ _| | ___ __ _ _ __ __ _| |_ _| |_ _ ___ ___
/ _` |/ _ \ / _ \ / _` | |/ _ \ / _` | '_ \ / _` | | | | | __| |/ __/ __|
| (_| | (_) | (_) | (_| | | __/ | (_| | | | | (_| | | |_| | |_| | (__\__ \
\__, |\___/ \___/ \__, |_|\___| \__,_|_| |_|\__,_|_|\__, |\__|_|\___|___/
__/ | __/ | __/ |
|___/ |___/ |___/
react_devtools_backend.js:4026 Running analytics_debug.js. This script is intended for testing and debugging only.
...
VM1232 analytics.js:30 Running command: ga("PurchasePage.require", "ec")
VM1232 analytics.js:30 Waiting on require of "ec" to be fulfilled.
VM1232 analytics.js:30 Executing Google Analytics commands.
VM1232 analytics.js:30 Running command: ga("PurchasePage.require", "ec")
VM1232 analytics.js:30 Waiting on require of "ec" to be fulfilled.
VM1232 analytics.js:30 Executing Google Analytics commands.
VM1232 analytics.js:30 Registered new plugin: ga(provide, "ec", Function)
VM1232 analytics.js:30 Running command: ga("PurchasePage.require", "ec")
VM1232 analytics.js:30 Plugin "ec" intialized on tracker "PurchasePage".
VM1232 analytics.js:30 Running command: ga("PurchasePage.set", "dimension1", "c4f0cab13b5537uid32yiu334f0354c18")
VM1232 analytics.js:30 Running command: ga("PurchasePage.ec:addProduct", {id: "310647", name: "App1", price: "10.0000000000", variant: "7364284628", quantity: 1, coupon: "", brand: "EYUIYEI", currency: "USD"})
VM1232 analytics.js:30 Running command: ga("PurchasePage.set", "dimension2", "ALL")
VM1232 analytics.js:30 Running command: ga("PurchasePage.set", "dimension3", "MP")
VM1232 analytics.js:30 Running command: ga("PurchasePage.set", "dimension4", true)
VM1232 analytics.js:30 Running command: ga("PurchasePage.ec:setAction", "purchase", {id: "6332d33fe8d5156c6bb6b68b", revenue: "110.0000000000", tax: "0.0000000000", coupon: null, step: 4})
VM1232 analytics.js:30 Running command: ga("PurchasePage.ec:setAction", "checkout", {step: 4})
VM1232 analytics.js:30 Running command: ga("PurchasePage.send", "pageview", {title: "Order Receipt Page"})
react_devtools_backend.js:4026 Tag Assistant debug signal detected for unsupported legacy tag.
...
VM1232 analytics.js:30 Setting throttling cookie: "_gat_OrderReceiptPage"
VM1232 analytics.js:30
Sent beacon:
v=1&_v=j97d&a=2039992036&t=pageview&_s=1&dl=https%3A%2F%2Ftestqwerty.qaz.com%2Freceipt%2F001965%3ForderUuid%3D12345%26gtm_debug%3D123&dr=https%3A%2F%2Ftagassistant.google.com%2F&ul=en-gb&de=UTF-8&dt=Order%20Receipt%20Page&sd=30-bit&sr=1792x1120&vp=1792x373&je=0&_u=yCCAAUIJAAAAAC~&jid=1383585562&gjid=1942449811&cid=296136795.1634033045&tid=UA-randomid-8&_gid=376555535.1664271026&_r=1&cd1=c4f0cab13b5537uid32yiu334f0354c18&cd2=ALL&cd3=MP&cd4=1&cos=4&pa=checkout&pr1id=12345&pr1nm=App1&pr1pr=10.0000000000&pr1va=7364284628&pr1qt=1&pr1cc=&pr1br=EYUIYEI&z=136380644
VM1232 analytics.js:30 _j1 (&jid) 1383585562
VM1232 analytics.js:30 _j2 (&gjid) 1942449811
VM1232 analytics.js:30 adSenseId (&a) 2039992036
VM1232 analytics.js:30 apiVersion (&v) 1
VM1232 analytics.js:30 clientId (&cid) 296136795.1634033045
VM1232 analytics.js:30 dimension1 (&cd1) c4f0cab13b5537uid32yiu334f0354c18
VM1232 analytics.js:30 dimension2 (&cd2) ALL
VM1232 analytics.js:30 dimension3 (&cd3) MP
VM1232 analytics.js:30 dimension4 (&cd4) 1
VM1232 analytics.js:30 ec:action (&pa) checkout
VM1232 analytics.js:30 ec:product "1" brand (&pr1br) EYUIYEI
VM1232 analytics.js:30 ec:product "1" coupon (&pr1cc)
VM1232 analytics.js:30 ec:product "1" id (&pr1id) 310647
VM1232 analytics.js:30 ec:product "1" name (&pr1nm) App1
VM1232 analytics.js:30 ec:product "1" price (&pr1pr) 10.0000000000
VM1232 analytics.js:30 ec:product "1" quantity (&pr1qt) 1
VM1232 analytics.js:30 ec:product "1" variant (&pr1va) 7364284628
VM1232 analytics.js:30 ec:step (&cos) 4
VM1232 analytics.js:30 encoding (&de) UTF-8
VM1232 analytics.js:30 hitType (&t) pageview
VM1232 analytics.js:30 javaEnabled (&je) 0
VM1232 analytics.js:30 language (&ul) en-gb
VM1232 analytics.js:30 location (&dl) https://testqwerty.qaz.com/receipt/001965?orderUuid=12345>m_debug=123
VM1232 analytics.js:30 referrer (&dr) https://tagassistant.google.com/
VM1232 analytics.js:30 screenColors (&sd) 30-bit
VM1232 analytics.js:30 screenResolution (&sr) 1792x1120
VM1232 analytics.js:30 title (&dt) Order Receipt Page
VM1232 analytics.js:30 trackingId (&tid) UA-randomid-8
VM1232 analytics.js:30 viewportSize (&vp) 1792x373
But on GA dashboard, the unique events are showing as blank.
After removing the PurchasePage.ec:setAction', 'checkout' from the script, I was able to see unique events on the analytics dashboard.
<script>
ga('create', 'UA-random-id-12', 'auto', {'name': 'PurchasePage'});
ga('PurchasePage.require', 'ec');
ga('PurchasePage.set', 'dimension1', 'c4f0cab13b5537uid32yiu334f0354c18');
ga('PurchasePage.ec:addProduct', {
'id': '12345',
'name': 'App1',
'price': '10.0000000000',
'variant': '7364284628',
'quantity': 1,
'coupon': '',
'brand': 'EYUIYEI',
'currency': 'USD'
});
ga('PurchasePage.set', 'dimension2', 'ALL');
ga('PurchasePage.set', 'dimension3', 'Marketplace');
ga('PurchasePage.set', 'dimension4', true);
ga('PurchasePage.ec:setAction', 'purchase', {
'id': '12345', 'revenue': '110.0000000000', 'tax': '0.0000000000', 'coupon': null, 'step': 4,
});
ga('PurchasePage.send', 'pageview', {
'title': 'Order Receipt Page'
});
</script>
I'm working on the observability part of Opensearch so I'm trying to collect the trace data of a wordpress website and send it to Opensearch.
I'm collecting the trace data using the wordpress plugin Decalog, this later sends the data to Jaeger agent, then from jaeger i'm sending the data to Opentelemetry and then to Data prepper and lastly to Opensearch.
Jaeger agent service in docker-compose :
jaeger-agent:
container_name: jaeger-agent
image: jaegertracing/jaeger-agent:latest
command: [ "--reporter.grpc.host-port=otel-collector:14250" ]
ports:
- "5775:5775/udp"
- "6831:6831/udp"
- "6832:6832/udp"
- "5778:5778/tcp"
networks:
- our-network
The "command" ligne got me this error : Err: connection error: desc = "transport: Error while dialing dial tcp: lookup otel-collector on 127.0.0.11:53: server misbehaving"","system":"grpc","grpc_log":true
So I changed otel-collector to the IP of the otel-collector container.
Otel collector and data prepper are installed using docker-compose.
data-prepper:
restart: unless-stopped
container_name: data-prepper
image: opensearchproject/data-prepper:latest
volumes:
- ./data-prepper/examples/trace_analytics_no_ssl.yml:/usr/share/data-prepper/pipelines.yaml
- ./data-prepper/examples/data-prepper-config.yaml:/usr/share/data-prepper/data-prepper-config.yaml
- ./data-prepper/examples/demo/root-ca.pem:/usr/share/data-prepper/root-ca.pem
ports:
- "21890:21890"
networks:
- our-network
depends_on:
- "opensearch"
otel-collector:
container_name: otel-collector
image: otel/opentelemetry-collector:0.54.0
command: [ "--config=/etc/otel-collector-config.yml" ]
working_dir: "/project"
volumes:
- ${PWD}/:/project
- ./otel-collector-config.yml:/etc/otel-collector-config.yml
- ./data-prepper/examples/demo/demo-data-prepper.crt:/etc/demo-data-prepper.crt
ports:
- "4317:4317"
depends_on:
- data-prepper
networks:
- our-network
The configuration of otel.yaml (to send data from opentelemetry to opensearch):
receivers:
jaeger:
protocols:
grpc:
exporters:
otlp/2:
endpoint: data-prepper:21890
tls:
insecure: true
insecure_skip_verify: true
logging:
service:
pipelines:
traces:
receivers: [jaeger]
exporters: [logging, otlp/2]
The configuration for data prepper pipeline : entry-pipeline:
delay: "100"
source:
otel_trace_source:
ssl: false
sink:
- pipeline:
name: "raw-pipeline"
- pipeline:
name: "service-map-pipeline"
raw-pipeline:
source:
pipeline:
name: "entry-pipeline"
prepper:
- otel_trace_raw_prepper:
sink:
- opensearch:
hosts: [ "http://localhost:9200" ]
cert: "/usr/share/data-prepper/root-ca.pem"
username: "admin"
password: "admin"
trace_analytics_raw: true
service-map-pipeline:
delay: "100"
source:
pipeline:
name: "entry-pipeline"
prepper:
- service_map_stateful:
sink:
- opensearch:
hosts: ["http://localhost:9200"]
cert: "/usr/share/data-prepper/root-ca.pem"
username: "admin"
password: "admin"
trace_analytics_service_map: true
As of now I'm getting the following errors:
Jaeger agent :
Err: connection error: desc = \"transport: Error while dialing dial tcp otel-collector-container-IP:14250: i/o timeout\"","system":"grpc","grpc_log":true}
Open telemetry collector :
2022-08-04T15:31:32.675Z info pipelines/pipelines.go:78 Exporter is starting... {"kind": "exporter", "data_type": "traces", "name": "logging"}
2022-08-04T15:31:32.675Z info pipelines/pipelines.go:82 Exporter started. {"kind": "exporter", "data_type": "traces", "name": "logging"}
2022-08-04T15:31:32.675Z info pipelines/pipelines.go:78 Exporter is starting... {"kind": "exporter", "data_type": "traces", "name": "otlp/2"}
2022-08-04T15:31:32.682Z info pipelines/pipelines.go:82 Exporter started. {"kind": "exporter", "data_type": "traces", "name": "otlp/2"}
2022-08-04T15:31:32.682Z info pipelines/pipelines.go:86 Starting processors...
2022-08-04T15:31:32.682Z info pipelines/pipelines.go:98 Starting receivers...
2022-08-04T15:31:32.682Z info pipelines/pipelines.go:102 Exporter is starting... {"kind": "receiver", "name": "jaeger", "pipeline": "traces"}
2022-08-04T15:31:32.683Z info static/strategy_store.go:203 No sampling strategies provided or URL is unavailable, using defaults {"kind": "receiver", "name": "jaeger", "pipeline": "traces"}
2022-08-04T15:31:32.683Z info pipelines/pipelines.go:106 Exporter started. {"kind": "receiver", "name": "jaeger", "pipeline": "traces"}
2022-08-04T15:31:32.683Z info service/collector.go:220 Starting otelcol... {"Version": "0.54.0", "NumCPU": 2}
2022-08-04T15:31:32.683Z info service/collector.go:128 Everything is ready. Begin running and processing data.
2022-08-04T15:31:32.684Z warn zapgrpc/zapgrpc.go:191 [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {
"Addr": "data-prepper:21890",
"ServerName": "data-prepper:21890",
"Attributes": null,
"BalancerAttributes": null,
"Type": 0,
"Metadata": null
}. Err: connection error: desc = "transport: Error while dialing dial tcp data-prepper-container-ip:21890: connect: connection refused" {"grpc_log": true}
Data prepper :
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.amazon.dataprepper.DataPrepper]: Constructor threw exception; nested exception is java.lang.RuntimeException: No valid pipeline is available for execution, exiting
Followed by this at the end :
WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance.
2022-08-04T15:23:22,803 [main] INFO com.amazon.dataprepper.parser.config.DataPrepperAppConfiguration - Command line args: /usr/share/data-prepper/pipelines.yaml,/usr/share/data-prepper/data-prepper-config.yaml
2022-08-04T15:23:22,806 [main] INFO com.amazon.dataprepper.parser.config.DataPrepperArgs - Using /usr/share/data-prepper/pipelines.yaml configuration file
Opensearch needs a separate tool to support ingestion of Opentelemetry data. It is called DataPrepper and is part of the Opensearch project. There is a nice getting started guide on how to set up trace analytics in Opensearch.
DataPrepper works similar as Fluentd or the Opentelemetry Collector, but has proper support for Opensearch as a data sink. It pre-processes trace data adequately for the Opensearch Dashboards UI tracing plugin. DataPrepper also supports the Opentelemetry metrics format.
Are you still having issues running Data Prepper? The configuration used in this example has been updated since the latest release, and should now be up to date and working (https://github.com/opensearch-project/data-prepper/blob/main/examples/trace_analytics_no_ssl.yml)
I was setting up Argo in my k8s cluster in Argo namespace.
I also Installed MinIO as an Artifact repository (https://github.com/argoproj/argo-workflows/blob/master/docs/configure-artifact-repository.md).
I am configuring a workflow which tries to access that Non-Default Artifact Repository as:
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
generateName: artifact-passing-
spec:
entrypoint: artifact-example
templates:
- name: artifact-example
steps:
- - name: generate-artifact
template: whalesay
- - name: consume-artifact
template: print-message
arguments:
artifacts:
# bind message to the hello-art artifact
# generated by the generate-artifact step
- name: message
from: "{{steps.generate-artifact.outputs.artifacts.hello-art}}"
- name: whalesay
container:
image: docker/whalesay:latest
command: [sh, -c]
args: ["cowsay hello world | tee /tmp/hello_world.txt"]
outputs:
artifacts:
# generate hello-art artifact from /tmp/hello_world.txt
# artifacts can be directories as well as files
- name: hello-art
path: /tmp/hello_world.txt
s3:
endpoint: argo-artifacts-minio.argo:9000
bucket: my-bucket
key: /my-output-artifact.tgz
accessKeySecret:
name: argo-artifacts-minio
key: accesskey
secretKeySecret:
name: argo-artifacts-minio
key: secretkey
- name: print-message
inputs:
artifacts:
# unpack the message input artifact
# and put it at /tmp/message
- name: message
path: /tmp/message
s3:
endpoint: argo-artifacts-minio.argo:9000
bucket: my-bucket
accessKeySecret:
name: argo-artifacts-minio
key: accesskey
secretKeySecret:
name: argo-artifacts-minio
key: secretkey
container:
image: alpine:latest
command: [sh, -c]
args: ["cat /tmp/message"]
I created the workflow in argo namespace by:
argo submit --watch artifact-passing-nondefault-new.yaml -n argo
But the workflow fails with an error:
STEP PODNAME DURATION MESSAGE
✖ artifact-passing-z9g64 child 'artifact-passing-z9g64-150231068' failed
└---⚠ generate-artifact artifact-passing-z9g64-150231068 12s failed to save outputs: Get https://argo-artifacts-minio.argo:9000/my-bucket/?location=: http: server gave HTTP response to HTTPS client
Can someone help me to solve this error?
Since the minio setup runs without TLS configured, the workflow should specify that it should connect to an insecure artifact repository.
Including a field insecure: true in the s3 definition section of the workflow solves the issue.
s3:
endpoint: argo-artifacts-minio.argo:9000
insecure: true
bucket: my-bucket
key: /my-output-artifact.tgz
accessKeySecret:
name: argo-artifacts-minio
key: accesskey
secretKeySecret:
name: argo-artifacts-minio
key: secretkey
I've been working with Symfony 2.7 and the RabbitMQBundle to handle some long processes asynchronously.
After facing the issue where the MySQL connection dies after a few minutes, I discovered rabbitmq-cli-consumer, a small app in Go that takes care of consuming the queue, and gives its content to a command.
In my case, I use it with this command: ./rabbitmq-cli-consumer -c configuration-stock.conf --include -V -e 'php app/console amqp:consume:stock --env=prod -vvv', with this configuration file:
[rabbitmq]
host = HOST
username = USERNAME
password = PASSWORD
vhost=/VHOST
port=PORT
queue=stock
compression=Off
[exchange]
name=exports
type=direct
durable=On
[queuesettings]
routingkey=stock
messagettl=10000
deadLetterExchange=exports.dl
deadLetterroutingkey=stock
priority=10
To handle errors, I intend to use RabbitMQ's x-dead-letter-exchange and x-dead-letter-routing-key configuration, to be able to retry the message later (in case something went temporarly wrong).
My issue is that, when I define my queues in RabbitMQBundle's configuration, rabbitmq-cli-consumer is unable to consume the queue, throwing this error:
2018/04/23 11:35:54 Connecting RabbitMQ...
2018/04/23 11:35:54 Connected.
2018/04/23 11:35:54 Opening channel...
2018/04/23 11:35:54 Done.
2018/04/23 11:35:54 Setting QoS...
2018/04/23 11:35:54 Succeeded setting QoS.
2018/04/23 11:35:54 Declaring queue "stock"...
2018/04/23 11:35:54 Registering consumer...
2018/04/23 11:35:54 failed to register a consumer: Exception (504) Reason: "channel/connection is not open"
Here is the configuration I use for RabbitMQBundle:
old_sound_rabbit_mq:
producers:
exports:
connection: default
exchange_options:
name: 'exports'
type: direct
exports_dl:
connection: default
exchange_options:
name: 'exports.dl'
type: direct
consumers:
stock_dead_letter:
connection: default
exchange_options:
name: exports.dl
type: direct
queue_options:
name: stock.dl
routing_keys:
- stock
arguments:
x-dead-letter-exchange: ['S', 'exports']
x-dead-letter-routing-key: ['S', 'stock']
x-message-ttl: ['I', 60000]
callback: amqp.consumers.exports.stock
multiple_consumers:
exports:
connection: default
exchange_options:
name: 'exports'
type: direct
queues:
stock:
name: stock
callback: amqp.consumers.exports.stock
routing_keys:
- stock
arguments:
x-dead-letter-exchange: ['S', 'exports.dl']
x-dead-letter-routing-key: ['S', 'stock']
Has anyone ever encountered something similar ? And how did you solve it ?
Since we added GA events to our webapp we lost bounce rate in our signup page. I found that adding "nonInteraction" key should make the trick but since I added it bounce rate is still 0.
Here it is what Analytic Debugger Add On, tell us what we are sending:
Download the React DevTools for a better development experience: http://fb.me/react-devtools
Download the React DevTools for a better development experience: http://fb.me/react-devtools
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check http://xhr.spec.whatwg.org/.
Initializing Google Analytics.
Running command: ga("create", "UA-45345323-1", "app.wizeline.com", {siteSpeedSampleRate: 100})
Creating new tracker: t0
Running command: ga("set", "forceSSL", true)
Running command: ga("send", "pageview", {page: "#/signup", title: "signup", nonInteraction: 1})
Setting throttling cookie: "_gat"
Sent beacon:
v=1&_v=j36d&a=1180036341&t=pageview&ni=1&_s=1&dl=https%3A%2F%2Fapp.wizeline.com%2F&dp=%23%2Fsignup&ul=en-us&de=UTF-8&dt=signup&sd=24-bit&sr=1920x1080&vp=1920x502&je=1&fl=17.0%20r0&_u=QAEAAQABI~&jid=552286626&cid=1169363107.1416505139&tid=UA-45345323-1&_r=1&z=1165069347
_j1 (&jid) 552286626
adSenseId (&a) 1180036341
apiVersion (&v) 1
clientId (&cid) 1169363107.1416505139
encoding (&de) UTF-8
flashVersion (&fl) 17.0 r0
hitType (&t) pageview
javaEnabled (&je) 1
language (&ul) en-us
location (&dl) https://app.wizeline.com/
nonInteraction (&ni) 1
page (&dp) #/signup
screenColors (&sd) 24-bit
screenResolution (&sr) 1920x1080
title (&dt) signup
trackingId (&tid) UA-45345323-1
viewportSize (&vp) 1920x502
Running command: ga("send", "event", "signup", "view", "form_viewed", {nonInteraction: 1}, undefined)
Sent beacon:
v=1&_v=j36d&a=1180036341&t=event&ni=1&_s=2&dl=https%3A%2F%2Fapp.wizeline.com%2F&ul=en-us&de=UTF-8&dt=Wizeline&sd=24-bit&sr=1920x1080&vp=1920x502&je=1&fl=17.0%20r0&ec=signup&ea=view&el=form_viewed&_u=QAEAAQABI~&jid=&cid=1169363107.1416505139&tid=UA-45345323-1&z=2130626078
_j1 (&jid)
adSenseId (&a) 1180036341
apiVersion (&v) 1
clientId (&cid) 1169363107.1416505139
encoding (&de) UTF-8
eventAction (&ea) view
eventCategory (&ec) signup
eventLabel (&el) form_viewed
flashVersion (&fl) 17.0 r0
hitType (&t) event
javaEnabled (&je) 1
language (&ul) en-us
location (&dl) https://app.wizeline.com/
nonInteraction (&ni) 1
screenColors (&sd) 24-bit
screenResolution (&sr) 1920x1080
title (&dt) Wizeline
trackingId (&tid) UA-45345323-1
viewportSize (&vp) 1920x502
Sent beacon:
v=1&_v=j36d&a=1180036341&t=timing&_s=3&dl=https%3A%2F%2Fapp.wizeline.com%2F&ul=en-us&de=UTF-8&dt=Wizeline&sd=24-bit&sr=1920x1080&vp=1920x502&je=1&fl=17.0%20r0&plt=6854&pdt=2&dns=0&rrt=508&srt=217&tcp=40&dit=5126&clt=5126&_u=QAEAAQABI~&jid=&cid=1169363107.1416505139&tid=UA-45345323-1&z=1698011418
_j1 (&jid)
adSenseId (&a) 1180036341
apiVersion (&v) 1
clientId (&cid) 1169363107.1416505139
encoding (&de) UTF-8
flashVersion (&fl) 17.0 r0
hitType (&t) timing
javaEnabled (&je) 1
l1 (&plt) 6854
l2 (&pdt) 2
l3 (&dns) 0
l4 (&rrt) 508
l5 (&srt) 217
l6 (&tcp) 40
l7 (&dit) 5126
l8 (&clt) 5126
language (&ul) en-us
location (&dl) https://app.wizeline.com/
screenColors (&sd) 24-bit
screenResolution (&sr) 1920x1080
title (&dt) Wizeline
trackingId (&tid) UA-45345323-1
viewportSize (&vp) 1920x502
Inspectlet: fatal error: wid has not been set.
It shows both "nonInteraction" keys but again it does not let our bounce rate to increase from 0.
Any idea/misreading/wrong syntax I'm doing?
Thanks!