API users and links.

The iRaiser platform complies with the GDPR (General Data Protection Regulation) for storing personal data. Managers can use the dashboard to manage, for example, all consent texts displayed in forms that require Users to grant permission by checking a box. Below is general information on how to comply with the GDPR within iRaiser and some general explanation of what the GDPR is.
Content of article:

Introduction
Controller versus Processor
What is personal data?
What is a special personal data?
When is there processing of personal data?
General rules for processing personal data
Overview Personal data
Exporting personal data: transfer
What are the rights of data subjects?
Expressive consent
Rights of data subjects

Right of access
Right to rectification and completion and/or restriction of processing
Right to erasure

At the request of the data subject (end user)
On termination of contract

Right to data portability

Introduction
To safeguard the data of our customers and their Users, we have established privacy and data protection policies within iRaiser.
Privacy protection & personal data; General Data Protection Regulation
Privacy protection is regulated by various laws and treaties. The most important is the General Data Protection Regulation (GDPR), which comes into force from 25 May 2018. This is a European regulation (i.e. with direct effect) that standardises the rules for the processing of personal data by private companies and public authorities throughout the European Union. In addition, the Telecommunications Act provides rules on mailings, spam and cookies.
Processor versus Processor
The GDPR makes a clear distinction between the duties and responsibilities of a so-called Controller and a Processor. iRaiser's customer owns the website and the data acquired with the website. They are the Controller. iRaiser carries out the technical operation of the website and does not do anything with the data without the consent of the customer. iRaiser is in GDPR terms a processor. The powers, duties and responsibilities of us as a Processor in terms of processing personal data are agreed in the so-called Processor Agreement that we conclude with our customers.  
What is a personal data?
Personal data is any data by which a person can beïdentified. A person can be identified if the person using the personal data can identify the person without making a special effort. This could include name and address data. E-mail addresses, passport photos, fingerprints and, for example, IP addresses are also considered personal data. And data that give a rating about a person, for example someone's IQ.     
What is a special-personal data?
In addition to ordinary personal data, the law also recognises special personal data. These are data that are so sensitive that processing them could seriously affect someone's privacy. Such data may therefore only be processed under very strict conditions. Special or sensitive personal data include, for example, data that says something about someone's race, religion, health, criminal past or sexual life. Trade union membership and the citizen service number (BSN) are also special personal data.
Special personal data is data about someone's:

race or ethnic origin
political opinions
religion or belief
membership of a trade union
genetic or biometric data for the purpose of unique identification
health
sexual life
criminal history

An organisation may not use special personal data unless there is an exception for this in the law. There must be a need to request this data.
When is personal data processing?"
Processing means any operation involving personal data. The law lists as examples of processing: the collection, recording, organisation, storage, updating, modification, retrieval, consultation, use, provision by means of forwarding, dissemination or any other form of making available, bringing together, linking, blocking, erasing and destroying of data. From this enumeration, it is clear that the processing of personal data is readily apparent. One could argue that everything one does with personal data do falls under processing.
General rules for processing personal data
Main rule is that personal data shall only be processed in accordance with the law and in a proper and careful manner. In addition, personal data may only be collected if a precise purpose is given for it. Moreover, the law states that personal data may only be processed insofar as they are adequate, relevant and not excessive.An example from practice is the making of a copy passport.An important obligation arising from the law is the notification that the processor must make to the Personal Data Authority AP. This notification is intended to promote transparency: all notifications made to the AP are included in a public register. Some processing operations do not need to be notified under the law, such as the trade register of the Chamber of Commerce. In addition, the GDPR includes a large number of processing operations that are exempt from notification. For such exempted processing operations, the other requirements of the GDPR simply remain in force. In addition to the general rules mentioned above, a justification ground must be present for any processing of personal data. This is explained below.
Conditions for processing personal data: justifications
In addition to the general rules mentioned above, the GDPR requires that at least ééone of the justifications listed in the law must apply to any processing of personal data. The GDPR has the following bases:

ConsentThe data subject (this is the person whose data is being processed) has given his unambiguous consent to the processing. This explicit consent is also called informed consent or informed consent 
. The processing of personal data of a child under 13 requires the consent of a parent or legal representative. An organisation must make a reasonable effort to verify that consent.

Execution of contractData processing is necessary for the performance of a contract to which the data subject is a party.

Legal obligationData processing is necessary for compliance with a legal obligation.

Vital interestData processing is necessary to counter a serious threat to the health of the data subject.

Public law taskThe data processing is necessary for the proper performance of a public law task.

Justified interestData processing is necessary for the fulfilment of a legitimate interest of the data controller (or of a third party to whom the data are disclosed). This means that the person processing the data must weigh his own interest against the interest and rights of the person concerned. The processor must also check beforehand whether the same result cannot be achieved with less data.

Overview Personal data
In the dashboard, via Administration > Overview Personal data, you can see a complete and current overview of all data processed by iRaiser for the website. This is governed by the concluded Collaboration Agreement or the General Terms and Conditions for the protection of personal data.
A distinction is made between the personal data that iRaiser processes by default and the, for this website, specific personal data from set-up forms. You can have an Excel file generated from these via the Download button. This is sent by e-mail to the e-mail address of the site administrator requesting the download and can be retrieved there via a link. If desired, you can also filter the data by:

All data
The additional form data (additional questions)
The default data (without the extra questions)

Exporting personal data: transfer
Exporting personal data, also known as transmission, is a form of processing personal data. The conditions described above apply to it in full. In addition, depending on the country to which the data is transferred, additional conditions apply.
What are the rights of data subjects?
The GDPR also grants rights to individuals whose data is processed:

Right of inspectionThis right allows everyone to check whether, and in what way, their data are processed.

Right of rectification and supplementation and/or restriction of processingWhen someone has used their right of inspection and comes to the conclusion that their data needs to be corrected, they can submit a request to that effect to the data controller.

Right to oblivionThe data subject may object to certain forms of data processing, as a result of which the processing of his personal data may have to be stopped.

Right to data portabilityThis is the ability to take data from one platform to another platform. 

The Controller (read: our client) must ensure that these rights are met. We as iRaiser only fill a role in this after consultation and approval from our customer. Thus, we have built functionalities within the iRaiser framework that largely automate the processes for the above rights. This is described in the agreement we enter into with a client.
Express consent
When and Users give permission (consent) for the storage of personal data anywhere within the iRaiser platform, a number of things are stored in the database to be able to resolve any dispute later. This explicit consent is also called informed consent or informed consent.
This explicit consent is also called informed consent.
The following data will be stored

id of the user (to retrieve the information)
consent text (which can be managed in the dashboard)
date/time
version number of the general terms and conditions
version number of the cookie statement
version number of the privacy settings

data subjects' rights
Every person whose personal data is stored has a number of different rights under the GDPR legislation to view or delete his/her data. Below we explain how we handle the different rights within iRaiser and what you or the Users can/should do to make use of these rights.
Users with an account can log in via the dashboard itself to exercise these rights. One does this by going to Accounts > Data protection when logged in:
 
Following this, they enter the dashboard where everything is explained about their rights and they can request different downloads for each right:

 
 
Right of access 

This right allows everyone to control whether, and how, their data is processed.
Procedure Users
Users can use the dashboard (see image above) to download their own archive containing all their data. After clicking on the button Download my archive , the user receives a message "Archive is being created now. You will soon receive an e-mail containing a link to download your archive." The link in the e-mail is valid for 24 hours.
Procedure Clients
When a customer addresses you and does not want to or cannot log into the dashboard himself, you (customer) can do so.
To do so, go to Accounts > Users and click on the three dots behind the relevant user and go to Data Protection: 

If a contributor asks this question then a request must be sent by you (customer) in writing on behalf of the requestor(consumer) to iRaiser via iRaiser's support desk.
After receiving the request, iRaiser will contact the customer to verify the request. In doing so, iRaiser asks for identification of the customer which is recorded in a logging.
After verification of the request, iRaiser will, within 5 working days, collect all the data of the requester (consumer) and bundle it in a password-protected zip file.
The password-protected zip file will be sent by iRaiser to the customer by secure WeTransfer.
We will send the corresponding password to open the zip file by SMS.
Right to rectification and completion and/or restriction of processing
 
When someone has used their right of inspection and comes to the conclusion that their data needs to be corrected, they can submit a request to that effect to the person responsible for data processing; the Controller (read: you as iRaiser's customer of iRaiser). You can already adjust a lot of data yourself via the dashboard at fer the user's request.
Should you not be able to change the data via the dashboard please contact support  via a written request on behalf of the applicant(consumer).  After receiving the request, iRaiser will contact you as customer to verify the request. In doing so, iRaiser will ask for identification of the customer which will be logged. After verifying the request, iRaiser will change the data within 5 working days and notify the customer accordingly.
Right to erasure

Users with accounts can request the deletion of their personal data themselves. After clicking the "Delete personal data" button, they will receive an email about this and can still withdraw the request within a week. After that, all data will be irrevocably deleted. 
You as a customer can also trigger this customer request via the dashboard:
To do so, go to Accounts > Users and click on the three dots behind the user in question and go to Data Protection.
If a user cannot log in themselves or does not have an account, we can do so at the klnat's request. 
At the request of Data Subject (End User):
There are three possibilities for this:

The data subject/end user addresses the request to the customer. Customer orders deletion to iRaiser;
The affected/end user uses the option for deletion of his/her personal data via the iRaiser Dashboard (option: Data Protection).
The affected/end user addresses the request directly to us.

iRaiser deletes Personal Data on dedicated servers and any hosted servers and from (internal) mailboxes, and other systems completely and irrevocably within 14 working days after being ordered to do so by customer. Within 30 days, Personal Data will be deleted from backup copyëns and from backup files.
Upon termination of contract:
If it is established after the end of the contract that the customer possesses all acquired Personal Data, iRaiser will completely and irrevocably delete all Personal Data on dedicated servers and any hosted servers and from (internal) mailboxes within 14 working days of being ordered to do so by the customer. Within 30 days, Personal Data will be removed from backup copyëns and from backup files.
Netherly 3 months after termination of the agreement, iRaiser will completely and irrevocably anonymise all acquired Personal Data, whether or not it has received an order to do so from  the customer. iRaiser will inform Customer two weeks prior thereto.
The account manager (sales consultant) of the relevant customer is responsible within iRaiser for initiating this procedure. 
Right to data portability
When a user wants to take their data with them, they can do so by downloading a file containing their data. This works exactly the same as with the Right of Inspection. 
Procedure Clients
If a customer contacts you and does not want to or cannot log into the dashboard themselves, you (customer) can do so.
To do so, go to Accounts > Users and click on the three dots behind the relevant user and go to Data Protection.
If a contributor asks this question then a request must be sent by you (customer) in writing on behalf of the requestor(consumer) to iRaiser.
After receiving the request, iRaiser will contact the customer to verify the request. In doing so, iRaiser will ask for identification of the customer which will be recorded in a logging.
After verification of the request, iRaiser will, within 5 working days, collect all data of the requester (consumer) and bundle it into a password-protected zip file.
The password-protected zip file will be sent by iRaiser to the customer via secure WeTransferPlus.
The corresponding password to open the zip file will be sent in a separate email.
After verification of the request, iRaiser will contact the customer to collect and bundle all data of the requester (consumer) into a password-protected zip file.
Questions?
Do you still have questions about the GDPR within iRaiser after reading this information? Then send an email to iRaiser

It is possible to track visitor behaviour on the iRaiser website, through Google Analytics. You can also have tracking pixels added by a support person upon request.
Via Integrations > Google Analytics you can add a G-ID. From then on, measurements will come in to the linked GA4 property. You can find out the G-ID as follows:
Click on Data streams:

 
Then click on the url:

On the top right you will see the ID:

Visual ID:
Add the G-ID.
 
Datalayer
In GA, we have added a data layer. Here you can see examples of the datalayer after a Donations on an action page and in the Sign up flow:
Example of the datalayer after donation on an action page:
{"transaction_id": "T_0168de416b8d87cb47af12270e6a2a6cd6243c1f","affiliation": "iRaiser","value": "60. 0","currency": "CHF","payment_type": "ideal","items":"{"item_id": "D_0168de416b8d87cb47af12270e6a270a6cd6243c1f","item_name": "Donation on action by Henk Vries","item_brand": "iRaiser","item_category": "Fundraisers","item_category_2": "henk-vries-2","item_category_3": "Private","price": "60. 0","quantity": 1},{"item_id": "TC_0168de416b8d87cb47af12270e6a2a6cd6243c1f","item_name": "Transaction costs","price": "2.0","quantity": 1}]}
&&">"item_category_3": "private","price": "60.
 
And after the Sign up flow:
{"transaction_id": "T_6a52a2e56689d38fc0dd3416869060e3367f57e3","affiliation": "iRaiser","value": "65. 0","currency": "EUR","payment_type": "ideal","coupon": "Discount code (as used)""items":[{"item_id": "D_57ef9a1aed94fe3129f995492a4b97f0b7bcfdb8","item_name": "Start donation","item_brand": "iRaiser","item_category": "Action","item_category_2": "john-doe","price": "15. 0","quantity": "1"},{"item_id": "RF_57ef9a1aed94fe3129f995492a4b97f0b7bcfdb8","item_name": "Registration fee","item_variant": "This is Registration fee","price": "50. 0","quantity": "1"}, {item_id: "WI_Webshop item name",item_name: "Webshop item title",item_variant: "Item variant (as present)",price: "15.0",quantity: "1"}]}
 
 

General target urls
Our flows for starting fundraisers and donating largely follow a fixed sequence. In order to measure things even better, for instance in your own Google Analytics, the flow for starting an fundraiser and donating is described below.
Below you need to replace <Mainurl> with the url of your platform.
Good to know is that the url may be different. If your site uses sub sites (i.e. an extra layer above campaigns) then the main url will also be different. It will look like this: <sub site name.Mainurl> and replaces <Headurl> in the flow below, if you want to measure the flow at sub site level.
If you want to set up a measurement in analytics, you can replace the ID and fundraiser url with .*Example:https://demo1.kentaa.nl/actie/.*/donate/.*/thanksHere you replace <fundraiser-url> and <ID> with .* to capture this.
Click on the link below to go directly to the relevant flow
1. Start fundraiser

Starting general fundraiser at site level

Individual
Create a team
Team member

Starting fundraiser for a campaigns

Individual
Create a team
Team member

2. Donate

General donation
Donate to a campaign
Donate to an fundraiser
Donate to a team
Donating to a sub site

1. Start fundraiser
https://<Hoofdurl>/come-in-fundraiser/choose--> choice page for which you want to start an fundraiser. This can be at website level, for a sub site or for campaign (or a combination of these)
a. Start general fundraiser at site level
https://<Hoofdurl>/subscribing is redirected to https://<Hoofdurl>/participate/how-to-participate -> choose between participating as an individual, team or team memberWherever mandatory is indicated, this step always returns in the registration flow. If it is optional, this step may not appear in your application flow, depending on the configuration.
i. Individual

Subscribe

https://<Mainurl>/participate/how-to-participate --> choice page individual, team, team member (mandatory)
https://<Hoofdurl>/participate/who-are-you --> enter personal data (mandatory)
https://<Hoofdurl>/participate/registration --> choose registration fee (optional)
https://<Headurl>/participate/choose-activity --> choose activity (optional)The above steps can be changed in terms of order in the dashboard under settings > login flow, so they may be different for you.
https://<Hoofdurl>/participate/fundraising-page --> create personal page (mandatory)
https://<Mainurl>/participate/extra-questions --> additional questions (optional)
https://<Hoofdurl>/participate/webshop --> webshop (optional)
https://<Headurl>/participate/start-donation --> make start-donation? (optional)
https://<Hoofdurl>/participate/summary --> overview page with your total order (mandatory)Add another person (optional)

Here you enter the flow again but with /2 after the url, for example:https://<Headurl>/participate/who-are-you/2

Rounding up:

https://<Hoofdurl>/participate/complete --> how would you like to pay? (mandatory)
https://<Hoofdurl>/participate/done --> payment succeeded (mandatory)
https://<Mainurl>/action/fundraiserurl--> then return to the fundraising page you just created (replace fundraiserurl with the url of the page, optional)

ii. Create team
This flow has the same structure. However, there is an extra step in it, which is in bold.

Subscribe

https://<Mainurl>/participate/how-to-participate --> choice page individual, team, team member (mandatory)
https://<Hoofdurl>/participate/who-are-you --> enter personal data (mandatory)
https://<Hoofdurl>/participate/registration --> choose registration fee (optional)
https://<Headurl>/participate/choose-activity --> choose activity (optional)The above steps can be changed in terms of order in the dashboard under settings > login flow, so they may be different for you.
https://<Hoofdurl>/participate/team-page --> create team page (mandatory)
https://<Hoofdurl>/participate/fundraising-page --> create personal page (mandatory)
https://<Mainurl>/participate/extra-questions --> additional questions (optional)
https://<Hoofdurl>/participate/webshop --> webshop (optional)
https://<Headurl>/participate/start-donation --> make start-donation? (optional)
https://<Hoofdurl>/participate/summary --> overview page with your total order (mandatory)Add another person (optional)

Here you enter the flow again but with /2 after the url, for example:https://<Hoofdurl>/participate/who-are-you/2

Rounding up:

https://<Hoofdurl>/participate/complete --> how would you like to pay? (mandatory)
https://<Hoofdurl>/participate/done --> payment succeeded (mandatory)
https://<Mainurl>/team/teamurl --> then return to the team page you just created (replace team-url with the url of the page, optional)

iii. Team member
There is also an extra step here, which is in bold

Subscribe

https://<Headurl>/participate/how-to-participate--> choice page individual, team, team member (mandatory)
https://<Hoofdurl>/join/team-member --> select team you want to join (mandatory)
https://<Hoofdurl>/participate/who-are-you --> enter personal data (mandatory)
https://<Hoofdurl>/participate/registration --> choose registration fee (optional)
https://<Mainurl>/participate/choose-activity --> choose activity (optional)The above steps can be changed in terms of order in the dashboard under settings > login flow, so they may be different for you.
https://<Hoofdurl>/participate/fundraising-page --> create personal page (mandatory)
https://<Mainurl>/participate/extra-questions --> additional questions (optional)
https://<Hoofdurl>/participate/webshop --> webshop (optional)
https://<Headurl>/participate/start-donation --> make start-donation? (optional)
https://<Hoofdurl>/participate/summary --> overview page with your total order (mandatory)Add another person (optional)

Here you enter the flow again but with /2 after the url, for example:https://<Hoofdurl>/participate/who-are-you/2

Rounding up:

https://<Hoofdurl>/participate/complete --> how would you like to pay? (mandatory)
https://<Hoofdurl>/participate/done --> payment succeeded (mandatory)
https://<Mainurl>/action/fundraiserurl--> then return to the fundraising page you just created (replace fundraiserurlwith the url of the page, optional)

 
B. Starting fundraiser for a campaign
 
i. Individual

Subscribe

https://<Hoofdurl>/project/<Campaign name>/participate/how-to-participate --> choice page individual, team, team member (mandatory)
https://<Hoofdurl>/project/<Campaign name>/participate/who-are-you--> enter personal data (mandatory)
https://<Hoofdurl>/project/<Campaign name>/participate/registration --> choose registration fee (optional)
https://<Hoofdurl>/project/<Campaign name>/participate/choose-activity --> choose activity (optional)The above steps can be changed in terms of order in the dashboard under settings > submission flow, so they may be different for you
https://<Mainurl>/project/<Campaign name>/participate/fundraising-page --> create personal page (mandatory)
https://<Hoofdurl>/project/<Campaign name>/participate/extra-questions --> additional questions (optional)
https://<Hoofdurl>/project/<Campaign name>/participate/webshop --> webshop (optional)
https://<Headurl>/project/<Campaign name>/participate/start-donation --> make start-donation? (optional)
https://<Hoofdurl>/project/<Campaign name>/participate/summary --> overview page with your total order (mandatory)Add another person (optional)

Here you enter the flow again but with /2 after the url, for example:https://<Hoofdurl>/project/<Campaign name>/participate/who-are-you/2

Rounding up:

https://<Hoofdurl>/project/<Campaign name>/participate/complete --> how would you like to pay? (mandatory)
https://<Hoofdurl>/project/<Campaign name>/participate/done --> payment was successful (mandatory)
https://<Mainurl>/action/fundraiserurl--> then return to the fundraising page you just created (replace fundraiserurl with the url of the page, optional)

ii. Create team
This flow has the same structure. However, there is an extra step in it, which is in bold.

Subscribe

https://<Hoofdurl>/project/<Campaign name>/participate/how-to-participate --> choice page individual, team, team member (mandatory)
https://<Hoofdurl>/project/<Campaign name>/participate/who-are-you --> enter personal data (mandatory)
https://<Hoofdurl>/project/<Campaign name>/participate/registration --> choose registration fee (optional)
https://<Mainurl>/project/<Campaign name>/participate/choose-activity --> choose activity (optional)The above steps can be changed in order in the dashboard under settings > login flow, so they may be different for you.
https://<Hoofdurl>/projects/<Campaign name>/participate/team-page --> create team page (mandatory)
https://<Mainurl>/project/<Campaign name>/participate/fundraising-page --> create personal page (mandatory)
https://<Hoofdurl>/project/<Campaign name>/participate/extra-questions --> additional questions (optional)
https://<Hoofdurl>/project/<Campaign name>/participate/webshop --> webshop (optional)
https://<Headurl>/project/<Campaign name>/participate/start-donation --> make start-donation? (optional)
https://<Hoofdurl>/project/<Campaign name>/participate/summary --> overview page with your total order (mandatory)Add another person (optional)

Here you enter the flow again but with /2 after the url, for example:https://<Hoofdurl>/project/<Campaign name>/participate/who-are-you/2

Rounding up:

https://<Hoofdurl>/project/<Campaign name>/participate/complete --> how would you like to pay? (mandatory)
https://<Hoofdurl>/project/<Campaign name>/participate/done --> payment was successful (mandatory)
https://<Mainurl>/team/teamurl --> then return to the team page you just created (replace team-url with the url of the page, optional)

iii. Team member
There is also an extra step here, which is in bold

Subscribe

https://<Hoofdurl>/project/<Campaign name>/participate/how-to-participate --> choice page individual, team, team member (mandatory)
https://<Hoofdurl>/project/<Campaign name>/participate/team-member --> select team you want to join (mandatory)
https://<Hoofdurl>/project/<Campaign name>/participate/who-are-you --> enter personal data (mandatory)
https://<Hoofdurl>/project/<Campaign name>/participate/registration --> choose registration fee (optional)
https://<Mainurl>/project/<Campaign name>/participate/choose-activity --> choose activity (optional)The above steps can be changed in order in the dashboard under settings > login flow, so they may be different for you.
https://<Mainurl>/project/<Campaign name>/participate/fundraising-page --> create personal page (mandatory)
https://<Hoofdurl>/project/<Campaign name>/participate/extra-questions --> additional questions (optional)
https://<Hoofdurl>/project/<Campaign name>/participate/webshop --> webshop (optional)
https://<Headurl>/project/<Campaign name>/participate/start-donation --> make start-donation? (optional)
https://<Hoofdurl>/project/<Campaign name>/participate/summary --> overview page with your total order (mandatory)Add another person (optional)

Here you enter the flow again but with /2 after the url, for example:https://<Hoofdurl>/project/<Campaign name>/participate/who-are-you/2

Rounding up:

https://<Hoofdurl>/project/<Campaign name>/participate/complete --> how would you like to pay? (mandatory)
https://<Hoofdurl>/project/<Campaign name>/participate/done --> payment was successful (mandatory)
https://<Mainurl>/action/fundraiserurl--> then return to the fundraising page you just created (replace fundraiserurl with the url of the page, optional)

2. Donate
If you click donate then, if there is a choice, you will be taken to the following url:https://<Mainurl>/donate/choose --> If there is a choice then choose here what you want to donate to
Here you have a choice between a general donation, a donation to a campaign, a donation to an fundraiser, a donation to a team and possibly a donation to a sub site. The choice depends on the settings of the platform.
If you donate to an fundraiser, team or campaign on a sub site then the main url below should read as <sub site.mainurl>
a. General donation

https://<Hoofdurl>/donate --> choose amount and enter personal data
https://<Headurl>/donate/<ID>/thanks --> thanks page you return to after paying.
https://<Hoofdurl>/donate/<ID>/share --> page where you can share that you donated.
https://<Hoofdurl>/donate/<ID>/periodic-donation --> page where you can indicate to become a structural donor (optional)

b. Donate to campaign

https://<Hoofdurl>/project/<Campaign-url>/donate --> choose amount and enter personal data
https://<Mainurl>/project/<Campaign-url>/donate/<ID>/thanks --> thanks page you return to after paying.
https://<Mainurl>/project/<Campaign-url>donate/<ID>/share --> page where you can share that you donated.
https://<Hoofdurl>/project/<Campaign-url>/donate/<ID>/periodic-donation --> page where you can indicate to become a structural donor (optional)

c. Donating to an fundraiser

https://<Mainurl>/action/<fundraiserurl>/donate --> choose amount and enter personal data
https://<Mainurl>/action/<fundraiserurl>/donate/<ID>/thanks --> thanks page you return to after paying.
https://<Mainurl>/action/<fundraiserurl>/donate/<ID>/share --> page where you can share that you donated.
https://<Mainurl>/action/<fundraiserurl>/donate/<ID>/periodic-donation --> page where you can indicate to become a structural donor (optional)

d. Donating to a team

https://<headurl>/team/<team-url>/donate --> choose amount and enter personal details
https://<Mainurl>/team/<team-url>/donate/<ID>/thanks --> thanks page you return to after paying.
https://<headurl>/team/<team-url>donate/<ID>/share --> page where you can share that you donated.
https://<Hoofdurl>/team/<team-url>/donate/<ID>/periodic-donation --> page where you can indicate to become a structural donor (optional)

e. Donating to a sub site

https://<sub site.Hoofdurl>/donate --> choose amount and enter personal details
https://<sub site.Mainurl>/donate/<ID>/thanks --> thanks page you return to after paying.
https://<sub site.Hoofdurl>/donate/<ID>/share --> page where you can share that you donated.
https://<sub site.Hoofdurl>/donate/<ID>/periodic-donation --> page where you can indicate to become a structural donor (optional)

 

The following changes went live on 20 October 2022 (iRaiser Premium and iRaiser Forms) and on 18 October 2022 (Digicollect): (Update: some more changes went live on 20 June 2023. See point four of this article)
Content:iRaiser Premium

General terms and conditions and privacy
Opt-ins have become soft opt-ins

Keep informed
To fill in your phone number
Newsletter

Enter whether data may be shared
Update 20 June 2023: Adjustment in showing donor name

Digicollect

General terms and conditions and privacy
Opt-ins have become soft opt-ins

Mobile number
Newsletter

Enter whether data may be shared

iRaiser Premium (incl. iRaiser Forms):
In the Academy of 20-01-2022, the changes were discussed:

iRaiser Academy 20-01-2022
0:00 Introduction 1:32 A/B testing of donation amounts12:17 A/B testing summary and questions16:01 Badges for Action Starters 20:12 Badges summary and questions26:54 New SUMO34:37 SUMO summary 37:50 Consent Registration for Telecom Act*43:50 Consent registration summary and questions

 
1. General terms and conditions and privacy
.
According to the Consumer & Market Authority, general terms and conditions are valid if the consumer knows they apply at the time he or she purchases the service from you. So you must make the general terms and conditions available and clickable in the sign-up and donation flow. - Source
When creating an action én when making a donation, Users no longer have to agree to the terms and conditions. You automatically agree to these when making the Donations or when continuing in the flow:

As you now also automatically agree to the privacy statement, we have added this to the api as well. This will be automatically saved as consent for newly created Fundraisers after 20 October. For old action starters/donors, this data is not saved retroactively.
2. Opt-ins have become soft opt-ins
Normally, a consumer must give an active opt-in at the time he or she wants to receive a newsletter or to be contacted by phone. The exception to this rule is the concept of 'customer relationship'. Since 1 July 2021, the concept of 'customer relationship' has been broadened for charities. Besides a financialële transaction, a volunteer and event participant is also counted under a customer relationship. In other words, someone who takes action on your behalf may be seen as a customer relationship. For a donor, this was already the case as they completed a financialële transaction. - Source
We replaced several opt-ins with soft opt-ins for the above reason. Whereas previously you had to tick yourself that you want to be kept informed of News updates, for example, this tick is now already on by default. This also applies to the two different tick boxes aimed at telephone solicitation. Here it is good to know that you, the customer, can change these consent texts yourself in the dashboard. We have turned on the checkmark by default in these places:
To keep informed
This is what you will see after making a Donations:

b. When entering your phone number in the Sign up flow or Donate
We can turn on the second tick about marketing purposes at your request.

c. Newsletter (when donating)

3. Indicating whether data may be shared
Contact information was shared (at the time it was entered by the donor) with the action starter. As this is not always desirable, we chose to add an additional soft opt-in when making a donation to an action, team, company on Campaign:

You, as a donor, can choose not to share details with the initiator of the action. This can be:

The action initiator
The team captain
The company manager
The project manager

If you uncheck this box (which is on by default) then that data is not shared with the action starter. Who will see it returned as Anonymous:

In the Excel file, an additional column has been added, at the very end, with 'Share contact information':

 
You as site administrators can still view this data.
4. Update 20 June 2023: Adjustment in show first name donor
Since 20 June 2023, a change has gone live that relates to the following scenario:
- You make a Donation and, when Donating, choose not to share your details with the initiator.
Previously, the name on the front end was then always shown as anonymous. With the logic that it's strange not to share your details with the initiator of the action, but that they could then still see at the front end who had donated.
We noticed, however, that it raised a lot of questions and confusion among donors. Especially because they were under the impression that showing the name was only linked to the checkbox  "Display my name on the website. "
We have now made that showing of name dependent only on the option "Shield my name on the website." If that tick is not turned on, you will see the donor's name on the website.
To clarify, we have now changed the text on sharing with the initiator to: "Sharing my contact information with the initiator of this action, so they may send me a thank you, for example."
We hope this makes it a lot clearer for the donor. This is a change that took effect from 20 June. Older Donations have not been made visible retroactively. In case you had an old donation where it was indicated that the data should not be shared with the initiator, the check mark at name blocking has now been switched on for each old donation. If you have a donor who wanted this to be shown, you can now change this in the system by looking up the donation and setting the checkmark to 'do not hide'.
Digicollect
In the academy of 6-10, the changes were discussed:

Digicollect Academy 06-10-2022
02:45 - Poules 23:45 - Recent updates 30:00 - GDPR changes 35:04 - Digicollect action month

 
1. General terms and conditions and privacy
According to the Consumer & Market Authority, general terms and conditions are valid if the consumer knows they apply at the time he or she purchases the service from you. So you should make the general terms and conditions available and clickable in the sign-up and donation flow. - Source
When creating a collection box én when making a donation, Users no longer have to agree to the terms and conditions. You automatically agree to these when making the donation or when continuing in the flow:

2. Opt-ins have become soft opt-ins outs
Normally, a consumer must give an active opt-in at the time he or she wants to receive a newsletter or to be contacted by phone. The exception to this rule is the concept of 'customer relationship'. Since 1 July 2021, the concept of 'customer relationship' has been broadened for charities. Besides a financialële transaction, a volunteer and event participant is also counted under a customer relationship. In other words, someone who takes action on your behalf may be seen as a customer relationship. For a donor, this was already the case as they completed a financialële transaction. - Source
We replaced several opt-ins with soft opt-ins for the above reason. Whereas previously you had to tick yourself that you want to be kept informed of News updates, for example, this tick is now already on by default. This also applies to the two different tick boxes aimed at telephone solicitation. Here it is good to know that you, the customer, can adjust these consent texts yourself in the dashboard.
We have turned on the tick by default in these places:
When entering the mobile number
When creating a collection box, if you enter a phone number both checkboxes for approach for tips or marketing purposes are on by default. We can enable the functionality to show the second tick for you:

Newsletter
When donating, if you leave your email address then opt-in for the newsletter is also already automatically on:

 
3. Indicate whether data may be shared
Contact information was shared (at the time it was filled in by the donor) with the collector. As this is not always desirable, we chose to add an additional soft opt-in when making a Donations: 'My contact information may be shared with the collector.' :

If you uncheck this box (which is on by default) then that data is not shared with the collector. It will see them as Anonymous in the automatic Emails:

In the Donations overview that a collector can see, the donation can also be seen as anonymous:

 
You as site administrators can still view this data.

What is included in the Monthly reports?
Directly after the end of a calendar month, a financialële Monthly report is available within the iRaiser Dashboard. The financialële Monthly reports contain a sum of all income and expenses in the month in question. It includes the following transactions:

transactions that have been given the status 'paid' in the month in question 
only transactions settled via the online checkout
successful PayPal and Tikkie transactions are also included in the statistics

The Monthly reports can be viewed by month and downloaded by the site administrator in an excel file.
What do the columns mean?
All black amounts are income and all red amounts are expenses.
Donated
This includes donation income. Both regular donations and any start-up donations. It is a sum of the donation amounts. This does not include contributions to transaction fees, registration fees and webshop revenue.
Registration fee
This includes receipts from paid registration fees.
Webshop
This includes receipts from webshop items purchased at registration.
Total refunded/refunded
The total amounts refunded by the site administrator and the total refunded by an end user, respectively.
Transaction fees including VAT
This is the cost of the payment service provider including VAT. PLEASE NOTE: this is an eo good indication of these costs. The costs may differ slightly from the actual payment service provider costs. For the actual payment service provider costs, please refer to the statement of these costs by the relevant payment service provider that can be seen in the payment service provider's dashboard. These transaction fees are automatically deducted from payouts by the payment service provider. 
iRaiser fees incl. VAT
This refers to iRaiser's variable licence fees including VAT. These are calculated automatically per transaction based on the applicable agreements. In case of a volume tier this is automatically taken into account. The corresponding invoice of these costs can be downloaded via the download button. These variable iRaiser licence fees are automatically deducted from the payouts by the payment service provider. unless other agreements have been made. 
Split by Sub site and Campaign
At th top of the report are the totals for the entire website. A breakdown is then given on that:

All transactions directly below the website homepage, broken down by Campaigns. Below that are the income from transactions on Fundraisers and Team pages created directly under the homepage and therefore not covered by a Campaign. Finally, general Donations made directly on the website's homepage. At the bottom there is a subtotal of all transactions directly under homepage, i.e. not under a Sub site or Campaigns.  
In case of using the iRaiser Sub site module: all transactions per Sub site. For each Sub site, a breakdown of transactions per Campaigns is also given. Below that are the income from transactions on campaign and team pages that were created directly under the Sub site page and thus do not fall under a campaign. Finally, general Donations made directly on the website's Sub site page. At the bottom is a subtotal of all transactions directly under the relevant Sub site.

An A/B test is a form of split testing in which you can test multiple variants against each other to see which variant has the best conversion rate. The aim is to use the test to measure which suggested donation amounts yield the most and therefore increase conversion.
Content article

Baseline

Suggested donation amounts
Information about baseline

A/B test

Setup A/B test
Results A/B test

See here also the explanation as given at the iRaiser Academy on 20 January 2022

 
Baseline
Suggested donation amounts
You can A/B test on the donation flow within the Kentaplatform. Via Settings > Set donation amounts you can set different suggested donation amounts. The currently set amount is your baseline. The baseline is the basis from which you measure and compare split tests. 
When someone makes a donation you will see the suggested donation amounts:
 
This can also include text to give more interpretation of what you are doing with the amount. For example:

 
When adjusting donation amounts, at the bottom you have to indicate whether you want to keep the current baseline or create a new one.
 
If you create a new baseline it will start measuring from that point on. You can see all its results via Settings > A/B testing. If you keep the current baseline, the adjustments are taken into account, but the baseline in terms of measurement remains intact. This is useful if, for example, you have made a typo and want to adjust it. 
 
Information about baseline
If you go to Settings >A/B testing you will always see the huige baseline at the top:
 
You can see here:

Active sinceThe moment when the chosen amounts were set
Chosen amountsThe chosen donation amounts. If you move over them you will also see the description
Number of visitsThe number of visitors who came to the donation form
Number of DonationsThe number of times the donation has been completed
ConversionThe percentage of visitors who completed the donation
Average donation amount The average amount made per donation
Days activeThe number of days these donation amounts are like this
AchievementsYou can see here whether that is the baseline or a split test group

You can click on the gear icon and then view details to see more specific information about the Donations:
 
That's all information about the current baseline. 
A/B test 
Set test
You start an A/B test by clicking on "start A/B test". All currently set data will then be filled in automatically:

In the A/B test, variants can be specified for:

the amounts
the order of the amounts
the mouse-over text

You can do two types of A/B test:

Test against current baselineWhere you change only Group A or Group B, testing against the current baseline
Test two separate groupsWhere you change both Group A and B, testing two new groups against each other.

From then on, donors randomly see the suggested amounts belonging to Group A or B. Suppose you have set these amounts:
And you click save then the test starts:

From then on, visitors who go to the donation form will either see the donation amounts as set at A, or from B. You'll see these randomly. You can't change the suggested donation amounts while an A/B test is running.
Results test
You can abort a test yourself by going to the cog above the test and choosing 'Abort'. And otherwise it is automatically stopped when 100 Donations have been made to both groups. Because you can get a group randomly, it may be that, for example, 130 Donations have been made to one group and 100 to the other.
If the test is stopped then the results will appear in the history, as for example in the case of this test that was manually aborted:

Interpreting the results is also important. It may seem that one group has better results, but if there is a very high Donations in one group it distorts the picture. We recommend looking at these critically and you can choose to set one of the groups that has a better conversion rate as a new baseline via Settings > Suggested donation amounts.

Within the platform, there are various options for viewing statistics. For example, you can export Donations, Fundraisers, Teams, Campaigns and Sub sites, as well as view Monthly reports. We also have ready-made overviews of relevant overall statistics and more on this in this support article.
Figures
The key figures can be found at the website level under Analytics > Download statistics. Here you can select a certain period for which you want to see the key figures and then click 'Create Excel file'. This will give you an Overview of the relevant key figures (the content may vary based on the content of your platform). These key figures can be useful to analyse the data on the platform and make adjustments if necessary. Specifically, you will see key figures in the following categoriesën (if present on the platform): PaymentsDonorsDonations by deviceDonations by payment method Average donation amountNumber of donationsPay Later Actions (including closed and invisible)TeamsProjectsSegmentsTransactions
Analytics
At each level you will see Analytics. These are graphically displayed statistics on the following components:
Number of DonationsAverage donatedNumber of FundraisersSmile of participants
And if used on the platform:Selected ActivitiesSelected Registration fees Returning participants
You can select a period you want to see the Analytics from at the top and you can optionally choose to download the statistics as a pdf.
If you hover over the Analytics itself, you will see more information about it. Under 'Number of Donations', for example, you can see how many donations have been made.

 
Statistics from underlying levelsBy default, statistics from underlying levels are turned on. This means that all statistics are shown. If you turn this off then you only get the statistics of that level. Concretely, for example, this looks like this:You are at the website level and also have Campaigns. If you don't choose to show statistics from underlying levels then you will only see statistics done at the website level. For example, general Donations. You won't see a donation made on a Campaign then.
Statistics
On each level you will also see general statistics:
For example, you can immediately see the average donation amount, how many Donations there are and the amount raised. These statistics appear at every level. For example, for a Campaign specifically, you can immediately see all relevant information. In addition, action starters, for example, also see relevant statistics for them.
Also here you see that toggle 'Also show statistics of underlying levels' and it works in the same way. With this, you differentiate between all statistics, and statistics that are directly below that level (which you are currently on). 
Statistics with this icon are clickable. This shows you graphs that are also clickable.