Since WhatPulse 2.2, the client has been able to upload your local application statistics to the website. This article will go into a little bit of detail on how it actually does that.
Whenever the client detects that an application is getting attention (whether it be input or active uptime), it saves that in it's local database, along with some details of the application (name, version, etc). These stats are saved as "pending application stats"
When you pulse, the client sends these pending application stats along with your other total stats. This synchronisation with the website is based on application IDs. Each different application has it's own ID to identify your different apps on the website.
Every 30 minutes, the client checks if it has any new applications and sends them to the website through a separate communication with the website (separate from pulsing). When this communication is complete, the new applications will receive an application ID, which is stored in your local database.
So only after new applications are uploaded, the stats for those applications will be pulsed. If you launch a new application and use it, the client will take 30 minutes to get an application ID and only after those 30 minutes, the application will start to show up in your pulses.
If something seems wrong with your application stats in your pulses, there is an option to reset all your local application IDs by using the option "Re-upload applications" in the "Advanced" menu on the "Settings" tab.