Feed deployment status
In order to ensure the best possible performance while optimizing costs we provide different feed statuses that are adapted to the different usages that can be made of a feed.
Warming up feeds for increased performance
Warm up consists in pre-loading and caching a set number of posts so that they're ready to be served to your users in the fastest time.
Warmup works according to tiers, where users in higher activity tiers will get their cache refreshed more frequently than the ones in lower tiers. The current activity tiers are detailed below:
| Tier | Visits (30 days) | Priority Score | Avg Visits/Day | Refresh Interval |
|---|---|---|---|---|
| HOT | ≥100 visits | OR score ≥10.0 | 3.36 avg (1.87 median) | 3 hours |
| WARM | 50–99 visits | OR score ≥3.0 | 0.50 avg | 6 hours |
| LUKEWARM | 20–49 visits | OR score ≥1.0 | 0.21 avg | 12 hours |
| COLD | 5–19 visits | OR score ≥0.3 | 0.13 avg | Daily |
| COOL | 2–4 visits | – | 0.07 avg | Every 2 days |
| FROZEN | 1 visit | – | 0.03 avg | On-demand only |
Draft
This is a status adapted to feeds which are in the process of being created. The feed's infrastructure is light and API responses will be slow. This is adapted to a phase where you experiment with your feed configuration in the embed console or a staging environment.
Group
This feed status has been designed for beta testing. You will soon be able to upload a CSV to whitelist a group of users for whom the the will be warmed up.
The table will always reflect the latest uploaded CSV— this means old entries are removed, and only the new ones remain.
CSV formats that work:
| user_id | name | signup_date | |
|---|---|---|---|
| 12345 | John Doe | [email protected] | 2024-01-15 |
| 67890 | Jane Smith | [email protected] | 2024-02-20 |
| user_id |
|---|
| 90909 |
| 67890 |
Live
Use this status only when you're rolling out your feeds to full production. This will trigger full warmup for the integrity of your users.
This option might incur additional costs. Please visit our pricing page.
Viewing your feed's status
In order to ensure the best possible performance while optimizing costs we provide different feed statuses that are adapted to the different usages that can be made of a feed.
Go to your console Dashboard and review the toggle next to your feeds
Warmup latency
Our warmup cycles take place every 3 hours, meaning that a feed brought from Draft to Group or Live will be ready for deployment in t+3hours. This is the necessary time so that all of the user's feeds are ready to be served according to high performance standards.
Potential Impact of Feed Status
- API latency - feeds Draft status will take a longer time to load than what's expected by users.
- Cost implications - feeds in Group and Live status will imply warm up costs.
- User experience
- Warmup behavior
Updated about 1 month ago