System page customization
Custom template of the unsubscribe page
Tracking page templates are located in the directory ak/static/trk/. If you need to reassign them, you need to put the modified templates in this directory and add custom. to the file name.
$ cd /opt/akd
$ cp ak/static/trk/unsubscribe.html ak/static/trk/custom.unsubscribe.html
$ nano ak/static/trk/custom.unsubscribe.html
...
$ ./akd onerestart procactions
The templates will be applied only when you restart the process procactions.
Description of the pages
| Template | Meaning |
|---|---|
unsubscribe.html | Page after unsubscribing, if it isn't specified in the message |
deprecated.html | The page of the expired web message |
not_found.html | Page for invalid links on tracking |
Custom notification templates
Custom notification templates are located in the directory templates/email/<CountryCode>/. As they will be overwritten during the upgrade, you can create files for them that override them. CountryCode determines the template language. If the language is not found, the default value will be EN (English).
You need to add custom. to the file name in order to define such a file:
$ cd /opt/akd
$ cp templates/email/RU/password.html templates/email/RU/custom.password.html
$ nano templates/email/RU/custom.password.html
...
$ ./akd restart --job_server
The templates will be applied only when you restart the process akd.
Template description
| Template | Level | Meaning |
|---|---|---|
content.json | all | Applies to all templates, contains headers, subject and reply-to addresses of letters |
template_all.html | all | Applies to all templates |
welcome.html | account, admin | Appears when the user with access is created |
password.html | account, admin | Password change by user or administrator |
complains.html | account | In case of exceeding the rates for complaints |
hardbounces.html | account | In case of exceeding the hardbounce indicators |
softbounces.html | account | In case of exceeding the softbounce indicators |
report_weekly.html | account | Weekly report of the user |
report_daily.html | account | Daily report of the user |
sendlimit.html | account | In case of exceeding the limit (tariff) for sending |
leadslimit.html | account | In case ofexceeding the limit (tariff) for the amount of data |
suspended.html | account | In case the account is inactive in the admin panel |
sender_problem.html | admin | During the process of setting up notification for sender in the administration panel |
Customization of form pages
All template files are located in the platform installation directory under /templates/form/v1/EN and /templates/form/v1/RU. Files in the .tpl format contain form templates and components used within those templates. The .html format contains standalone tables.
| File | Description |
|---|---|
| button.tpl | Template for displaying buttons. Controls their appearance and placement in the form. |
| content.json | File containing the form's data and structure — includes field descriptions, transition logic, texts, settings, etc. |
| user_code.tpl | A custom template designed to override the default form template. It is used to insert custom code into the <head>, <body>, and <footer> sections of the page. It also allows wrapping the main form content with additional HTML markup. |
| error.html | Page displayed when an error occurs while loading the form or if the link is invalid. |
| final.tpl | Template for the final page shown to the user after successful form submission. |
| form_fill.tpl | Template for the main form page where the user fills in the fields. |
| form.tpl | Main container template for the form. Includes basic HTML layout, structure, and links to other templates. |
| hidden.html | Displayed when the form is hidden from public access. Usually contains a message like "Form unavailable". |
| redirect.tpl | Template for the redirection page. |
Similar to other config files, you can create a copy of any of them, rename it to "custom.<original_name>", and use it instead of the original configuration.
Static tracking files
In some cases it can be useful to place static files on the tracking — the necessary files can be placed in the directory ak/static/trk/public/. This way, they will be available at the absolute path /static/ of your tracking. For example, this directory contains the cat.html file.