There is a lot to consider here when it comes to PII, even for a small
amount. In highly regulated industries such as government or banking,
even a tiny amount of PII can result in significant penalty from
regulatory bodies and auditors. You could "segment-out" the data, but it
is still there and on...
Hi @RashidJorvee , This is a loaded question but there are some things
to consider:Any logic in your tag manager which is dependent on
URL/DomainAny processing rules dependent on URL/DomainAny segments using
URLs or DomainsCookies which are set against the domain name....you get
the idea. If you're ...
the plugin getTimeBetweenEvents might be a good option (depending on
your needs). Take a look:
Hey @trochira , without knowing specifics about your implementation it
sounds like you're looking for Multi-Suite tagging. This is possible by
simply including both RSID's in your configuration. So for instance you
could send the dataset (same dataset) to an App-specific Report Suite
and to a Global...
The JS hosting shouldn't matter for this code since it effectively does
2 things:Checks for a valid desktop user agentAdds an event listener for
mouse movement which sets the bot variable to "false"Without knowing too
much on how you've implemented this, I might lean on this being a timing
Generally that is what happens with Launch already (without needing any
rules since Launch for AA works a bit differently in mobile vs web).
Essentially in your AA extension, you specify the report suites where
you want the data to be sent and in processing rules, you would see the
context data in y...
That is an absolutely fair statement. Tools have costs and it's
important to ensure we're getting the most value out of them. That being
said, personally, before onboarding any product, I prefer to get a
capabilities walkthrough (essentially the sales demo which demonstrates
all the capabilities of ...