Gamfi for sales · Module
Sales data integration – results from your systems feed targets, contests and bonuses
Results stay where they are created – in your sales system, data warehouse or point-of-sale system. Gamfi pulls them through a documented API and turns them into targets, a live result, contests and bonus calculations. One connection serves every module, so adding another programme does not go back into your IT's task queue.
Our API is designed for this kind of integration, and we agree the scope and timeline with your IT. A programme can start on files before the target integration is ready.
Data source
sales system
results stay where they are created
Connection
one
API, webhooks or files to start with
Draw on this feed
every module
targets, live result, contests, knowledge, rewards, bonuses
They improve their results with us
How it works
One data connection serves the whole chain – from target, through contest, to a calculated bonus.
- 1
We agree the source of truth
Where results come from: a sales system, a data warehouse, a point-of-sale system, files. We also agree which metrics should drive programmes and how we recognise people.
- 2
We connect the feed
A documented API for sending results, webhooks for events from your systems, and file import to start with – depending on what your team can do.
- 3
Data works in every module
The same stream feeds targets, a live result, contests, knowledge doses and calculations. One connection, not five separate integration projects.
- 4
Accounts and access stay with your IT
Company sign-in (SSO), automatic creation and closing of user accounts, two-factor authentication and passwordless sign-in – set up in the panel, on your side.
More, because it is one system
A separate tool for targets, another for contests and a third for commissions means three integrations with the same source. Here, one connection serves the whole chain.
One feed, every module
The same stream of results drives targets, dashboards, contests, the incentive programme, knowledge doses and bonus calculations. Your IT does one project, and adding another area does not mean a new integration. Tools bought separately – for commissions, for competitions, for learning – each need their own connection to the same source.
We recognise people with no company inbox
The incentive and commission tools you compare us to take a company email address as a participant's identifier. In a Polish retail network or in the field, that address is often missing, and then a result has no way of reaching the right person. Gamfi recognises a participant by an HR code, so a programme covers the whole network, not just head office.
Access security included in the price
Company sign-in, automatic account creation, two-factor authentication and passwordless sign-in are part of the platform. In business software, company sign-in is sometimes a paid add-on or a condition of a more expensive tier – with us, it is not a separately priced add-on.
See how Gamfi is used in sales networksCustomers →
Describe your need
Describe the situation in your own words – we will write back with how the Gamfi platform answers that challenge. You decide about a meeting after you have read the answer.
What you get in Gamfi
What a large organisation's IT department asks before letting a new tool in.
Data feed
- A documented, public API for sending sales resultsyou get the documentation before signing the contract, for your IT to assess
- Webhooks for events from your systemsan event counts with no waiting for a scheduled read
- File import to start withthe programme starts while the target integration is still in progress
- Importing results with a row-by-row error reportyou see what does not match before the upload is accepted
- Tokens assigned to the organisation, not to a personan administrator leaving does not break the integration
- One feed for every moduletargets, live result, contests, knowledge, rewards, calculations
- An MCP server for your AI toolsan assistant on your side reaches the data within the scope you set
Recognising people in the network
- Recognising a person by an HR code, a company address, or an identifier from the sales systema result reaches the right person even where advisors have no company inbox
- Automatic creation and closing of user accountsin line with HR movements on your IT's side
- Sign-in by link or SMSfor people who have no account on your domain
Sign-in and access
- Company sign-in (SSO) on the OpenID Connect standardwe confirm the list of supported identity providers at a technical meeting
- Two-factor authentication with a policy per organisationyou switch the requirement on, not us
- Sign-in with a hardware key or biometrics, no passwordpasskeys
- Sign-in settings in a self-service panela change with no ticket to the vendor's support
- Access security included in the platform's pricecompany sign-in and automatic accounts are not a separate line in the offer
Data protection and separation
- Each organisation's data separated at database levelaccess enforced by rules in the database itself, not only by a filter in the app
- Data stored in the European Unionincluding processing on the AI features' side
- Integration tokens and keys encrypted by a separate systemsecrets do not sit in the configuration as plain text
- Gamfi as a data processora GDPR model with a data processing agreement
Trail and audit
- An append-only log of changes and accesswe neither delete nor overwrite entries; every operation has an author and a timestamp
- A history of changes to company sign-in settingswith the author and a timestamp
- Reconstructing who changed the integration's access datamaterial for an audit question
- A trail of admin actions and sign-ins in a user's contextflagged in the log
Implementing the integration
- Your IT team carries out the integrationbased on the documentation, with no waiting for our calendar
- The Gamfi team can run the integrationas part of the implementation project
- Starting on files, adding the API laterthe programme does not wait for your IT's task queue
- A correction in source data recalculates the resultearlier records stay in the history; the mechanics of closing a period are described on the bonus calculation page
Common questions
Open the one that applies to you.
You don't have a ready-made connector for our sales system. Will that block the implementation?
It does not block the start. Our API is designed for this integration and has public documentation, and you can start on files. The integration is carried out by your team, a partner, or us as part of implementation. We say plainly how it is: we do not sell a list of ready-made connectors, only one feed that every module draws on.
Who carries out the integration, and what affects its scope?
It can be carried out by your IT team based on the documentation, or by us and an implementation partner as part of a project. The scope depends on the number of data sources and on how people are currently mapped in your systems – we go through this at a technical meeting.
How often does data flow?
On our side, a result is visible as soon as the API accepts it, and with files, as soon as they are uploaded. The real pace is set by your system, and we agree that at a technical meeting. We say this plainly, because in this category "live" often means data from an overnight recalculation.
What about corrections: a return, a reversal, a correction after the fact?
A correction in the source data recalculates what changed, and the history of earlier calculations stays. The mechanics of thresholds, disputed items and closing a period are described on the bonus and commission calculation page.
Where is our data, and who has access to it?
Data is stored in the European Union and separated from other organisations' data by rules in the database itself, not only by a filter in the app. Every change and every sign-in stays in a log whose entries we neither delete nor overwrite. Integration secrets are encrypted by a separate key management system, and we provide the list of sub-processors and the processing regions together with the data processing agreement.
Do you have a test environment, and what happens to the data after the contract ends?
We agree the scope of the test environment, request limits, and how data is handed over on exit in the contract and at a technical meeting. We hand over data in formats a spreadsheet can open, together with the event history.
Do we pay separately for company sign-in or automatic accounts?
No. Company sign-in, automatic account creation, two-factor authentication and passwordless sign-in are part of the platform and are not a separate line in the offer.
Our IT will send you a security questionnaire. Will you fill it in?
Yes, that is a normal part of talking to a large organisation. We answer questions about data separation, processing location, the event log, secret encryption, sub-processors and the data processing model. Where we do not have something, we say so plainly – in a requirements matrix that is faster than explaining it later.
We also want to feed our own AI assistant with data. Is that possible?
Yes. The platform provides an MCP server, so your AI tools can use the organisation's data within the scope you set. We agree the scope of permissions and the access model during implementation.
What does pricing depend on?
Several factors affect pricing: the number of people in the network, the number of data sources to connect, and the scope of modules that use this data. We are happy to go through the details at a meeting and in further contact.