Her finner du en samlet, strukturert oversikt over hvordan GoRabbit fungerer – for kunder, tekniske brukere og governance/styring.
Prepares the account for safe publishing.
The proprietary internal mechanism handled automatically by the system. proprietary internal mechanism handled automatically by the system. Without proprietary internal mechanism handled automatically by the system. The module simulates natural activity through proprietary internal mechanism handled automatically by the system.
To avoid triggering Facebook’s safety mechanisms.
Facebook monitors aggressive posting behavior. Accounts that suddenly go from zero activity to posting in 200 groups in one day are automatically flagged. proprietary internal mechanism handled automatically by the system. This gives Facebook a ‘normal’ posting history and reduces the risk of restrictions by 80–95%.
Standard 14 days, adjustable.
Standard proprietary internal mechanism handled automatically by the system. The days gradually increase posting volume and frequency. The system can extend to 21 or 30 days for sensitive accounts (typically newly created accounts). For strong accounts or stable business tokens, proprietary internal mechanism handled automatically by the system.
Gradual, randomized, safe activity.
proprietary internal mechanism handled automatically by the system. (2) Gradual daily increase. (3) Randomized posting intervals. (4) Natural pauses. (5) No repetitive patterns. (6) No posting to sensitive groups early. (7) Respect for the account’s history. (8) Auto-stop if Facebook reacts.
proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. proprietary internal mechanism handled automatically by the system.
Executed exactly like normal posting.
RabbitAgent performs proprietary internal mechanism handled automatically by the system. The difference is that proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system.
Selects groups via global + customer + campaign data.
Groups are selected through three layers: (1) fb_group_master.json — a global list of all groups. (2) gruppe_mapping.json — the customer’s priorities and overrides. (3) Campaign A-json — the groups the campaign should target. proprietary internal mechanism handled automatically by the system.
Gradually increasing volume day by day.
proprietary internal mechanism handled automatically by the system. Day 2: 8–12. Day 3: 10–15. Day 4: 12–20. Day 5: 15–25. After that, 30–50 per day. The exact curve is adjusted based on account type, prior restrictions, and posting windows. This model is based on thousands of real publishing cycles.
NiceLife can publish without proprietary internal mechanism handled automatically by the system.
The NiceLife account has documented history, high stability, and strong tokens. Therefore, it can safely skip the entire 14-day proprietary internal mechanism handled automatically by the system. This exception applies only to NiceLife and certain verified business pages. All other accounts require full proprietary internal mechanism handled automatically by the system.
No — sensitive groups avoided early.
No. proprietary internal mechanism handled automatically by the system. Sensitive groups, political groups, low-activity groups, and groups with strict moderation are avoided until day 7–12. Some are never used in proprietary internal mechanism handled automatically by the system.
Stops immediately and alerts.
If a proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. proprietary internal mechanism handled automatically by the system. proprietary internal mechanism handled automatically by the system.
Yes — dedicated Slack category.
Yes. proprietary internal mechanism handled automatically by the system. The system also marks when proprietary internal mechanism handled automatically by the system.
Uses 6 key files.
proprietary internal mechanism handled automatically by the system.json, (2) gruppe_mapping.json, (3) the campaign’s A-json, (4) warmup_config.json, (5) warmup_queue.json, (6) slack_log.json. These files are used to select groups, generate timing, track progress, and send status updates.
Yes — but only light, non-commercial content.
Yes. proprietary internal mechanism handled automatically by the system. The content must be light, natural, and non-sales-oriented. proprietary internal mechanism handled automatically by the system.
Fully automated after start.
proprietary internal mechanism handled automatically by the system. The customer only selects groups, defines the campaign, and presses 'Start proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system.
Yes — auto-stop on risk.
Yes. If Facebook shows signs of restriction, the account behaves unusually, cookies fail, or postings are blocked, proprietary internal mechanism handled automatically by the system. An operator must manually approve resuming after confirming the issue.
Yes — flexible duration.
Yes. The proprietary internal mechanism handled automatically by the system. The system supports 3, 5, 7, 14, 21, and 30 day proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system.
Short, light, neutral content.
Best practice is: short text, neutral content, light information, emoji teasers, small images without strong commercial messaging. proprietary internal mechanism handled automatically by the system.
Yes — but only after manual approval.
Yes, but only after manual approval. The proprietary internal mechanism handled automatically by the system. proprietary internal mechanism handled automatically by the system. It never skips days or increases volume unnaturally after a stop.
Tracks error rate, DOM, cookies, and risk.
proprietary internal mechanism handled automatically by the system. Based on these metrics, proprietary internal mechanism handled automatically by the system.
New or weak accounts require most proprietary internal mechanism handled automatically by the system.
Accounts requiring the most proprietary internal mechanism handled automatically by the system. These should complete at least 14 days of proprietary internal mechanism handled automatically by the system.
No — proprietary internal mechanism handled automatically by the system.
No. proprietary internal mechanism handled automatically by the system. If the system is paused for multiple days, proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system.json to: (1) identify which groups are safe for early proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system.
A-json provides the group base for proprietary internal mechanism handled automatically by the system.
The A-json is the campaign’s base list of groups. proprietary internal mechanism handled automatically by the system. If A-json contains many groups, proprietary internal mechanism handled automatically by the system. From day 7 onward, the full set is used.
proprietary internal mechanism handled automatically by the system.
The Publisher receives proprietary internal mechanism handled automatically by the system. The difference is that proprietary internal mechanism handled automatically by the system. The Publisher ensures proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system. All proprietary internal mechanism handled automatically by the system.json and are reloaded after a restart. The proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. No proprietary internal mechanism handled automatically by the system.
Yes — baseline activity recommended.
Yes. The account should have (1) a minimum number of friends, (2) some personal posts, (3) profile picture, (4) normal activity. Accounts with zero activity are high risk. proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system. Campaign = volume.
proprietary internal mechanism handled automatically by the system. A full campaign is high-volume posting aimed at reach, conversions, and distribution. proprietary internal mechanism handled automatically by the system.
Yes — but requires long and careful proprietary internal mechanism handled automatically by the system.
Yes, but with extreme caution. New accounts are very risky. They often require 21–30 days of proprietary internal mechanism handled automatically by the system. proprietary internal mechanism handled automatically by the system.
Yes — but not early.
Yes, but only after day 5–7. Large groups have stricter moderation and higher risk. proprietary internal mechanism handled automatically by the system.
Yes — with variations.
Yes, but in moderation. proprietary internal mechanism handled automatically by the system. The system also randomizes small text components to avoid pattern detection.
Uses server timezone.
proprietary internal mechanism handled automatically by the system. Customers can also define their own timezone in the campaign, which the proprietary internal mechanism handled automatically by the system.
Yes — but controlled.
Yes, but within safe parameters. proprietary internal mechanism handled automatically by the system. However, strict bounds ensure start and end volume per day remain safe.
When proprietary internal mechanism handled automatically by the system.
After proprietary internal mechanism handled automatically by the system. This indicates the account has: (1) posting history, (2) normal engagement profile, (3) tested tokens, (4) stable cookies, (5) no restrictions, and (6) zero risk indicators.
Safe, controlled account proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system. It follows strict safety rules, analyzes risk, pauses automatically on anomalies, and ensures that customer accounts can publish to hundreds of groups without restrictions.
Typically 120–200 groups total.
proprietary internal mechanism handled automatically by the system. Only 20–40 safe groups are used during the first five days, and the volume gradually expands. Large campaigns may use up to 300 groups, with strict prioritization.
Automatic throttling protects the account.
proprietary internal mechanism handled automatically by the system. It inserts pauses, extends intervals, and stops completely on risk. This protects the account’s reputation.
Yes, full schedule is visible in GoRabbit.
Yes. GoRabbit displays a complete overview of proprietary internal mechanism handled automatically by the system. This gives the customer clear insights into progress without needing technical knowledge.
Priority based on risk and activity.
Priority is determined by: (1) group activity, (2) risk history, (3) moderation level, (4) group type, (5) customer priorities from gruppe_mapping.json, and (6) global score from fb_group_master.json. This ensures safe and stable proprietary internal mechanism handled automatically by the system.
Only late — and only a few.
Only late in the process. Low-activity groups carry higher risk of manual moderation. They are therefore included only after day 10, and in low volume. Some low-activity groups are not used at all.
proprietary internal mechanism handled automatically by the system.
If Facebook changes critical UI elements (Create Post box, image upload button, DOM structure), the proprietary internal mechanism handled automatically by the system. proprietary internal mechanism handled automatically by the system. The system resumes only after updated Playwright selectors are deployed.
Internal risk score for safe proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system. It includes: (1) failure rate, (2) DOM latency, (3) number of restrictions, (4) Facebook reactions, (5) engagement level, (6) cookie stability, and (7) group risk. The score is used for automatic pause logic.
Yes — tokens validated daily.
Yes. Each day, the proprietary internal mechanism handled automatically by the system. If a proprietary internal mechanism handled automatically by the system. This avoids publishing attempts with invalid credentials.
Completed when all posts done and risk = low.
To complete proprietary internal mechanism handled automatically by the system. Then proprietary internal mechanism handled automatically by the system.
Scales to hundreds of accounts.
proprietary internal mechanism handled automatically by the system. You can run 10, 50, or 200 proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system. Cooldown reduces posting volume when an account has been exposed to risk or restrictions. Cooldown is used after heavy campaigns, past limitations, or UI changes. proprietary internal mechanism handled automatically by the system.
Stable account and safe publishing.
proprietary internal mechanism handled automatically by the system.
Safe posting history before full capacity.
proprietary internal mechanism handled automatically by the system.
Account proprietary internal mechanism handled automatically by the system.
The proprietary internal mechanism handled automatically by the system. It mimics human behavior by posting moderately, varying timing, reacting to posts, and gradually increasing frequency. This reduces risk of restrictions and ensures account stability.
To avoid blocks and detection.
New or inactive Facebook accounts that suddenly publish to hundreds of groups are flagged as suspicious. proprietary internal mechanism handled automatically by the system. This makes publishing safer and increases reach.
Realistic intervals and variation.
The proprietary internal mechanism handled automatically by the system. These behaviors make the proprietary internal mechanism handled automatically by the system.
Typically 10–14 days.
Standard proprietary internal mechanism handled automatically by the system. Accounts with strong history may reduce this to 3–5 days. Accounts with restriction history may require longer proprietary internal mechanism handled automatically by the system.
Yes — both types need proprietary internal mechanism handled automatically by the system.
Yes. Personal accounts need proprietary internal mechanism handled automatically by the system. Business accounts need proprietary internal mechanism handled automatically by the system.
Four phases: Light → Moderate → Heavy → Launch.
proprietary internal mechanism handled automatically by the system. (2) Moderate: 5–15 groups/day. (3) Heavy: 15–30 groups/day. (4) Launch: unrestricted publishing. The proprietary internal mechanism handled automatically by the system.
Yes — several proprietary internal mechanism handled automatically by the system.
Yes. Customers may choose standard proprietary internal mechanism handled automatically by the system. Enterprise clients may receive customized profiles where the proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system.json which RabbitEngine reads before main publishing begins. The proprietary internal mechanism handled automatically by the system. When proprietary internal mechanism handled automatically by the system.
Executes proprietary internal mechanism handled automatically by the system.
RabbitAgent performs all proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system.
Adapts continuously to risk.
proprietary internal mechanism handled automatically by the system. If Facebook starts rejecting posts or reducing visibility, proprietary internal mechanism handled automatically by the system.
Yes — when risk is low.
Yes. If the account shows very strong history and low risk, the proprietary internal mechanism handled automatically by the system. This is done automatically based on historical score.
Minimal proprietary internal mechanism handled automatically by the system.
Customers with few groups may enable minimal proprietary internal mechanism handled automatically by the system. This is useful for proprietary internal mechanism handled automatically by the system.
Advanced proprietary internal mechanism handled automatically by the system.
Enterprise mode includes advanced proprietary internal mechanism handled automatically by the system. This provides optimal account health for large campaigns.
Config and proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system.json, (2) normalized_group_list.json, (3) gruppe_mapping.json (optional), (4) fb_group_master.json, (5) warmup_config.json. These files form the data foundation.
Segments = who. proprietary internal mechanism handled automatically by the system.
Segments define which groups the campaign will publish to. proprietary internal mechanism handled automatically by the system. In short: Segments = who. proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system. proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system. RabbitEngine is the production phase that distributes the campaign at full scale. proprietary internal mechanism handled automatically by the system.
A list of proprietary internal mechanism handled automatically by the system.
warmup_queue.json is an array of proprietary internal mechanism handled automatically by the system. Each task includes group_id, group_name, proprietary internal mechanism handled automatically by the system. This allows the proprietary internal mechanism handled automatically by the system.
Starts in safe groups.
Groups are selected based on segments, risk, activity and relevance. proprietary internal mechanism handled automatically by the system. More demanding groups are added gradually. Group history influences prioritization.
Randomized intervals.
proprietary internal mechanism handled automatically by the system. All intervals are randomized to simulate human variation.
Light activity in safe groups.
The Light phase includes: small posts, likes, scrolling, participation in low-risk groups, and short pauses. No aggressive or high-risk groups are used. The goal is to establish natural activity.
Increases volume and variation.
The Moderate phase increases the number of groups, adds more advanced scrolling and reactions, and tests posting in medium-risk groups. The proprietary internal mechanism handled automatically by the system.
High volume and stress test.
The Heavy phase includes publishing in larger volumes (15–30 groups), stronger timing variation, and more advanced actions. This phase determines whether the account is ready for full publishing.
Full production begins.
The Launch phase means proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system.
If the system detects abnormal patterns such as rapid post rejections, drop in reach or repeated failures, proprietary internal mechanism handled automatically by the system. In severe cases, the account is placed in a 24–72h cooldown.
Rest period for high risk.
Cooldown is a rest period where the account does not post. It is triggered when risk is high or Facebook has imposed temporary limitations. The system logs this in Slack and resumes proprietary internal mechanism handled automatically by the system.
History influences speed.
proprietary internal mechanism handled automatically by the system. Accounts with strong history progress faster. Accounts with weak history receive more conservative proprietary internal mechanism handled automatically by the system.
Supports both text and images.
Yes. proprietary internal mechanism handled automatically by the system. The system selects the appropriate content based on group rules and natural behavior.
Yes — for strong accounts.
Yes, but only for accounts with extremely strong history or when publishing via authorized Page Tokens. Bypass is used only in special cases, such as NiceLife Page proprietary internal mechanism handled automatically by the system.
Typically 30–80 groups.
proprietary internal mechanism handled automatically by the system. Smaller campaigns may use 10–20, while large campaigns may involve over 100 groups with strict progression control.
proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system. Full publishing means the system posts to all segmented groups without upper limits. proprietary internal mechanism handled automatically by the system.
Yes — pausing supported.
Yes. proprietary internal mechanism handled automatically by the system. The pause is safe — no tasks are deleted, and the proprietary internal mechanism handled automatically by the system.
JSON status + Slack updates.
Progress is tracked in warmup_queue.json via status fields such as pending, running, completed, failed and cooldown. Slack notifications are also sent for all milestones.
Errors → retry → cooldown if needed.
proprietary internal mechanism handled automatically by the system. If a task fails, it is flagged as failed and retried after a randomized proprietary internal mechanism handled automatically by the system. If the issue repeats, the account enters cooldown. All errors are logged to Slack with details about the group, cause and recommended actions.
proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system. This gives high transparency in production and makes troubleshooting easy. Each proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system. The campaign enters waiting mode until proprietary internal mechanism handled automatically by the system. Once proprietary internal mechanism handled automatically by the system.json.
Limited by Facebook's rules.
Yes. proprietary internal mechanism handled automatically by the system. It also cannot warm up groups requiring admin approval or groups the account is not a member of.
Yes — highly scalable.
Yes. The system can run proprietary internal mechanism handled automatically by the system. proprietary internal mechanism handled automatically by the system.
Resumes exactly where it left off.
If the system stops (e.g., server restart), proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. No tasks repeat unnecessarily, and no steps are skipped.
Group excluded immediately.
If a group suddenly becomes high-risk (e.g., admin changes rules), it is automatically excluded from the rest of the proprietary internal mechanism handled automatically by the system. proprietary internal mechanism handled automatically by the system.
Active campaign or inactive account.
proprietary internal mechanism handled automatically by the system. It also triggers automatically if the account has been inactive for 7–30 days.
8 status codes.
proprietary internal mechanism handled automatically by the system. These make it easy to understand the campaign’s activity and real-time state.
No — one group at a time.
No. proprietary internal mechanism handled automatically by the system. Multi-posting is only available in full proprietary internal mechanism handled automatically by the system.
Stable activity → risk reset.
If an account enters cooldown or gets rejected posts, proprietary internal mechanism handled automatically by the system. After 48–72 hours of stable results, the risk model resets and proprietary internal mechanism handled automatically by the system.
Full admin control when needed.
Admins can pause, resume, skip groups, change speed, manually switch phases, reset proprietary internal mechanism handled automatically by the system. This makes the module extremely flexible in production.
All proprietary internal mechanism handled automatically by the system.
warmup_config.json contains: proprietary internal mechanism handled automatically by the system.
Fallback for unusual conditions.
Edge cases — such as the account losing access to groups, Facebook downtime or major changes in segments — trigger fallback mode. The system delays proprietary internal mechanism handled automatically by the system.
Reports to proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system. This gives full transparency.
proprietary internal mechanism handled automatically by the system.
When proprietary internal mechanism handled automatically by the system. The warmup_queue.json proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system. It mimics human behavior, builds account health, minimizes risk and ensures campaigns can publish at scale without restrictions. Without proprietary internal mechanism handled automatically by the system.