Hi @roshang , Trust you are well and this issue is resolved. While this
needs some investigation. A few reasons could be that an event fires
without a conversion variable, or the variable is not available or not
specified. Another scenario could be that the moment the event occurs
(revenue), the corresponding users had no tracking code.
Additionally, here is a document to help you guide how to decide on the
data model and structures based on attributes
Hope this helps.
Hi @Milan_Vucetic , Yes, you are correct. This recommendation probably
comes from best practices we follow while referring to temporary tables.
The recommendation is subject to how tables are structured, size of
tables, nature of workflows, number of personalization elements and
more. One of the reasons i suspect for this suggestion could be that
temporary tables could result in the size of the database increasing
significantly and eventually the size limit being reached therefore
slowing down t...
Hi, Thanks for the query. This is something we often see with reports.
While the exact nature of the campaign and the report may need some
investigation. But this is something we commonly see. The primary reason
is the way in which Visits and Page views are tracked. Page views counts
the number of times a page is viewed. Visits counts the number of
sessions for visitors. One visit consists of one or more page.