The video is in the works. Until then, the guide will get you there.
Step-by-step guide
What is in it for me?
Trustlytics sends your reports two ways: by email or by text. Email works out of the box. For text messages, you need someone who actually pushes the message into the mobile network. That is ASPSMS's job.
Short and honest: no ASPSMS, no SMS reports. Once the service is connected here, the "SMS" channel becomes selectable when you create a report. Before that, it stays grayed out.
And why texts when you already have email? The two have different jobs:
| Channel | What it is good for |
|---|---|
| Everything in detail, with a PDF to file and forward. The standard case. | |
| SMS | A quick pulse check on the go. Three to five numbers, one glance, done |
Text messages are especially handy for people who are rarely at a screen. Management, for example, who do not need the whole set of numbers, just an answer to one question: is it working?
Where to find Connect ASPSMS
In the top menu bar, click " (Settings)".
The Settings menu opens on the left. Choose "Services".
The Services page opens.
Under "Available services" you will see "ASPSMS". Click "Connect" there.
Opening an ASPSMS account
For a text message to go out at all, you need an account with ASPSMS. Behind it stands VADIAN.NET AG from St. Gallen, a registered Swiss telecommunications provider. So your data falls under Swiss data protection.
If you do not have an account yet, here is how to go about it:
- On the connect page you will find the link «Create an account with ASPSMS». That opens the sign-up in a new tab.
- Open your account there.
- Buy credits, meaning prepaid balance. That is what pays for every text you send later.
A few key facts, so you know what you are getting into:
| What | How |
|---|---|
| Coverage | Worldwide across more than 900 networks. The link "Check supported networks" shows you whether your target country is included. |
| Price | From around CHF 0.06 per text, depending on the destination country. |
| Payment | Credit card, PayPal, bank transfer, PostFinance, or Twint. |
| Credits | Bought in advance and they do not expire. |
Copying your ASPSMS Userkey and API password
Trustlytics needs two pieces of information from your ASPSMS account. Here is how to get there:
- Sign in to ASPSMS.
- In the main menu "Registered Users", click "API Credentials".
That page holds both items you are about to need: your Userkey and your API password. Best to leave the tab open, then you can copy both straight over.
Connecting ASPSMS to Trustlytics
Fill in the two fields:
| Field | What to enter |
|---|---|
| Userkey | Paste the Userkey you just copied from ASPSMS. This is not your email address. |
| Password | Paste your API password. Not the password you sign in to ASPSMS with. Trustlytics stores it encrypted, never in plain text. |
Then click "Save". "Cancel" discards your entry and takes you back to the Services page.
After saving, the service moves up under "Your connected services", with a green "Active" label. That is all there is to it.
ASPSMS connected
Back on "Services", ASPSMS now sits at the top under "Your connected services". You will see:
- The name ASPSMS with the green "Active" label.
- A small info table with Userkey and Password (masked, so never readable).
- Three buttons: Test connection checks your credentials, Edit reopens the form, Delete removes the connection.
What is possible now: In Settings under Reports, the "SMS" channel is selectable from here on. Before that it was grayed out. Your SMS reports then go out automatically, billed against your ASPSMS credits.
The connection test
The "Test connection" button knocks on ASPSMS's door with your credentials and checks whether it opens.
- Successful? Then the Userkey and API password are correct, and your SMS reports can go out.
- Failed? Then something is off, usually one of the two entries. Open "Edit" and go through them carefully.
Run this test right after connecting. That half minute saves you from wondering why no text arrived on Monday.
You cannot test endlessly back to back, though. Try too often, and you get the message "Too many connection tests. Please wait a few minutes." Take a breath, then it works again.
Editing credentials or removing the connection
Changing something: Click "Edit". The Userkey is already filled in, the password shows up masked. Type it in again and click "Save".
You mainly need this when you have changed your API password at ASPSMS. Update it here as well, otherwise sending fails silently. If you only change your sign-in password at ASPSMS, there is nothing to do here.
Removing the connection: Click "Delete" and confirm the safety prompt. ASPSMS moves back to the "Available services" section, and your credentials are permanently deleted. You can reconnect any time.
Setting up SMS reports
ASPSMS is only the prerequisite, the engine in the background, so to speak. You set up the actual sending under Reports.
There you create a report, pick "SMS" as the channel, and enter the recipients' phone numbers. Important: in international format with a plus sign, so +12125551234.
Without ASPSMS connected, the SMS channel stays locked there. You can see it, but you cannot click it. With ASPSMS active, it is ready to go.
For a step-by-step walkthrough of setting up a report, see Setting up reports.
Common questions
Where do I find my Userkey and API password?
In your ASPSMS account, not at Trustlytics. Sign in there, and in the main menu "Registered Users", click "API Credentials". Both items are on that page.
Is the API password the same as my ASPSMS login password?
No, and that is the most common mistake. ASPSMS issues a separate password for interfaces. That is the only one that belongs in the Trustlytics form.
My connection test is failing. Why?
Almost always one of the two entries. First check that you actually entered the Userkey and not your email. Second, check that the password field holds the API password and not your sign-in password. Open "Edit" and copy both over fresh from your ASPSMS account.
What does all this cost me at Trustlytics?
Nothing extra at Trustlytics. You only pay for the texts you send, and you pay ASPSMS directly out of your credits. Around CHF 0.06 per text, depending on the destination country.
Does the connection test use up credits?
No. The test only checks whether your credentials are correct. It does not send an actual text, so it does not cost you anything.
What happens when my credits run out?
Then the text does not go out. Your email reports carry on unaffected. So if you rely on the texts, it pays to glance at your ASPSMS account now and then, especially when several recipients are on the list.
I deleted ASPSMS. Are my SMS reports gone now?
The reports themselves stay set up, but they cannot be sent as long as no SMS provider is connected. Reconnect ASPSMS and sending picks up again.
Can I use ASPSMS for several websites?
Yes. A single ASPSMS account is enough, no matter how many websites you manage in Trustlytics. So you do not have to register multiple times or juggle several credit balances. All texts are billed against the same balance.
Do my ASPSMS credits expire if I do not use them for a while?
No. Credits you buy at ASPSMS stay put, they do not expire. So you can start at your own pace and do not have to rush through them.
Do I have to renew the connection regularly?
No. You set it up once and it keeps running. Only when you change your API password at ASPSMS do you have to update it here.
Are there other SMS providers to choose from?
Right now Trustlytics works with ASPSMS. The upside: Swiss company, data processed in Switzerland, Swiss data protection, ISO 27001 certified. Plus clear pricing and no subscription.