In these particular times, companies are now more than ever shifting their efforts towards increasing their online presence. This, while facing economical uncertainties and needing to preserve cash as much as possible. This reflects an unprecedented need to make sure marketing dollars/euros are spent on those campaigns that bring most return for just-enough investment.
This does in no way mean that we’re quickly launching a half-baked product!
It is in this spirit that Hans and I have decided —a few months ahead of planning— to pre-release journy.io. This does in no way mean that we’re quickly launching a half-baked product. Having successfully field-tested our MVP and public-beta releases throughout our early customer programme, we are now confident that the released features are GA-ready and will provide the intended value of evaluating channels, campaigns and funnels against sales conversion.
Features we are releasing
‘Under the hood’: Advanced Tracking
Everyone’s tracking. So much that Apple and Firefox have been altering their browsers to block any JS cookie that is either not from own domain (3rd party) or older than 7 days. And while we welcome any measure that would endorse complying to GDPR, CCPA and other privacy directives, we also strongly feel it is upon the end-user to decide whether he allows tracking for the benefit of receiving a more personalised interaction with the brand. Certainly when that visitor has been provided clear data processing information and has given consent through a proper data processing and privacy agreement. journy.io offers brands the technology to perform advanced tracking that is not impacted by the browser’s vendors.
Think of it as your own URL shortners (on own domains), with special instructions on how to redirect and what events to trigger.
Further focussing on security, usability and flexibility, we also introduce tracking URLs. Such URLs allows our customers to track virtually anything through the use of jtm parameters (on top of the known utm) which never directly trigger target servers. Think of it as your own URL shortners (on own domains), with special instructions on how to redirect and what events to trigger. This makes the often-required use of event code snippets redundant!
Visit this link for more information.
A clear overview of the funnels, channels, campaigns, pages and attribution elements that contribute to journeys achieving the goal event (e.g. sign-up, registration completed...)
Channels: Conversion, Multi-Campaigns, Setup & Details
- Full channel management features that allow utm sources and referrers to be viewed as ‘logical’ channels, with proper logo, description.
- Comparison chart that shows how channels compare to each other, in function of how they perform against the goal event. In terms of totals, new/recurrent/ assisting and conversion.
- Comparison chart that shows how channels compare to each other, in function of associated campaigns. You get a clear answer on which channels worked best for which campaigns.
Campaigns: Conversion, Multi-Campaigns, Setup & Details
Similar to channels, we offer full campaign management.
- Full campaign management features that allow utm campaigns to be viewed as ‘logical’ campaigns, with proper logo, description, etc...
- Comparison chart that shows how campaigns compare to each other, in function of how they perform against the goal event. In terms of totals, new/recurrent/ assisting and conversion.
- Comparison chart that shows how campaigns compare to each other, in function of associated channels. You get a clear answer on which campaigns worked best for which channels.
Funnels: Flow Lists and Details, Events Setup
- All flows that lead to goal event, sortable as (horizontal) tree view, or by most occurrences.
- Flow detail that highlights the traffic between the different events, on where customers take another path or where they drop off.
Attribution: Channels + Campaigns
- A clear visual on how traffic is formed for customer journeys that flow between 2 events, from event 1 to assisting to event 2. One can choose to see only channels, only campaigns, or all unque combinations of channel and campaigns
Contacts: Lists, Summarised Details (Part I so far)
- List of contacts that were identified under certain conditions, sortable by location, first touch timestamp, last touch timestamp and amount of touchpoints.
- Contact details with initial summary, including flow, top channels, top campaigns, top pages, location, first touch and last touch timestamps, as well as a full history of all touchpoints.
- Not all planned features are implemented yet: mainly engagement score and detailed profiling are still missing. See later section “Features we didn’t release yet”
Discover (Others): Channels, Campaigns, Events
- List of traffic characteristics that are not strategic for the setup and therefore left to be seen as “Others”. The moment the amount of occurrences are important enough you can easily add them (back) to your ecosystem with 1-2 simple clicks...
Settings: Personal, Business, Notifications, Team, Billing
- Personal info: to set name, email and password.
- Notifications: to set personal notification and digest information in-app or through email.
- Business/Account settings: to set the name of the account, the main goal event towards dashboard, digest and channel+campaign conversion screens.
- Team management: to define who can view and access the account.
- Integrations/SLACK: To set which types of notification and digest messages you want to receive in your favourite Slack channel.
Features we didn’t release yet!
Engagement scoring (May)
Knowing the journey a visitor is traversing, and (deep-)learning the various flows a visitor could traverse at which conversion, it will determine how likely that visitor will be buying. As such, based on their behaviour, we will be assigning engagement scores to visitors and send out notification for those identified visitors that reach a certain level.
Behaviour-based profiling (May-June)
By assigning profile attributes to content and specific situations (pages, campaigns, events), we will be able to construct a behaviour-based profile for each visitor.
CRM/Ecosystem Synchronisation (June+)
We understand that the data we produce must be shared across an ecosystem of customer data-consuming apps. We may select different middleware platforms to that end, but will certainly implement some direct connectors as well...