Who the platform is for
GBS® is a Polish food group that runs marketing for several brands: newsletter signups, contests and discount-code campaigns. Alongside that it exchanges data with B2B partners, who pass on registry information and consent status.
Consent records were scattered across several databases, each brand's own tools and email inboxes. Every GDPR audit meant gathering data by hand, and adding a brand or a partner took weeks of integration work.
What we delivered
One consent management platform for every GBS® brand, its campaigns and its B2B partners.
Multi-brand campaigns: newsletters, contests and discount-code drops set up per brand, with email, SMS or both as verification.
A code redemption page for customers in each brand's own look.
A discount-code API other GBS® systems can use, not only the built-in page.
A B2B partner integration: published OpenAPI documentation and webhooks that pass withdrawals and registry data to partners automatically.
Partner validation against the company registry by NIP and REGON at signup.
An audit log where granting consent, withdrawing it and syncing it to a partner are each recorded as separate events.
One log for every consent
The key decision: every consent, wherever it comes from, lands in a single log. Withdrawal therefore works the same way for a newsletter, a contest and a partner, and answering a GDPR request is one search instead of pulling data from several systems.
The same code-issuing mechanism behind the built-in redemption page is available over the API. Among others, the Halloween game we later built for GBS® uses it.
Where it stands today
The platform has been running since 2025. A new brand or B2B partner is a configuration change, not a separate project. The marketing team launches campaigns on its own, and partners connect by following the published API documentation.
