0.9.0

Elasticsearch upgrade notice. We'll be raising Elasticsearch compatibility to 7.* in the beginning of 2020 to keep with the latest changes. Current implementation Segments API is tested and maintained again Elasticsearch 6.*. Please plan your upgrade accordingly.

Go was updated to version 1.13.

[Beam]

• Major refactoring and redesign of IOTA (on-site stats) which now include more relevant statistics. GH-24
• Article detail now shows referer (traffic source) statistics. remp/remp#445
• Added command for compressing snapshot data. remp/remp#442
• Timespent interval configuration in JS is now configurable. remp/remp#461
• Added configuration for various views of conversion rate (decimals, multiplier). remp/remp#475
• Added support for property token selection on Beam dashboard. remp/remp#473

[Campaign]

• Bugfixed notice in showtime when adblock was not detectable. remp/remp#447
• Campaign listing now displays segment names instead of segment codes.
• Bugfixed campaign form not being able to update some options to their default value.
• Added HTML overlay banner template. remp/remp#457
• Added support to pass custom query parameters to displayed banner URL.
• All links in banner (not just CTA) now include Campaign's UTM parameters. remp/remp#455

[Mailer]

• Updated Hermes library, logging only error events to the database.
• Refactored UTM parameter replacing in email links.
• Added support to send single emails via API.

0.8.2

Elasticsearch upgrade notice. We'll be raising Elasticsearch compatibility to 7.* in the beginning of 2020 to keep with the latest changes. Current implementation Segments API is tested and maintained again Elasticsearch 6.*. Please plan your upgrade accordingly.

Changelog:

• [Mailer]: Fixing error screen in case SSO wasn't able to log user in 7fd4154

  Please change following line in your .env file in Mailer:

  SSO_ERROR_URL=http://mailer.remp.press/sign/error
  

• [Campaign]: Some tables didn't have primary keys since creation. This was preventing migrations on the replicated instances. This release fixes the failing migration issue. f211d2c

Note: generated binaries are the same as in 0.8.1, no need to deploy them if you have 0.8.1 deployed.

0.8.1

Elasticsearch upgrade notice. We'll be raising Elasticsearch compatibility to 7.* in the beginning of 2020 to keep with the latest changes. Current implementation Segments API is tested and maintained again Elasticsearch 6.*. Please plan your upgrade accordingly.

Changelog:

• [Segments]: Fixing mapping fetching changes which was causing "include_type_name" deprecation notices since Elastic 6.8. This is to prepare to provide full compatibility for Elastic 7.* and drop compatibility promise for 6.* in the following months.

• [Beam]: Added experimental database-based dashboard data source which works with snapshot of "concurrents" data made every minute. Snapshotting is being done automatically for you against concurrents_by_browser elastic index. This should be populated by your Telegraf instance based on similar configuration.

0.8.0

Changelog:

• [Mailer]: Material checkbox was not being rendered properly in Mailer causing custom generator implementations not being able to use it.

• [Mailer]: If generated queue was too big, memory exhausted exception was possible. Pagination was added to queue generation prevent the issue.

• [Beam]: New functions for tracking commerce events were added to give caller more precise control over what is being tracked. See documentation of following methods in https://github.com/remp2020/remp/tree/master/Beam#js-tracking-interface:

  • remplib.tracker.trackCheckoutWithSource
  • remplib.tracker.trackPaymentWithSource
  • remplib.tracker.trackPurchaseWithSource
  • remplib.tracker.trackRefundWithSource

• [Beam]: In some cases, Beam's database could have been migrated with invalid default value for conversion's paid_at column. 553c2dc

• [Campaign]: New configuration options were added to append extra query parameters to banner's target URL in case target page needs to identify source page/article and referer is not enough.

  See rempConfig.campaign.bannerUrlParams object at https://github.com/remp2020/remp/tree/master/Campaign#javascript-snippet for more detailed info:

  bannerUrlParams:  {
      "foo": function() { return "bar" },
      "baz": function() { return "XXX" }
  }
  

• [Campaign]: HTML banner now supports custom JS and CSS inclusion from external sources.

• [Campaign]: Bugfixing HTML banner's Farbtastic color picker which was not being initialized after the latest dependency changes.

Note: Generated binaries were not changed since 0.7.0, there's no need to redeploy them if you have 0.7.0 deployed.

0.7.0

Changelog:

• [Breaking][Segments]: Configuration option ELASTIC_ADDR in .env file was renamed to ELASTIC_ADDRS. The value now supports multiple comma-separated addresses to Elastic servers. At least one address needs to be functional for application to start.
• [Tracker]: Tracker now tries to parse provided referer manually before it's passed to the source detection library. If the referer is not parseable, derived_referer_medium is set as unknown.

0.6.1

Changelog:

• [Tracker]: New property "explicit_referer_medium" added to tracker options. It allows to specify custom referer (not based on Referer HTTP header) when tracking pageviews. The value can be utilized later, e.g. in Beam dashboard statistics.
• [Tracker]: Added support for tracking of reading progress (both for full page and for articles). See swagger.json and section related to track/pageview.
• [Segments]: New "inverse" flag added, which allows to invert arbitrary "filter_by" condition when querying Segments API.

Related to reading progress tracking, we've also release updated version of our Telegraf fork. You can download the newest version (1.10.4) here: https://github.com/remp2020/telegraf/releases

0.5.3

Changelog:

• [Segments]: Segments internally caches mapping of each requested index. When an alias was requested, Segments API returned an error regarding missing mapping. This version fixes the issue of missing mapping data for aliases and handles it correctly.

0.5.2

Bugfixing mail type stats view when no stats are present yet

0.5.1

Adding ProcessPageviewSessions to Beam's console Kernel

This command was unintentionally omitted from Kernel and the default
installation doesn't have any session/device data because of that.
Even though it's still possible to run the command manually, this
shouldn't be visible to the user/admin and it should be consistent
with the rest of command suite.

0.5.0

Changelog:

• [Segments]: Adding segment criteria related APIs used by new version of Segment creation UI. You can check the new APIs in generated swagger.json
• [Segments]: Segment check APIs now has explicit whitelist on what rules are cacheable to prevent bloat of cache property in responses
• [Tracker]: Removed obsolete tracking properties (source.ref, source.social) as they're being generated automatically into derived_referer_source and derived_referer_medium fields.