Systeme.io
Verkkokurssikassa automatically activates your Systeme.io course after purchase by adding tags to the customer's contact, which trigger your Systeme.io Automations.
How It Works
- Systeme.io is enabled with an API key in the checkout's Course Platforms settings
- The customer pays at checkout
- Verkkokurssikassa creates the customer as a contact in Systeme.io (or finds the existing contact) and adds the configured tags
- Your Systeme.io Automations detect the tags and activate the course for the customer
- Optionally, the automations send the customer a welcome or access email
When a refund revokes access, Verkkokurssikassa removes the tags, allowing reverse automations to revoke course access.
Setup in Verkkokurssikassa
Before adding a Systeme.io post-purchase action, enable Systeme.io and enter your API key in the checkout's integration settings:
- Open the checkout and go to Settings → Integrations → Course Platforms
- Enable Systeme.io with the toggle switch
- Enter your Systeme.io API key (see Finding the API Key below)
- Save
Once enabled, the "Grant Systeme.io Access" action appears as an option when adding post-purchase actions to products and offers.
Finding the API Key in Systeme.io
The API key is found in your Systeme.io account under Profile (top right) → Public API keys. Click Create a new API key, give it a name (e.g. "Verkkokurssikassa"), and copy the generated key.
Action Settings
Add a "Grant Systeme.io Access" action to a product, offer, or checkout and fill in the following fields:
| Asetus | Kuvaus |
|---|---|
| Name | Internal name for the action, e.g. 'Grant Systeme.io Access – Neck & Shoulder First Aid Kit'. Only visible in the dashboard. |
| Tags | The Systeme.io tags to add to the customer's contact after purchase. Each tag can trigger a separate Systeme.io automation to activate the course. Tags are loaded from Systeme.io using the API key configured in checkout settings — create the tags in Systeme.io first. |
You need a separate "Grant Systeme.io Access" action for each course you want to activate. One action can add one or more tags — each tag can trigger a separate Systeme.io automation.
Setting Up Automations in Systeme.io
Courses in Systeme.io are activated through Automations. You need at least one automation per tag:
Granting access on purchase (required)
- In Systeme.io, go to Automations → Create
- Set the trigger to Tag added and select the tag you configured above
- Add an action: Grant access to a course and select the course
- Save and activate the automation
Revoking access on refund (optional)
This automation is only needed if you want to revoke course access directly from Verkkokurssikassa (e.g. when processing a refund).
- Create a second automation
- Set the trigger to Tag removed and select the same tag
- Add an action: Revoke access to a course and select the course
- Save and activate the automation
When you revoke access from the Verkkokurssikassa dashboard, Verkkokurssikassa removes the tags automatically. If you have created a "Tag removed" automation, it handles the actual course access revocation in Systeme.io.
Troubleshooting
If the action fails, the error message is visible in order management: open the order's side panel by clicking the order, and look at the Post-Purchase Actions section.
Common causes of failure:
- The API key is incorrect, expired, or missing the required permissions
- A tag was deleted in Systeme.io after the action was configured
- Systeme.io returned an API error (the error message is visible on the order)
Contact not tagged
If the purchase completes successfully but the customer does not receive course access, check that:
- The Systeme.io Automation is active and configured correctly
- The tags shown in the action settings match the tags used in the automation triggers
- The customer's contact appears in Systeme.io with the tags applied
Kajabi
Verkkokurssikassa automatically activates a Kajabi Offer after purchase by sending the customer's details to the Kajabi Offer's webhook URL.
Overview
Checkout links are the primary way to track sales by channel. The checkout also supports Google Tag Manager (incl. server-side GTM), Google Analytics 4, Meta Pixel, and Meta Conversions API. Tracking integrations are only activated with the customer's GDPR consent.