◾"Client action" event

Smartico has a specical type of event called "Client aciton".

Such actions can be triggered from the front-end or through the REST API and can start realtime campaigns (Journeys), Automation rules and progress/complete Missions or Badges.

In order to see "Client action" value in the Smartico BackOffice, you need to trigger it at least once, the triggered value will appear within 30 minutes in Smartico BackOffice automatically.

You can also register "Client action" manually in the Smartico BackOffice \ Tools \ Properties. Search for "Client action" property and use "+" sign to add action.

How to trigger client action from the front-end

You can report a specific action done by the end-user, for example when the user is clicking on the submit button on the cashier page, you can report the action 'CashierSubmitClicked'.

_smartico.action('CashierSubmitClicked');

As soon as the action is defined, and triggered at least once, you can build a real-time journey to react to such action.

Triggering custom action through the URL (or any other deep link)

In some cases, you will want to start a campaign when the user is getting to a specific page.

One of the options is to pass a special parameter in the URL of any of your pages.

For example, you can build a URL like:

https://mycasino.com/deposit.html#_smartico_dp=dp%3Aaction%26action%3DDEPOSIT_OPENED

When a user comes on this page you can catch him with the campaign waiting for the "Core: client action" and action DEPOSIT_OPENED

Note: the passed parameter in our example is "dp:action&action=TEST5" which is "URL Encoded". You can also pass any other deep links that will be triggered automatically after the user is logged in

Trigger client action through the REST API

You can send client action using server-to-server approach using Smartico REST API.

You can find details of REST API in the Smartico BackOffice \ Tools \ REST API (requires special permissions as there are secret keys that should be kept in private).

Example of payload in the REST API request

Payload of request should contain one required field called same way "client_action", and may contain any other information. The payload of event may contain links to reset password, email verification or whatever you decide.

For exampe, your payload may look like

{
    "eid": "98866720-1ae7-452c-bc08-1b703954d2ea",
    "event_date": 1737986306201,
    "ext_brand_id": "spacex",
    "user_ext_id": "test98635568",
    "event_type": "client_action",
    "payload": {
        "client_action": "reset_password",
        "url": "https://mysitecom/reset?code=WREWSREGS"
    }
}

To handle this event you need to prepare realtime campaign triggered by "Client action" event and with Client action = "reset_password" (or any other name that you choose).

Inside campaign you, will send email right on the start of campaign. And inside mail resource, you will write something like this

Here is your link to reset password - <a href="{{event.url}}">click here</a>

Another case, you want to inform client that he got a cashback.

{
    "eid": "98866720-1ae7-452c-bc08-1b703954d2ea",
    "event_date": 1737986306201,
    "ext_brand_id": "spacex",
    "user_ext_id": "test98635568",
    "event_type": "client_action",
    "payload": {
        "client_action": "cashback_ready",
        "cashback_amount": 44.22,
        "cashback_currency": "USD",
        "url": "https://mysitecom/activate_cashback?code=WREWSREGS"
    }
}

And example of email:

You got {{event.cashback_amount}} {{event.cashback_currency}} in cashback, 
<a href="{{event.url}}">click here to activate</a>