Her finner du en samlet, strukturert oversikt over hvordan GoRabbit fungerer – for kunder, tekniske brukere og governance/styring.
GoRabbit’s master group database.
fb_group_master.json is the global master database of all Facebook groups known to GoRabbit. It contains metadata such as group name, ID, region, category, activity, risk, language, member count and rule sets. It is the foundation for Segments, proprietary internal mechanism handled automatically by the system.
Source for all group data.
The Group Master serves as the central source of truth. All modules — Segments, proprietary internal mechanism handled automatically by the system. Without the Group Master, there would be no standardized metadata and no reliable targeting.
JSON array with metadata for each group.
The proprietary internal mechanism handled automatically by the system.
Extensive metadata per group.
Metadata includes: (1) ID, (2) name, (3) category, (4) region, (5) language, (6) activity, (7) member count, (8) risk, (9) rule set, (10) admin strictness, (11) image permissions, (12) auto-tags, (13) history, and (14) last verification.
Region determines geographic targeting.
Region is used by Segments and the proprietary internal mechanism handled automatically by the system. For example: ‘NO’ for Norway, ‘ES-ALC’ for Alicante, ‘EU’ for Europe. It determines which groups are appropriate for a campaign and which should be excluded.
The group’s thematic category.
The category field defines which thematic cluster a group belongs to. Examples include: real estate, rentals, renovation, IT, food, health, motorhomes, travel, photography, families, etc. This field is critical for segmentation.
Measures group activity.
The activity score measures how active each group is. It is based on posts in the last 30 days, comment volume, and response rates. Low-activity groups receive low scores and are often filtered out by Segments.
Indicates potential reach.
Member count gives an indication of potential reach. Large groups often provide better visibility, but member count alone is not enough — relevance and risk matter more. The proprietary internal mechanism handled automatically by the system.
Measures risk of restrictions.
The risk score predicts the likelihood of failed posts, rejected content, or negative Facebook reactions. High-risk groups receive low scores or are excluded completely. This protects the customer’s account.
Group posting rules.
The ruleset describes the group’s publishing rules: ads allowed, images allowed, admin approval required, no self-promotion, no external links, etc. Segments uses these rules to evaluate group suitability.
Language affects targeting.
Language is important for targeting. Norwegian campaigns should mainly target Norwegian-speaking groups. International campaigns have broader language coverage. The language field strengthens scoring accuracy.
Strictness of group admins.
Admin strictness measures how strict the group administrators are. High scores indicate heavy moderation, frequent post rejections, or approval requirements. These groups usually have higher risk and lower priority.
Historical posting results.
The history field contains data such as last posting attempt, result, whether the post was accepted or rejected, and any Facebook reactions. This enables the system to learn and improve segmentation and risk scoring.
Last time the group was checked.
The last_checked field shows when the group was last validated by the Group Scanner or proprietary internal mechanism handled automatically by the system. Groups not validated for a long time receive lower score or are marked for re-scan.
One of the system’s most critical files.
The Group Master is one of the three most critical files in the GoRabbit system — together with segment rules and proprietary internal mechanism handled automatically by the system. Without an updated Group Master, the system loses accuracy, reach, and safety.
Automatically updates group data.
The Group Scanner updates fb_group_master.json by fetching changes in groups: new rules, member counts, activity levels, language, admin restrictions and other metadata. It is used for periodic maintenance.
Weekly by default.
The recommended frequency is once per week. For high-load or multi-campaign operations, it may run daily. Enterprise environments can configure automatic cron-based schedules.
Must be added to be used.
If a group is missing from fb_group_master.json, Segments cannot use it. These groups are flagged in the proprietary internal mechanism handled automatically by the system.
Yes — customer additions supported.
Yes. Customers may submit their own groups through GoRabbit.no. These are stored in a customer-specific proprietary internal mechanism handled automatically by the system. After verification, the group is added to the Group Master.
Groups that must never be used.
Blacklisted groups come from historical blocks, publishing failures, rule violations, spam patterns, or manual administrator decisions. These groups are permanently removed from all segments.
Groups always prioritized.
Whitelisted groups are groups that should always be included. These may be customer-owned groups, GoRabbit-owned groups, partners, or high-performance groups.
Total quality score.
Quality is measured using a total score: activity + relevance + risk + history. High-quality groups deliver consistent publishing success. Quality is used to optimize future campaigns.
Deprecated groups are excluded.
Groups with no activity over time are flagged as outdated and receive low scores. After multiple negative cycles, they are marked as deprecated and excluded from segmentation. They may be reactivated manually.
High precision for city/country.
Geolocation is based on group names, descriptions, and auto-tags. Accuracy is very high for city and country levels but may vary in small regions. Customers can submit corrections.
Continuously updated.
Synchronization is maintained through: (1) periodic Group Scanner runs, (2) proprietary internal mechanism handled automatically by the system. The system ensures Group Master stays current.
Supports tens of thousands of groups.
The Group Master can hold tens of thousands of groups without performance issues. The JSON format keeps the proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system.
Validation ensures consistency.
Consistency is ensured through validation routines that check for duplicates, invalid ID formats, incorrect regions, incorrect language and missing fields. Changes must pass proprietary internal mechanism handled automatically by the system.
Used to identify correct groups.
The proprietary internal mechanism handled automatically by the system. Groups are then filtered based on segment rules, risk and relevance before entering normalized_group_list.json.
Duplicates removed automatically.
The proprietary internal mechanism handled automatically by the system. Duplicates are logged for manual review.
Imported via a safe pipeline.
New groups pass through an import pipeline: (1) customer proprietary internal mechanism handled automatically by the system. This ensures data quality.
Faulty groups excluded temporarily.
Errors are caught by the validation module and logged to Slack. The system does not stop campaigns, but flawed groups are excluded until corrected. This keeps the system robust against data corruption.
Missing groups for a segment.
A gap occurs when segmentation requires groups that are not present in the Group Master. Example: when a customer requests a new region. Gaps are automatically flagged and forwarded to admin with expansion suggestions.
Full metadata validation.
The validation pipeline includes: (1) schema check, (2) duplicate check, (3) region validation, (4) language validation, (5) rule set verification, (6) risk analysis, (7) activity score calculation, (8) history update. Only validated groups are activated.
Monthly full update.
Global updates run a complete review of the entire group list. The system checks changes in names, rules, activity and language. Large datasets are typically updated once per month.
Only changed groups updated.
Instead of scanning the entire database, updates run only on groups that changed since last_checked. This reduces resource usage and speeds up maintenance.
Shows risk and quality.
Quality flags are indicators marking risk, low activity, rule violations or historically rejected posts. The proprietary internal mechanism handled automatically by the system.
Marked as 'unverified'.
If the Group Scanner cannot access a group (Facebook errors, permission changes, etc.), the group is marked 'unverified' and assigned low score until the next successful scan.
New rules → new score.
Changes in admin rules (e.g. images no longer allowed, admin approval required) are detected in the next scan. The group receives an updated score and may be temporarily excluded if risk increases.
Permanently blocked.
A hardlock means the group must never be used again. Reasons include severe rule violations, repeated block events or security issues. Hardlocked groups are removed from all segments and cannot be reactivated.
Temporarily blocked.
A softlock means the group is temporarily excluded due to low activity, behavioral anomalies, rule changes or temporary errors. The group may be reactivated after validation.
Admin-only edits.
Yes, but only by administrators. Manual edits always pass through validation before activation to prevent errors that could impact Segments or the proprietary internal mechanism handled automatically by the system. Customers cannot directly edit the Group Master.
Limited customer visibility.
Customers see only limited and anonymized information in the UI — such as number of groups selected, regional distribution and excluded groups. The full Group Master is internal-only.
Export available internally.
Yes, if needed. Export is available in JSON or CSV for analysis, administrative review or archival. Customer data and sensitive fields are automatically removed prior to export.
Full regeneration possible.
Yes. The system can perform a full reconstruction if needed (in case of errors, configuration changes or major data loss). This takes longer but ensures full data integrity.
Supports seamless EU expansion.
EU expansion is handled by adding new region codes (e.g., DE, FR, IT, BE, NL) and auto-generating metadata for thousands of groups. Segments and proprietary internal mechanism handled automatically by the system.
Scales globally without changes.
Yes. The architecture supports global scaling including regions in the US, Asia, South America and Africa. New countries are introduced through the same pipeline used for EU expansion.
AI and realtime coming later.
Future improvements include: (1) AI-based group detection, (2) better region classification, (3) automatic language detection, (4) real-time updating, (5) subscription-based customer visibility.
Group Master = heart of the system.
The Group Master is the heart of GoRabbit. It ensures all campaigns target the right groups with the right risk level, language, activity and category. Without the Group Master, accurate publishing is impossible.
Final validation before use.
Before the proprietary internal mechanism handled automatically by the system. Only after passing this check is it used for segmentation.