⚠️

Initial Data Pull

This article aims to help you understand what happens during the first days after connecting your integrations.

Dependencies of initial loading speed

⚡️ The size of your community and the number of activities

⚡️ The number of clients (communities) that are being imported simultaneously

⚡️ API rate limits (different rate limits for each integration)

⚡️ Massive amount of simultaneous calculations waiting in the queue

How does the initial pull of data work

1️⃣ In the first minutes of connection

  • As soon as you connect an integration, we will start pulling the data from all the public channels. (Please check the Discord-specific particularities below)
  • The different API rate limits allow us to pull at a specific speed and can’t be changed, but don’t worry you will see data showing up in your account from the first few minutes
  • You might notice a notification modal on the left panel informing you about current data imports
image

2️⃣ First 24hours

  • Our powerful scoring system feature is not accessible during the first 24 hours, as we’re calculating the optimal setup in the background based on members and activities across your community. You will see some magic after 24h :)
  • In case we’re onboarding more than one community at the same time, the pulling jobs are evenly split into different queues and across API limits (This can increase the initial pull significantly)

3️⃣ After initial 24h

  • After 24 hours, you will be able to change the scoring system to your liking. Here is an article on how to set up your scoring system in case you don’t like our settings
  • If you create the first dashboards, make sure you press that refresh button from time to time. You will see that data start flowing in right from the beginning. Bit by bit, the reports in your dashboard will come to life. The refresh button sits under the 3 dots
image
  • In communities with a lot of historical data, the time to fully download everything to Ahoy might take several days. But don’t worry, you can use the platform → the data loading on the back is mostly the oldest history data.

Particularities per integration

Discord
  • Make sure the bot has permission to look into your channels. You can verify this in the channel section of your integration, This is how it looks
image
  • A full Discord-specific article is waiting for you here
  • Read permissions
  • Read history permissions (extended loading time during the initial pull)
  • 30 days into the past sentiment analysis (ML calculations slowing down initial pull)
Telegram
  • Read permissions
  • Read history permissions (extended loading time during the initial pull)
  • 30 days into the past sentiment analysis (ML calculations slowing down initial pull)
Circle
  • Read permissions
  • Read history permissions (extended loading time during the initial pull)
  • 30 days into the past sentiment analysis (ML calculations slowing down initial pull)
Hubspot
  • Read permissions
  • Read history permissions (extended loading time during the initial pull)
  • 30 days into the past sentiment analysis (ML calculations slowing down initial pull)
Twitter
  • Read permissions
  • Read history permissions (extended loading time during the initial pull)
  • 30 days into the past sentiment analysis (ML calculations slowing down initial pull)
Slack
  • Read permissions
  • Read history permissions (extended loading time during the initial pull)
  • 30 days into the past sentiment analysis (ML calculations slowing down initial pull)
Airtable
  • Read permissions
  • Read history permissions (extended loading time during the initial pull)
  • 30 days into the past sentiment analysis (ML calculations slowing down initial pull)
Vanilla Forums
  • Read permissions
  • Read history permissions (extended loading time during the initial pull)
  • 30 days into the past sentiment analysis (ML calculations slowing down initial pull)

Discourse
  • Read permissions
  • Read history permissions (extended loading time during the initial pull)
  • 30 days into the past sentiment analysis (ML calculations slowing down initial pull)
inSided
  • Read permissions
  • Read history permissions (extended loading time during the initial pull)
  • 30 days into the past sentiment analysis (ML calculations slowing down initial pull)
Github
  • Read permissions
  • Read history permissions (extended loading time during the initial pull)
  • 30 days into the past sentiment analysis (ML calculations slowing down initial pull)

What can you do during that time?

  1. You can start exploring the dashboard templates in the gallery.
  2. Start playing around and build your dashboards. Here is an article that explains how to navigate these waters
  3. You can build specific dashboards looking into this year and filtering by month (you will slowly see how the historical data is pulling in
  4. Start building some segments. Here is a very comprehensive article covering how to do so
  5. Make sure you get acquainted with our knowledge hub here and join our Discord server. Your gateway to the fastest support in the market 😁

Similar community loading times

Integration
Members
Total Activities
Number of channels
Initial loading time
Discord
70.000
1.2M
20
49h
Discord
56.000
476.000
4
24h
Slack
13.000
229.000
13
18h
Twitter
2.5M
3.9M
1
24h