Skip to content

Commit 0d64f56

Browse files
eshanrnhgitbook-bot
authored andcommitted
GITBOOK-52: Tom's Dec 10 changes
1 parent 464feb4 commit 0d64f56

File tree

2 files changed

+12
-0
lines changed

2 files changed

+12
-0
lines changed
13.4 KB
Loading

13/umbraco-engage/installation/installation.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -135,3 +135,15 @@ If you [change the default cookie behaviour](../developers/introduction/the-umbr
135135
### Load balancing and CM / CD environments
136136

137137
Are you using a load-balanced setup or separate CM and CD environments? [Please check our documentation about this topic](../getting-started/for-developers/loadbalancing-and-cm-cd-environments.md).
138+
139+
### The first run
140+
141+
When you visit your site locally for the first time, Umbraco Engage will begin tracking page views, visitors, etc. If you go to **Engage** -> **Analytics,** you won't see any data until the first reporting run. By default, reporting data will be generated at 04:00 AM automatically. 
142+
143+
<figure><img src="../.gitbook/assets/Umbraco-Engage-Regenerate-data.png" alt=""><figcaption><p>Regenerate button</p></figcaption></figure>
144+
145+
To generate reporting data manually on your local installation, go to **Engage** -> **Configuration.** Scroll down to **Reporting** section and click the red **Regenerate** button.
146+
147+
{% hint style="warning" %}
148+
Use the **Regenerate** button only in non-production environments because it can cause temporary performance degradation.
149+
{% endhint %}

0 commit comments

Comments
 (0)