Extensions Directory
Extensions are installable packages which give CiviCRM new functionality, and this directory provides a centralized list of extensions which the CiviCRM community has created. This listing displays CiviCRM extensions that work on all Content Management Systems (CMS).
The newest extensions · Create an extension · Add an extension to this directory
Simple conversion tracking for your contribution and event pages.
The idea is that information from CiviCRM thank you pages should be made available when a transaction has been successfully completed.
The idea is that information from CiviCRM thank you pages should be made available when a transaction has been successfully completed.
This extension adds google analytics tracking to contribution/event registration pages.
Control the profile visibility using CMS user roles.
This will control the accessibility of your profile based on your role, even if you give permissions to the CMS like profile create, 'profile listings', etc.
Each profile can have its own controls for accessibility.
This will control the accessibility of your profile based on your role, even if you give permissions to the CMS like profile create, 'profile listings', etc.
Each profile can have its own controls for accessibility.
Collect important mailing statistics, such as open and click-through rates, without compromising individual user privacy by decoupling tracking events from specific contacts.
UTM Tracking is an extension to track the UTM Source, UTM Medium and UTM Campaign across various entities in CiviCRM such as Contributions, Recurring Contributions, Activities, Participants and Memberships.
For example this useful to track the effectiveness of an campaign. One can see how many donations came in or how many petitions are signed.
For example this useful to track the effectiveness of an campaign. One can see how many donations came in or how many petitions are signed.
Limit the number of custom fields per custom group to avoid database errors based on the size of the field and the type of collation of the column of custom fields.
This extension adds the ability to send google analyitcs events when a PayPal IPN is processed to enrich the data in google analytics.
This extension aims to be a toolkit to help you comply with the GDPR.
What does it do?
The core of this toolkit is a new custom group where you can store consent records with your contacts. These records can be explicit or implicit consent, opt-outs, and similar things.
It integrates neatly with the UI, and gives you some search and data entry helpers.
Each record has the following fields:
date and time
category (e.g. "newsletter")
source (e.g. "main website")
type (e.g. "opt-in", "opt-out", "soft opt-in")
In addition, there are also some optional fields for each consent record:
expiry date (consent expires after the given date/time)
terms and conditions. (the full text of the TOC that the user agreed to*)
note (in case you want to add a remark)
(*) it has a clever mechanism so that it doesn't store the same TOC text over and over.
How do I use this?
Since the actions or consequences derived from the collected data differ greatly between organisations, this toolkit doesn't do anything automatically. However, it can be used as a basis for further automation, e.g. by using the SQL Tasks extension to tag contacts for deletion if the basis for a contact's retention is not there anymore.
That's it?
Yes and no. There are some additional features that might interest you as a developer:
- There is a feature to make the communication preferences read-only, in case you want to derive them from the contact's consent record.
- There is a fully functioning API
- It defines a custom hook to be triggered if the consent records are modified for a contact. This way you can add code update the contact's permissions/subscripts/whatever right away.
What's next?
We'll keep on extending the built-in functionality of this extension, while aiming to keep it compatible with earlier versions. However, since the implementation of the GDPR is very specific to the individual organisation, this will never be "plug&play" solution for any user.
Feel free to raise ticket if you have a question.
What does it do?
The core of this toolkit is a new custom group where you can store consent records with your contacts. These records can be explicit or implicit consent, opt-outs, and similar things.
It integrates neatly with the UI, and gives you some search and data entry helpers.
Each record has the following fields:
date and time
category (e.g. "newsletter")
source (e.g. "main website")
type (e.g. "opt-in", "opt-out", "soft opt-in")
In addition, there are also some optional fields for each consent record:
expiry date (consent expires after the given date/time)
terms and conditions. (the full text of the TOC that the user agreed to*)
note (in case you want to add a remark)
(*) it has a clever mechanism so that it doesn't store the same TOC text over and over.
How do I use this?
Since the actions or consequences derived from the collected data differ greatly between organisations, this toolkit doesn't do anything automatically. However, it can be used as a basis for further automation, e.g. by using the SQL Tasks extension to tag contacts for deletion if the basis for a contact's retention is not there anymore.
That's it?
Yes and no. There are some additional features that might interest you as a developer:
- There is a feature to make the communication preferences read-only, in case you want to derive them from the contact's consent record.
- There is a fully functioning API
- It defines a custom hook to be triggered if the consent records are modified for a contact. This way you can add code update the contact's permissions/subscripts/whatever right away.
What's next?
We'll keep on extending the built-in functionality of this extension, while aiming to keep it compatible with earlier versions. However, since the implementation of the GDPR is very specific to the individual organisation, this will never be "plug&play" solution for any user.
Feel free to raise ticket if you have a question.
